Cloudflare Acquires Deno: What Happens to Deno, Deno Deploy and JSR

Last updated: October 11, 2026. Facts checked against Ryan Dahl’s post on the Deno blog, the joint Cloudflare blog post by Kenton Varda and Ryan Dahl, Cloudflare’s Workers pricing docs and Deno’s Deploy pricing page, with reporting from TechCrunch and The New Stack. This is a researched news explainer.

Deno was the most famous “fix Node.js” project in JavaScript. Ryan Dahl started it in 2018 after creating Node.js itself. Now the Deno company is folding into Cloudflare, and the products many developers built on are being wound down. Here’s exactly what changes, the dates to plan around, and what a move to Cloudflare Workers could cost.

What did Cloudflare announce?

Cloudflare said on October 9, 2026 that the whole Deno team is joining the company to work on Cloudflare Workers and Durable Objects. The goal is to merge Deno’s open-source celld project into workerd, Cloudflare’s open-source Workers runtime, so developers can self-host the Workers programming model on their own servers.

In Deno’s own words: “Today we’re announcing that the entire Deno team is joining Cloudflare to take that work further,” Ryan Dahl wrote on the Deno blog. TechCrunch described the deal as Cloudflare acquiring Deno and reported that the financial terms were not disclosed. Deno had raised about $26 million in total, including a Series A led by Sequoia, according to TechCrunch.

Ryan Dahl and Deno co-founder Bert Belder will lead a new Cloudflare effort to “make workerd self-hosting a first-class supported way to build and run apps using the Workers programming model,” Cloudflare distinguished engineer Kenton Varda wrote in the joint Cloudflare post.

What happens to the Deno runtime?

The Deno runtime gets one more year of support, with monthly releases that contain bug fixes and security updates, and then Deno the company stops developing it. Deno stays open source under the MIT license, so the community can keep it going after official work ends.

Deno’s blog lists four concrete commitments:

• Deno runtime: supported “for another year with monthly releases containing bug fixes and security updates.” After that, the Deno team ends development, but “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,” with migration support for paying customers moving to Cloudflare Workers.
• JSR: the JavaScript package registry “will continue operating, with its infrastructure moving to Cloudflare.”
• rusty_v8: Deno’s Rust bindings for Google’s V8 engine stay supported, with work toward integrating them into workerd.

Dahl explained the runtime decision in a Hacker News comment, quoted by developer Simon Willison: Deno “has been sucked into the gravity well of node compatibility, which forces it to behave exactly as Node does. Why reimplement Node? It works.” Speaking to The New Stack, Dahl added that “how it lives on is up to the community,” pointing to the io.js fork of Node.js as a precedent.

When does Deno Deploy shut down?

Deno Deploy will keep running for six months from the October 9, 2026 announcement, which points to roughly April 2027, and then shut down. Deno hasn’t published an exact switch-off date yet, so treat April 2027 as an estimate and watch Deno’s dashboard and email for the official date.

Deno says it will provide migration support for paying customers moving to Cloudflare Workers. Free-tier users weren’t promised the same help, so they should plan their own move early.

Key dates at a glance

Approximate dates are calculated from the “six months” and “another year” wording in Deno’s October 9, 2026 post.

If you track software end-of-life dates for your team, add these next to your OS and app deadlines. Our Microsoft end-of-support calendar for 2026–2027 is a good model for planning around that kind of cutoff.

What is celld, and why did Cloudflare want it?

Celld is an open-source, self-hostable implementation of Cloudflare’s Workers and Durable Objects programming model, released by Deno in August 2026. It’s a single Rust binary that needs only an object storage bucket to coordinate and store data, which makes it far easier to run on your own servers than Cloudflare’s production system.

A Durable Object is a small, individually addressable server with its own SQLite database. Cloudflare’s own open-source runtime, workerd, could only run Durable Objects as a single instance, which Varda admitted is “good enough for local testing, but unable to scale.” Celld filled that gap. “Here was an implementation of Workers and Durable Objects designed to be fully compatible with our own, while being focused on being self-hostable and scalable,” Varda wrote.

Varda also took on the lock-in argument directly. Celld makes it easier to move Workers apps off Cloudflare, yet he wrote that “being open source and giving people an escape hatch is good business.” Dahl told The New Stack the combined project is expected to stay open source, likely under the Apache 2.0 license celld already uses, and that “the API will be the same as Cloudflare’s own platform.”

