
Cloudflare Buys Deno: Self-Hosted Workers Finally Get a Team
Cloud Platform EngineeringCloudflare’s own principal engineer admits the company has struggled to make its open-source Workers runtime practical outside its network, and its fix is to hire the team that built a rival. For platform teams weighing Workers, the Deno acquisition announced Friday could make the Workers model portable, or it could simply leave them with one fewer runtime to choose from.
What Happened
The New Stack reports that the entire Deno team, led by Node.js creator Ryan Dahl, is joining Cloudflare. Terms were not disclosed. Deno raised around $26 million across two rounds and launched Deno Deploy in direct competition with Cloudflare Workers. In August, Deno released Celld, an open-source recreation of Cloudflare’s Workers and Durable Objects programming model for teams running on their own infrastructure.
Cloudflare’s announcement says the plan is to merge Celld into workerd, the open-source Workers runtime, with Dahl and Deno co-founder Bert Belder leading the effort. Cloudflare principal engineer Kenton Varda writes that workerd’s Durable Objects support is limited to a single instance, and that “The Deno team understands how to create a good developer experience around a self-hosted runtime.” He told The New Stack: “Frankly, we haven’t done a great job of building out the ecosystem of adjacent services and tooling to make it really work.”
Deno’s own post spells out the cost. The Deno runtime gets monthly releases with bug fixes and security updates for another year, and then Deno ends its development of the runtime. Deno Deploy keeps operating for six months, with migration support for paying customers moving to Workers. JSR continues operating.
Why It Matters
Celld’s design is the part to watch. Cloudflare describes it as a single Rust binary with object storage as its only external dependency, so a self-hosted fleet is many instances plus one bucket. Dahl told The New Stack the combined project should 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 — which is a good thing.” Varda framed the incentive in market terms: “If the model is exclusive to us, that narrows our TAM [total addressable market], and ultimately makes us less competitive versus the legacy clouds.”
That could flip the usual lock-in calculation. If the merger delivers, code written for Workers and Durable Objects could run on another provider or on premises behind the same API. Until then it is a plan, not a product: Cloudflare says more announcements will come “in the coming months.”
What This Means for Builders
Deno users carry the immediate cost. Deno Deploy customers have six months to migrate, and teams on the Deno runtime have a year of maintenance before they depend on the community. Dahl pointed to io.js, the community fork of Node.js that later merged back, as precedent. The New Stack draws the contrast with Anthropic’s purchase of Bun in December 2025: Anthropic committed to keep developing Bun as an open-source runtime, while Deno’s runtime development will end.
Dahl also pitched the model for AI agent harnesses, writing that Durable Objects combine “inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface.” Cloudflare has been building toward agent workloads already, as with its temporary Workers for AI agents.
The So What
Platform teams on Deno Deploy should start the Workers migration now rather than near the six-month deadline. Teams evaluating Workers should ask Cloudflare for the self-hosting roadmap in writing before committing. If workerd ships multi-instance Durable Objects backed by plain object storage, Workers becomes a portable architecture rather than a single-vendor bet. Until it does, plan as if it is still a single-vendor bet.
Source: The New Stack
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →