Deno Team Joins Cloudflare: Deno Runtime Gets One More Year of Monthly Releases, Deno Deploy Shuts Down in Six Months and celld Merges Into workerd
Deno's team is joining Cloudflare; Deno says it will support the runtime for one more year, run Deno Deploy for six months, and merge celld into workerd.
Overview
Deno’s team is joining Cloudflare, according to a post by Ryan Dahl on the Deno blog dated October 9, 2026. The post says the Deno company will keep supporting the Deno runtime for one more year, shut down Deno Deploy after six months, and fold its self-hosting work into Cloudflare’s open-source Workers runtime, workerd. TechCrunch describes the deal as an acquisition, while the Deno and Cloudflare posts both use the phrase “joining Cloudflare.”
What We Know
The announcement. The Deno blog says: “Today we’re announcing that the entire Deno team is joining Cloudflare to take that work further.” TechCrunch reported that Cloudflare announced the move on Friday, and that “the financial terms of the acquisition were not disclosed.” TechCrunch also reported that Deno had raised a total of $26 million, including a Series A led by Sequoia. The Cloudflare Blog post, written by Dahl and Cloudflare’s Kenton Varda, carries a publication timestamp of 2026-10-09T12:50:00.000Z.
What happens to the Deno runtime. According to the Deno blog, “We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime.” The post adds that Deno “will remain open source” and that others who want to continue its development are welcome to do so. It describes the change as a decision about focus: “We’ve decided to put our future development work into this shared platform rather than continuing to develop a separate runtime and hosting service.”
Deno Deploy, JSR and rusty_v8. Per the Deno blog, Deno Deploy “will continue operating for six months before shutting down,” with migration support for paying customers moving to Cloudflare Workers. JSR, the TypeScript-first package registry, will keep operating “with its infrastructure moving to Cloudflare.” The post says the team will continue supporting rusty_v8 and work toward integrating it into workerd.
The celld connection. The new work centers on celld, which The Machine Herald previously reported as Dahl’s self-hosted implementation of Cloudflare’s Durable Objects. Dahl writes on the Cloudflare Blog that “we’re merging workerd and celld,” and describes celld as “one binary, written in Rust, with object storage as its only external service dependency.” Varda writes that workerd “implements them, but only in a single-instance way, good enough for local testing, but unable to scale,” referring to Durable Objects. He says Cloudflare was “delighted” when the Deno team released celld in August.
Per the Cloudflare Blog, “Ryan and Bert will be leading a new effort to make workerd self-hosting a first-class supported way to build and run apps using the Workers programming model. This will involve merging code and ideas from celld back into workerd.” The post names Bert Belder alongside Dahl as part of the Deno Land crew and says more announcements will come “in the coming months.”
Cloudflare’s lock-in argument. Varda’s section of the Cloudflare Blog addresses a “popular theory” that Workers was built differently to create lock-in, calling it wrong and writing that “being open source and giving people an escape hatch is good business.” TechCrunch quoted the same passage and identifies Varda as principal engineer for Cloudflare Workers.
Why Dahl says it fits. Dahl wrote on the Deno blog that Durable Objects “bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface.” He acknowledged: “We know this is a consequential change for people who have built on Deno.”
What We Don’t Know
- Deal terms. TechCrunch reported that financial terms were not disclosed, as of its October 10, 2026 article. Neither the Deno nor Cloudflare post, as read for this article, states a price.
- Runtime fate after the support year. The Deno blog says Deno Land will end its own development of the runtime after one year and that others are welcome to continue it. None of the cited sources names a successor maintainer or a governance plan.
- Workerd timeline. Cloudflare’s post promises further announcements “in the coming months” but gives no dates or feature list for merging celld into workerd.
- Migration detail. The posts mention migration support for paying Deno Deploy customers moving to Workers but do not describe pricing or tooling for that move in the text read here.
Analysis
The three accounts agree on the core facts: the whole Deno team is moving to Cloudflare, and Deno’s own runtime has a stated one-year support window. They differ in framing. The Deno post presents the move as a change of focus toward a shared platform, the Cloudflare post presents it as a way to make self-hosting Workers and Durable Objects easier, and TechCrunch calls it an acquisition. Teams running Deno in production, or Deno Deploy workloads, now have two dates from the Deno blog to plan around: six months for Deploy and one year for runtime development by Deno Land.