A Deno Deploy Alternative Before It Closes In April 2027

Deno Deploy closes in April 2027. A Deno Deploy alternative for your API and your front end, what to do with Deno KV data, and a dated migration checklist.
The OxyPages Team · · 8 min read
Your Deno Deploy app still runs fine, and that's the problem. Nothing is broken, so it's easy to leave the move until March, and then find out in a hurry which parts of your code only work on Deno.
On 9 October 2026 Deno announced it is joining Cloudflare. Deno Deploy keeps running for six months and then shuts down, and the pricing page now says "Deno Deploy will be sunset in April 2027."
If you picked Deploy for a small SaaS, a front end plus an API, you're choosing a Deno Deploy alternative for two different things at once. The front end is the easy half. The API is mostly portable too, because Deno handlers are built on the same web-standard Request and Response objects most modern hosts use.
The hard parts are narrower than people fear: Deno KV, Deno.cron, and anything that calls a Deno.* API directly. This post covers where each piece goes, five places worth moving to, a worked example, and a checklist with dates. Every Deno detail comes from Deno's own blog, docs and pricing page, and every price is as of November 2026.
TL;DR: Deno Deploy shuts down in April 2027, six months after Deno announced on 9 October 2026 that it is joining Cloudflare. Deno is offering migration help to paying customers moving to Cloudflare Workers, which makes Workers the default destination. Netlify Edge Functions also run on a Deno-based runtime. If you'd rather keep running Deno itself, Railway or Fly.io will run it in a container. Move the built front end to any static host. Export Deno KV data early, because it has no drop-in equivalent elsewhere.
If your Deploy project was only ever a static site, a static hosting comparison across every option is the shorter read. This post is for apps with server code.
What Is Happening To Deno Deploy?
Deno Deploy is closing in April 2027, and Deno's team is moving to Cloudflare. The announcement, posted 9 October 2026, says Deploy "will continue operating for six months before shutting down" and that Deno "will provide migration support for paying customers moving to Cloudflare Workers."
Two more lines in that post matter for planning:
- The Deno runtime gets one more year of monthly bug-fix and security releases. After that, Deno says, "we will end our development of the Deno runtime."
- JSR, the package registry, keeps operating, with its infrastructure moving to Cloudflare.
So this is a hosting move with a second, slower question behind it. If you keep running Deno on another host, you're on a runtime with a known end to development. That doesn't make it unsafe next year, but it's worth keeping new code runtime-neutral.
The free tier was already shrinking. When the new Deploy went GA on 3 February 2026 the free plan included 100 GB of egress and 15 CPU hours. As of November 2026 it lists 20 GiB of egress and 10 hours of active CPU a month.
What Deno Deploy Did Well
Deploy was a pleasant place to ship TypeScript. No build config, framework detection for Next.js, Astro, Fresh, SvelteKit and Nuxt, a preview for every commit, and an isolated database per pull request. Pro was $20 a month flat with ten team members included, which is generous next to per-seat pricing.
If you loved that workflow and you're a paying customer, take Deno's offer of migration help to Workers. It's the path Deno itself is putting effort into, and nobody else is offering you hands-on help.
The Parts Of A Deno App That Move Easily