How does Deno Deploy pricing compare with Cloudflare Workers?

Cloudflare’s Workers Paid plan starts at $5 a month and includes 10 million requests, while Deno Deploy’s Pro plan is $20 a month with 5 million requests. Both have free tiers. The two platforms meter different things, though, so check your real usage before assuming a move will save money.

Prices from Deno Deploy pricing and Cloudflare Workers pricing as listed on October 11, 2026. Both companies bill in US dollars, so UK customers pay the dollar price converted by their card provider.

Worked example: a small API

Take an app that serves 8 million requests a month and uses about 3 ms of CPU per request:

1. Deno Deploy Pro: $20 base, plus 3 million requests over the 5 million included at $2 per million = $26 a month (before any CPU, memory or bandwidth overages).
2. Cloudflare Workers Paid: $5 base. 8 million requests is under the 10 million included, and 24 million CPU-ms is under the 30 million included = $5 a month.

That’s a rough estimate from published list prices only. Deno also bills memory time and bandwidth, Cloudflare bills Durable Objects and other add-ons separately, and your own CPU numbers will differ. Treat it as a starting point, not a quote.

What should Deno users do now?

Deno Deploy customers should start planning a migration now, and Deno runtime users have about a year to decide whether to stay, switch to Node.js or Bun, or move code to Cloudflare Workers. Nothing breaks today, but the clock is running.

1. List what runs on Deno Deploy. Note custom domains, cron jobs, Deno KV data and environment variables, since each needs a new home.
2. Pick a target. Cloudflare Workers is the officially supported path, and paying Deno Deploy customers get migration help. Any host that runs Node.js is another option, because Deno has spent years improving Node.js compatibility.
3. Plan your Deno KV export. Deno KV is a Deno-specific database. Workers KV, D1 and Durable Objects on Cloudflare work differently, so budget time to move and test data.
4. Pin your Deno runtime version and keep applying the monthly security releases until you migrate.
5. Keep publishing to JSR if you use it. Deno says the registry continues, now on Cloudflare infrastructure.

Why does this matter beyond Deno?

The deal moves the team behind one of the three big JavaScript server runtimes into a cloud company and ends that runtime’s independent development. It also signals that Cloudflare wants its Workers model to run anywhere, not just on its own network, which matters for anyone worried about lock-in.

It follows Anthropic’s purchase of Bun in December 2025, The New Stack noted, with one key difference: Anthropic committed to keep developing Bun as an open-source runtime, while Deno’s runtime development is ending. That leaves Node.js, which is governed by the OpenJS Foundation, as the only one of the big three server runtimes whose core team doesn’t sit inside a single company.

AI is part of the pitch too. “Durable Objects bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface,” Dahl wrote. If you’re following how AI agents are changing developer tools, our guide on how to use OpenAI’s dots covers the consumer side of that shift.

FAQ

Did Cloudflare buy Deno?

Yes. Cloudflare announced on October 9, 2026 that the entire Deno team is joining the company, which TechCrunch reported as an acquisition. Financial terms were not disclosed.

Is Deno being discontinued?

The Deno runtime gets one more year of monthly bug-fix and security releases, then the Deno team stops developing it. The code stays open source under the MIT license, so others can continue it.

When is Deno Deploy shutting down?

Deno Deploy will keep operating for six months after the October 9, 2026 announcement, which points to around April 2027. Deno hasn’t announced an exact shutdown date yet.

What happens to JSR?

JSR, the JavaScript package registry Deno created, will keep operating. Deno says its infrastructure is moving to Cloudflare.

Will Deno help me migrate to Cloudflare Workers?

Deno says it will provide migration support for paying Deno Deploy customers moving to Cloudflare Workers. It hasn’t promised the same help for free-tier users.

What is celld?

Celld is Deno’s open-source, self-hostable implementation of the Cloudflare Workers and Durable Objects programming model, released in August 2026. Cloudflare plans to merge it into its open-source workerd runtime.

Sources: Deno blog: Deno is joining Cloudflare, Cloudflare blog: Deno is joining Cloudflare, Cloudflare Workers pricing, Deno Deploy pricing, TechCrunch, The New Stack, Simon Willison.