Cloudflare Buys Deno: Runtime Winds Down as Ryan Dahl's Team Joins Workers

Cloudflare is buying Deno, the company founded by Node.js creator Ryan Dahl, and the Cloudflare Deno acquisition comes with a big change for developers: the Deno team is moving on to Cloudflare Workers, and the standalone Deno runtime is being wound down. Cloudflare announced the deal on Friday without disclosing financial terms. For a JavaScript runtime that set out in 2018 to fix the mistakes its creator saw in Node.js, it is a surprising final turn.

Here is what is changing, what stays, and what developers who rely on Deno should do now.

What happened

Cloudflare and Deno shared the news in a joint blog post written by Dahl and Kenton Varda, the principal engineer behind Cloudflare Workers. According to TechCrunch, Cloudflare plans to use the acquisition to improve the Workers programming model and platform, which lets customers run code on Cloudflare's global network.

Dahl wrote that his team is joining Cloudflare to make the Workers model a mainstream way to build servers. He and Deno co founder Bert Belder will lead a new effort inside Cloudflare to make self hosting workerd, Cloudflare's open source Workers runtime, a first class option.

Deno had raised about $26 million, including a Series A led by Sequoia, according to TechCrunch and The New Stack. Neither company disclosed a price.

What the Cloudflare Deno acquisition means for each product

The joint blog post focuses on the future plan and points readers to Dahl's separate post on the Deno blog for details about Deno's own products. The New Stack reported the breakdown this way.

The Deno runtime

Active development of the Deno runtime is ending. According to The New Stack, it will get monthly maintenance and security updates for one more year. The code stays under the MIT license, so the community is free to fork it and keep it going. Dahl pointed to io.js, the community fork of Node.js from years ago, as a precedent and said the outcome is "up to the community."

Deno Deploy

Deno Deploy, the company's hosting service, will shut down in six months, The New Stack reported. Paying customers will receive help migrating. The report did not say what happens to free tier users beyond the shutdown itself.

JSR

JSR, the JavaScript package registry that Deno launched, will continue under Cloudflare, according to The New Stack. That is good news for library authors who publish there.

celld

In August, Deno released celld, an open source implementation of Workers and Durable Objects built for self hosting. The joint blog post describes it as a single Rust binary whose only outside dependency is object storage. The two teams now plan to merge celld with workerd. Varda told TechCrunch that celld "delighted" the Cloudflare team.

Why Cloudflare wants Deno

The deal is mostly about people and an idea. Cloudflare's workerd runtime is already open source, but the blog post notes that its Durable Objects support only runs as a single instance. That works for local testing, not for production at scale. celld solved that problem for self hosting, and the people who built it are Deno's engineers.

Varda was direct about it. The New Stack quoted him saying Cloudflare did not have the talent in house to build this on its own. He also argued that letting the Workers model run on other providers helps Cloudflare, because a model that only runs on one network would narrow the company's total addressable market.

That also answers a long running complaint about Workers: lock in. Varda rejected the idea that Cloudflare designed Workers to differ from other platforms to trap customers. He said open source and an "escape hatch" are good business, and the blog post notes that some former customers have already moved off Cloudflare using workerd.

AI is part of the story too. According to The New Stack, Dahl said AI agents are a major motivation, because Durable Objects are well suited to the harnesses that run agents. If you are new to that concept, our explainer on how AI agents work covers the basics.

Why it matters

A shake up in the JavaScript runtime world

For several years, server side JavaScript had three main independent runtimes: Node.js, Deno and Bun. That picture is changing fast. The New Stack pointed out that the Deno deal follows Anthropic's purchase of Bun in December 2025. One key difference, according to the report, is that Anthropic committed to keep developing Bun in the open, while Deno's runtime development is ending.

The result is that the runtime layer is getting folded into bigger platforms. Developers now have to think about who owns the tools underneath their code, not just how fast those tools run.

Open source sustainability, again

Deno is one more example of a well liked open source project that struggled to turn usage into a business. It is a familiar tension. We saw a version of it when Google paused part of its open source bug bounty program, as we reported in our story on that pause. Big platforms increasingly decide which open projects get long term funding.

Cloud competition

Deno Deploy competed directly with Cloudflare Workers, according to The New Stack. Removing it trims the field of edge hosting options. At the same time, a stronger self hosted workerd could give developers more freedom, since the same code would run on Cloudflare or on their own servers. Which effect wins out will depend on how quickly the merged project ships.

Who is affected

Deno Deploy customers are most directly affected. With a six month runway, teams need to plan a move now rather than later.

Developers building on the Deno runtime have a year of security and maintenance updates. That is enough time to test a community fork or to plan a move to Node.js, Bun or Workers.

JSR users should see little short term change, since the registry is staying.

Cloudflare Workers customers could benefit from more engineering muscle and a clearer path to running the same apps on their own hardware.

What developers should do now

1. Inventory your Deno usage. List which services run on the Deno runtime, which deploy to Deno Deploy and which only use JSR packages.
2. Start with Deno Deploy. It has the shortest deadline. Watch for the migration help Deno has promised paying customers.
3. Test compatibility. Check how much of your code depends on Deno specific APIs versus web standard APIs. Code that leans on standards will be easier to move.
4. Follow the fork conversation. If you value the runtime, keep an eye on whether a community fork gains real momentum within the support year.
5. Try the self hosted path. The blog post says developers can start self hosting celld or workerd today if they do not want to wait.

What to watch next

Cloudflare said more announcements will come "in the coming months." Watch for a timeline for the merged workerd and celld project, its final license (The New Stack said it will likely be Apache 2.0, the license celld uses), and clear guidance for Deno Deploy's free users. It is also worth watching whether other platform companies move to buy runtime teams of their own, following moves like this one and the Bun deal. For a sense of the money flowing into AI infrastructure behind these deals, see our coverage of the Bain report on AI revenue needs.

For more on big tech deals and the platforms developers depend on, visit our tech news section.

Frequently asked questions

Did Cloudflare buy Deno?

Yes. Cloudflare announced on October 9, 2026, that it is acquiring Deno. The Deno team, including founders Ryan Dahl and Bert Belder, is joining Cloudflare. Financial terms were not disclosed.

Is the Deno runtime being discontinued?

Active development is ending. According to The New Stack, the runtime will get monthly maintenance and security updates for one more year, and it remains MIT licensed so the community can continue it.

What happens to Deno Deploy?

The New Stack reported that Deno Deploy will shut down in six months and that paying customers will get migration help.

Will JSR keep working?

Yes. According to The New Stack, the JSR package registry will continue under Cloudflare.