Most Deno Deploy code is plain web-standard JavaScript, and that part moves with very little change. A Deploy handler takes a Request and returns a Response. Cloudflare Workers do the same thing; only the wrapper differs.
// Deno Deploy
Deno.serve((req) => new Response("ok"));
// Cloudflare Workers
export default {
fetch(req) {
return new Response("ok");
},
};
Those objects come from the browser's Fetch API, which is why they travel. MDN's reference for the Fetch API lists what's in the standard. If your code sticks to fetch, Request, Response, URL and crypto, it ports to Workers, Netlify Edge Functions, Bun or Node with little more than a new entry point.
Which Parts Need A Plan?
Three things don't travel, and finding them first saves the rest of the move. Search your code for each of these:
Deno.openKv. Deno KV is specific to Deno. Outside Deploy, Deno's docs describe KV running on a local SQLite file for development, which on a server means one machine and a persistent disk. Elsewhere, the data has to move to another store, such as Postgres, Cloudflare KV or D1.Deno.cron. Scheduled jobs need the new host's own scheduler. Workers have cron triggers, and Railway has cron jobs.- Other
Deno.*calls, such asDeno.envor file reads. Each one needs the new host's equivalent, usually environment bindings. - Deploy's Postgres. If you used the dashboard's free Prisma databases, dump them with
pg_dumpand restore to your new provider. - Server-rendered pages. A Fresh or Next.js app that renders on the server needs a host that runs server code. It can't go onto a static host.
The front end is the exception to all of this. A Vite, React or static Astro build is just files, and it can move this week.
Picking A Deno Deploy Alternative For Each Half
Here are five options, checked on each vendor's own pages in November 2026. Prices are monthly unless marked.
| Host | Takes which half | Free tier | Real starting price | The catch |
|---|---|---|---|---|
| Cloudflare Workers | API + front end | 100,000 requests a day, 10 ms CPU per request, unlimited static asset requests | $5 a month minimum, 10M requests included | No Deno KV; 10 ms CPU cap on free |
| Netlify | API + front end | 300 credits a month, hard limit | Personal $9 a month; Pro $20 a month, unlimited members | Sites pause when credits run out; bandwidth costs 20 credits per GB |
| Railway | API running real Deno | $1 of usage credit a month after a 30-day trial | Hobby, $5 a month minimum, includes $5 of usage | Usage billed on top; egress $0.05/GB |
| Fly.io | API running real Deno | None; $1 trial credit for 7 days | Smallest always-on VM $2.19 a month, plus egress | Docker and a command line |
| OxyPages | Front end only | 1 non-commercial site on a subdomain | Lite, $5 a month or $48 a year | No servers, functions or databases |
Cloudflare Workers
Workers suit most Deploy apps, and Deno is pointing paying customers there. Static assets are free and unlimited, and Workers Paid starts at $5 a month per account with 10 million requests included. The catches: free requests get 10 ms of CPU each, KV data has to be rewritten for Cloudflare's own stores, and Pages and Workers overlap. our Cloudflare Pages alternative post untangles that split.
Netlify
Netlify Edge Functions run on a Deno-based runtime, so edge-style handler code feels familiar. The free plan allows commercial use and custom domains, and Pro is $20 a month with unlimited members. Netlify now meters everything in credits, and an empty balance pauses your sites, so watch the bandwidth meter.
Railway
Railway suits people who want to keep running Deno exactly as it is. Put the app in a container, add Postgres beside it, and deploy from GitHub. Hobby is a $5 monthly minimum that includes $5 of usage, and builds are free. It's a minimum, not a cap.
Fly.io
Fly.io runs Deno in a small VM near your users, from $2.19 a month for the smallest always-on machine. There's no free tier, but a personal account's bill under $5 a month is waived with a card on file. Volumes are available if you insist on keeping KV on SQLite, though one machine with one disk has no failover.
OxyPages, For A Static Front End
We take the built front end and nothing else. Connect the repo and we build the Vite, React or static Astro output with SPA routing, or you upload the folder. A SaaS is commercial use, so it starts at Lite rather than the free plan. We don't run Deno, functions or databases, so your API needs one of the four hosts above.
A Worked Example: A Habit Tracker On Deploy
Say you run a small habit-tracking SaaS. A Vite front end, an API using Deno.serve, users and streaks in Deno KV, and one Deno.cron job that emails reminders at 8am. Here's how I'd move it to Workers plus a static host.
- Export KV now. Write a short script that lists every key with
kv.listand writes keys and values to a JSON file. Run it on Deploy and keep the file. This is the one step you can't do after April. - Pick the new store. Users and streaks are relational, so I'd load them into a small Postgres or Cloudflare D1 rather than force them into another key-value store.
- Port the handler. Swap
Deno.servefor the Workersfetchexport shown above, replaceDeno.envwith Worker bindings, and replace KV calls with the new database client. - Move the cron. Replace
Deno.cronwith a Workers cron trigger on the same 8am schedule. - Deploy the front end separately. Build it with the new API address in an environment variable, publish the
distfolder to a static host, and allow that address in the API's CORS settings. - Run both for a week, then switch DNS. Lower the TTL to 300 seconds the day before.
Step 2 takes the longest. Steps 3 and 4 are usually an evening.
A Dated Migration Checklist

Deno hasn't named a day in April, so treat 31 March 2027 as your deadline.
- By 30 November 2026: search the code for
Deno.openKv,Deno.cronand otherDeno.*calls, and list every environment variable and custom domain. - By 31 December 2026: export all KV data and any Postgres databases. Move the static front end, which needs none of the above.
- January 2027: stand up the API on the new host and run it against a copy of production data.
- February 2027: switch DNS for the API, keep Deploy running as a fallback, and watch error logs for a week.
- By 31 March 2027: nothing calls Deploy any more. Delete the old apps once you're sure.
What To Do Next
Run the code search from the checklist today. It takes five minutes and tells you whether this is an evening's work or a month's.
Then move the front end first, because it's the part with no Deno in it. If you want it on a flat price with no bandwidth meter, compare the plans. If your pages render on the server, keep them with the API on Workers, Netlify or Railway instead.
Whatever you pick for the API, any Deno Deploy alternative starts the same way: export the KV data before the end of the year. Everything else can be rebuilt; that can't.
FAQ
When Does Deno Deploy Shut Down?
April 2027. Deno announced on 9 October 2026 that Deploy would keep running for six months and then close, and the pricing page says it will be sunset in April 2027. No exact day was given as of 18 November 2026, so plan to be off by the end of March.
Is Cloudflare Workers The Official Replacement?
It's the one Deno recommends. Deno says it will help paying customers move to Cloudflare Workers, and the Deno team is joining Cloudflare. Free users can move there too, just without the hands-on help.
What Do I Do With My Deno KV Data?
Export it with a script that lists every key and saves the values, then load it into another store. Postgres or Cloudflare D1 suit relational data; Cloudflare KV suits simple lookups. There's no drop-in replacement, so budget time to change the code that reads it.
Can I Keep Running Deno Somewhere Else?
Yes. Railway, Fly.io and Render all run a Deno app in a container. Remember Deno plans one more year of runtime releases from October 2026, so any Deno Deploy alternative that keeps you on Deno is a medium-term answer, not a permanent one.