Cloudflare acquires Deno team, sets one-year end date for the runtime

Cloudflare announced on October 9 that it is bringing the team behind Deno, the JavaScript and TypeScript runtime created by Node.js inventor Ryan Dahl, onto its staff — and setting a hard end date for Deno's independent development. Financial terms were not disclosed.

Under the arrangement, Cloudflare will keep shipping monthly bug fixes and security patches to the open-source Deno runtime for one year, after which official development stops. The project remains open source, and Deno's own announcement said it welcomes other contributors who want to keep building on it — though continued community maintenance is a markedly different proposition than the backing of a well-funded company, leaving the runtime's long-term future genuinely uncertain. Deno Deploy, the hosted service built around the runtime, has a shorter runway: it shuts down in six months, with Cloudflare offering paying customers migration assistance toward Cloudflare Workers, its own serverless platform.

The Real Prize: celld

The acquisition's logic becomes clearer once you look past the runtime itself. Cloudflare's actual target appears to be celld, a Rust binary the Deno team released in August that lets developers run Cloudflare's Workers and Durable Objects infrastructure on their own servers rather than exclusively on Cloudflare's network. Dahl and Deno co-founder Bert Belder will now lead an effort to merge celld directly into workerd, Cloudflare's own open-source Workers runtime.

That detail matters because it points to an unsolved problem inside Cloudflare itself: according to one report, Cloudflare engineer Kenton Varda acknowledged that his own prior attempts to build a scalable, self-hosted version of Durable Objects «embarrassingly didn't work.» Rather than keep iterating in-house, Cloudflare appears to have concluded that acquiring the team that had already solved a version of the problem was the faster path — even if that team's own product line has to be wound down as a result.

What Survives the Transition

Not everything built around Deno is disappearing. JSR, the package registry Deno launched as an alternative to npm, will keep operating, though its infrastructure will now run on Cloudflare's network instead of Deno's own. The rusty_v8 Rust bindings that underpin Deno's V8 integration will also continue to be maintained, with work already underway to fold them into workerd as well.

A Notable Reversal

The deal is a pointed turn for a company that spent years positioning itself as Cloudflare's direct rival. Dahl had previously described Cloudflare Workers as Deno Deploy's most direct competitor, dating back to 2022 — the same year Deno closed a $21 million Series A led by Sequoia, part of roughly $26 million the company raised as an independent venture. Four years later, the rivalry has ended with the challenger's team joining the incumbent, and its flagship product given a one-year clock, as reported by The New Stack.

For developers currently running production workloads on Deno Deploy, the practical takeaway is immediate: start planning a migration path now rather than waiting for the six-month window to narrow, and for teams relying on the standalone Deno runtime, treat the one-year patch commitment as a firm deadline to evaluate whether community maintenance will be sufficient for long-term use, or whether migrating to an actively-developed alternative is the safer bet.