Deploy an app to Deno Deploy from a local directory with the deno deploy CLI
domain: deno.com · 8 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Auth: Interactive browser login on first `deno deploy` run; the CLI stores a token in the system keyring and reuses it (deno deploy logout clears it).
Create an account/organization at https://console.deno.com/ - the current Deno Deploy platform. Do NOT use the deprecated Deploy Classic dashboard (dash.deno.com) or deployctl; both were discontinued July 20, 2026.
In your project directory run `deno deploy` to deploy interactively, or `deno deploy --app my-app-name` to target a specific app.
To create the app non-interactively: deno deploy create --org my-org --app my-api --source local --framework-preset fresh --build-timeout 5 --build-memory-limit 1024 --region us.
Add --prod to deploy straight to the production timeline (e.g. deno deploy --org my-company --app my-api --prod); otherwise the deploy lands on a development/preview timeline.
The CLI tarballs the directory, uploads it, and Deploy builds and serves it, returning a live URL.
Use deno deploy switch --org <name> --app <name> to set the default org/app context for future commands in that directory.
Official docs: https://docs.deno.com/deploy/getting_started/ ; https://docs.deno.com/runtime/reference/cli/deploy/ ; https://docs.deno.com/deploy/migration_guide/
Known gotchas
Deploy Classic (dash.deno.com) and deployctl were discontinued on July 20, 2026 - use console.deno.com and the built-in `deno deploy` subcommand.
The legacy std serve() helper is not supported on the new platform; apps must use Deno.serve() or deploys fail with a timeout error during the warmup phase.
Without --prod, deploys go to a development/preview timeline - a plain `deno deploy` does not update the production URL.
Regions are limited to US and EU on the new platform (down from 6 regions in Classic).
Build timeout defaults to 5 minutes (extendable on paid plans); --build-memory-limit accepts roughly 1024-4096 MB.
Give your agent this knowledge — and 17,900+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?