Deno Deploy alternatives: where to move your apps before the six-month shutdown

Deno Deploy alternatives split three ways, and the right one depends on what your app touches. Plain fetch handlers move most directly to Cloudflare Workers. Apps that lean on Deno APIs move with the fewest edits to a Deno-based runtime such as Netlify or Supabase Edge Functions. Apps that need the full Deno runtime belong in a container.

That choice has a deadline. On October 9, 2026, Deno founder Ryan Dahl wrote that the Deno team is joining Cloudflare and that "Deno Deploy will continue operating for six months before shutting down." The post gives no calendar date. Counting six months from the announcement points to around April 2027, but that is our arithmetic, not Deno's. By the end of this guide you will know which platforms run your existing code, what each costs as of October 2026, and what to do about Deno KV and Fresh before the switch-off.

Is Deno Deploy shutting down? Yes, and only some users get help

The announcement is short and specific. These are the five commitments it makes, quoted from Deno's own post:

• "We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates."
• "After that year we will end our development of the Deno runtime. Deno will remain open source, and we welcome others who want to continue its development."
• "Deno Deploy will continue operating for six months before shutting down."
• "We will provide migration support for paying customers moving to Cloudflare Workers."
• "JSR will continue operating, with its infrastructure moving to Cloudflare."

Three things follow. First, migration help is promised only to paying customers, and only for a move to Workers. If you are on the free plan, or heading somewhere other than Cloudflare, you are migrating on your own. Second, the post says nothing about Deno KV databases, Fresh or Deno Subhosting, so any claim you read about their fate goes beyond what Deno has published. Third, the runtime outlives the hosting service by about six months, which matters if your plan is to keep running Deno yourself.

The post also explains the reasoning. Dahl writes that the team will combine its work with Cloudflare's Workers and Durable Objects teams and has "decided to put our future development work into this shared platform rather than continuing to develop a separate runtime and hosting service."

Deno Deploy alternatives compared by runtime and price

Prices below were checked on each vendor's own pricing page in October 2026. "Runs Deno code" means the platform executes on a Deno or Deno-compatible runtime, not that every Deno API works.

Two caveats sit behind that table. Netlify bills by credits, so the free tier is a credit allowance rather than a request count. And Vercel's Hobby plan, per its pricing page FAQ, "is for personal, non-commercial use," which rules it out for most production apps.

Plain fetch handlers: migrate Deno Deploy to Cloudflare Workers

If your Deno Deploy app is a module that exports a fetch handler and uses web-standard APIs, Cloudflare Workers is the shortest move and the only one Deno will help paying customers with. Workers runs on Cloudflare's own runtime, not Deno, so the work is in finding what your code assumes about Deno.

According to Cloudflare's Workers pricing page, the Free plan allows 100,000 requests per day with 10 ms of CPU time per invocation. The Paid plan has a $5 monthly account minimum and includes 10 million requests and 30 million CPU milliseconds a month, then $0.30 per additional million requests and $0.02 per additional million CPU milliseconds.

The 10 ms CPU cap on the Free plan is the number to check first. A handler that renders pages or parses large payloads is the kind most likely to need the Paid plan.

A practical order of work:

1. Search your code for the Deno namespace (Deno.env, Deno.openKv, Deno.readFile, Deno.cron). Each hit needs a Workers equivalent or a rewrite.
2. Move npm and Node built-in imports over. Cloudflare's Node.js compatibility docs say that for compatibility dates of 2026-08-04 or later, Workers enables nodejs_compat and nodejs_compat_v2 by default.
3. Rework how configuration reaches your code, and plan the Deno KV replacement using the next section.
4. Deploy a test copy, run it against real traffic patterns, and only then point your domain at it.

Skip Workers if your app depends heavily on Deno-specific APIs or on file system access. A Deno-based runtime will need fewer edits.

Deno KV alternative after shutdown: back up first, then choose a store

Deno KV is the piece most likely to cause trouble, because Deno's announcement does not mention it. Deno's documentation does describe a way out. Its KV backup page says "KV databases hosted on Deno Deploy can be continuously backed up to your own S3-compatible storage buckets," configured from the project's KV tab, with AWS S3 or Google Cloud Storage as targets. The page does not say whether that applies to the current Deploy platform, Deploy Classic or both, so check your own dashboard.

Turn that backup on now, whatever you decide later. Deno's Node.js KV docs note that "External KV Connect access to new‑Deploy KV databases is not currently exposed," so on the current platform the backup is the documented route to get your data out of Deno's infrastructure.

Once the data is in a bucket, you have three realistic homes for it:

