The Cloudflare Deno acquisition was announced on October 9, and it ends two things at once: Deno Deploy shuts down in about six months, and the Deno runtime stops getting new features. If you host anything on Deno, you have a move to plan. If you only use the runtime locally, you have about a year.
Here’s what’s confirmed, what isn’t, and what to do first.
Quick facts — the short version before the details:
- Cloudflare is bringing in the whole Deno team, led by Ryan Dahl and Bert Belder. Terms weren’t disclosed.
- Deno Deploy closes in about six months.
- The Deno runtime gets security and bug-fix releases for about a year, then development ends.
- The runtime stays MIT-licensed, and the JSR registry continues.
- Deno’s self-hosting project, celld, will be merged into Cloudflare’s workerd.
The Cloudflare Deno acquisition, explained in plain terms
Deno was Ryan Dahl’s second try at a JavaScript runtime, built after Node.js. It raised about $26 million and later launched Deno Deploy, a hosting service that competed directly with Cloudflare Workers.
Now the team is moving over. According to The New Stack, the standalone runtime and cloud hosting are being wound down while engineers shift to Workers.
The real prize looks like celld, a Deno project launched in August. It’s a single Rust binary that recreates the Workers and Durable Objects model so you can run it on your own servers. Forbes notes this is Cloudflare’s second developer-tooling buy this year, after the Vite team at VoidZero in June.
What happens to Deno Deploy and the Deno runtime
The two products get very different treatment, so it helps to see them side by side. The dates below are relative, because neither report gives calendar deadlines.
| Product | What happens | When |
|---|---|---|
| Deno Deploy (hosting) | Shuts down. Paying customers get help moving to Cloudflare Workers. | In about six months |
| Deno runtime | Monthly bug-fix and security releases only. No new development. | For about one year |
| JSR package registry | Keeps running under Cloudflare. | No end date given |
| celld (self-hosting tool) | Gets merged into Cloudflare’s open-source workerd. | “Coming months,” no firm date |
The runtime’s license stays MIT, so anyone can fork it. But Dahl’s own words on the future were blunt: “How it lives on is up to the community.” No organization has committed to maintaining it yet.
Why Cloudflare wants celld and self-hosted Workers
Cloudflare has open-sourced its Workers runtime, workerd, for years. But Kenton Varda, who works on Workers, said Cloudflare “never quite cracked” the self-hosting experience.
That’s the gap celld fills. You run several instances against one object-storage bucket, and the software handles placement, routing and persistence. Dahl and Belder will lead the work of folding it into workerd.
Today, workerd only supports Durable Objects as a single instance. That’s fine for local testing, not for production, so the multi-machine part is the piece to watch. Dahl says the merged project will “likely” stay open source under Apache 2.0, but that isn’t confirmed.
What Deno users should do this week
Your first step depends on which Deno product you use. Start with the list below, then pick the row that matches you.
- Deno Deploy users: list every app and domain on it, and start testing them on Workers now. Six months is tight for anything regulated.
- Runtime users: check where it runs, including build scripts and internal CLI tools, then decide between Node.js, Bun and Workers.
- Anyone curious about Workers: find which parts of your app rely on Durable Objects or other Cloudflare-only services.
The year-long runtime window sounds generous, but security patches are the only thing it guarantees. If you ship production code on it, treat that date as a deadline. Dependencies matter too: our guide to the MALFEX npm malware packages shows why a stale toolchain is a risk worth taking seriously.
What’s still unclear
Several things haven’t been answered yet, so treat any firm claim about them as a guess:
- The exact shutdown and end-of-support dates.
- Whether free-tier Deno Deploy users get migration help. Only paying customers are mentioned.
- Whether KV, R2 or Queues will get self-hosted versions.
- Who will sell paid support for self-hosted Workers.
It’s also a reminder of how fast the runtime space is changing. Anthropic bought Bun in December 2025 and said it would stay open source, per The New Stack. Deno is taking the opposite path. Maintainers weighing their options may also like our post on Anthropic’s free open-source security scans.
Frequently Asked Questions
Is Deno shutting down completely?
Not overnight. Deno Deploy closes in about six months, and the runtime gets security fixes for about a year. After that, development ends unless the community takes over.
Will my Deno code still run?
Yes. The runtime stays MIT-licensed and keeps working. You just won’t get new features, and fixes stop after the support window.
Where should Deno Deploy users move?
Cloudflare is offering migration help to Workers for paying customers. Node.js and Bun hosts are the other obvious options, depending on how your app is built.
How much did Cloudflare pay for Deno?
Nobody has said. Terms weren’t disclosed.
Our take: plan the move, don’t panic
If you’re on Deno Deploy, start testing on Workers this month, since six months goes fast once procurement and QA get involved. If you only use the runtime, you’re safe for now, but I wouldn’t start a new production project on it. The community may keep it alive, yet “may” isn’t a plan.
Leave a Reply