• Self-hosted Deno KV. The open source denokv server is "a self-hosted backend for Deno KV," built on SQLite and MIT licensed. Its README documents running it as a replica of a Deploy-hosted database through the S3 backup feature with a sync-from-s3 option. Your Deno.openKv code keeps working against it.
• Cloudflare Workers KV. Cloudflare's own docs say Workers KV is eventually consistent, that changes "may take up to 60 seconds or more to be visible" elsewhere, and that it "is not ideal for applications where you need support for atomic operations." Fine for caches and config, wrong for counters or anything that relied on Deno KV's atomic transactions.
• Cloudflare Durable Objects. Cloudflare describes Durable Objects as combining compute with storage that is "strongly consistent yet fast to access," and lists them as available on Free and Paid plans. This is the closer match for transactional KV use, at the cost of restructuring how your app reaches its data.

Host a Fresh framework app without Deno Deploy

Fresh's own deployment docs list four targets: Deno Deploy, deno compile, Docker and Cloudflare Workers. The Fresh guide to Cloudflare Workers installs the Cloudflare Vite plugin and Wrangler, adds the plugin next to Fresh in the Vite config, and exports the Fresh server's fetch handler from a server.js entry file named in wrangler.jsonc.

The Docker route is simpler if you want to keep the Deno runtime. Fresh's Docker page uses the denoland/deno base image and starts the app with deno serve on the built server file. That image runs on Fly.io, on a Vercel container or on your own server.

Neither Fresh page says anything about the framework's future after the Cloudflare move, and the announcement does not either. If you are starting something new rather than moving something old, weigh that.

Deno-based runtimes keep code changes smallest

Three platforms run functions on Deno itself, which means fewer rewrites than Workers.

Netlify's docs say its Edge Functions run on "a secure runtime based on Deno." The limits are tight, and Netlify's limits page gives 50 ms of CPU execution time per request, a 20 MB compressed code size and 512 MB of memory per set of deployed edge functions. Netlify's pricing page lists Free at $0 with 300 credits, Personal at $9 a month and Pro at $20 a month. Edge Functions suit request-time logic on a site, not a whole API server.

Supabase's docs say "Edge Functions are developed using Deno," that the runtime is open source, and that functions run "on any other Deno-compatible platform (including self-hosted infrastructure)." Supabase's pricing page lists 500,000 Edge Function invocations on the Free plan and 2 million on Pro, which starts at $25 a month, then $2 per million. The catch: "Free projects are paused after 1 week of inactivity," so a low-traffic production function needs a paid project.

Appwrite's runtime docs list deno-2.0 and deno-2.6 among the runtimes on Appwrite Cloud, alongside Node.js and Bun. It makes sense if you also want Appwrite's database and auth. Its pricing page did not show per-plan function limits when we checked, so confirm them before you commit.

Vercel and Fly.io suit a container, not an edge isolate

Vercel does not list Deno among its official function runtimes, which cover Node.js, Bun, Python, Rust, Go, Ruby, Wasm, Edge and Container. The Container option is how a Deno app gets there. Per Vercel's Container runtime docs, it is "available in Beta on all plans" and runs any OCI image built from a Dockerfile.vercel file, billed on Active CPU. Functions run in a single region (iad1) by default unless you configure more. Skip Vercel if you need multi-region by default on a small budget, or if your project is commercial and you hoped to stay on Hobby.

Fly.io's Deno guide says fly launch detects a Deno app and generates a Dockerfile, then fly deploy ships it. You run the real Deno runtime on a long-lived machine, so Deno APIs that work on your laptop should work there too, and a denokv server can run beside the app if you keep Deno KV. Fly.io's pricing page lists a shared-cpu-1x machine with 256 MB at $2.19 a month, billed by the second while it runs, and no free allowance.

Self-host a Deno app on a VPS, with one date in mind

Running Deno on your own server keeps every API you use today. Coolify is one way to manage that. Its pricing page lists the self-hosted edition as "Free forever" and Coolify Cloud at $5 a month for two connected servers, plus $3 for each additional server, with the servers supplied by you.

The date to remember is the runtime's. Deno's post commits to one more year of monthly bug-fix and security releases, after which official development ends. A self-hosted Deno app is therefore a good bridge, not a permanent answer, unless the open source community picks up maintenance. If you migrated off another host this year, our guide to Railway alternatives covers a similar trade-off between managed platforms and your own servers.

What to do this week

1. Turn on Deno KV continuous backup to your own bucket and confirm a backup lands.
2. Search your code for the Deno namespace to size the rewrite.
3. If you pay for Deno Deploy and Workers fits, contact Deno about the migration support its post promises.
4. Deploy a copy to your chosen target and run it beside Deno Deploy before you switch DNS.

To compare more hosts side by side, Upfynd lists 247 products in Databases & Infrastructure and 491 in Developer Tooling, as of October 2026.