Deno joins Cloudflare to bring Workers to self-hosted infrastructure

Why it matters

Deno is ending its separate runtime and hosting roadmap to help Cloudflare address a specific gap: running Workers and Durable Objects across self-managed infrastructure. The transition gives Deno Deploy customers six months to migrate and runtime users a year of company-backed maintenance.

Deno's entire team is joining Cloudflare, where Ryan Dahl (@rough__sea) plans to focus on making Cloudflare's Workers programming model practical to run on infrastructure outside Cloudflare's network. The move folds Deno's future development into a shared platform built around celld, Deno's system for self-hosting distributed applications, and Cloudflare's open-source workerd runtime.

Dahl has spent much of his career revisiting the foundations of server-side JavaScript. He created Node.js in 2009, then introduced Deno in 2018 after concluding that Node's security model, package management and tooling needed a fresh start. Before Deno, he worked at Google Brain; he studied mathematics at UC San Diego and began a doctoral program at the University of Rochester. Now he is turning away from building a separate runtime and hosting service to work on the infrastructure layer he says remained complicated even after Deno Deploy.

In Deno's announcement on October 9th, Dahl described the move as a continuation of the team's effort to make server software simpler. The transition comes with a clear product tradeoff: Deno says it will support the runtime with monthly bug-fix and security releases for another year, then end its own runtime development. Deno Deploy will operate for six more months before shutting down. Deno says it will support paying Deploy customers migrating to Cloudflare Workers.

From runtime to infrastructure

Dahl's latest project, celld, takes the Workers programming model in a direction Cloudflare has wanted to support but had not yet made production-ready for self-hosters. It lets developers build distributed applications using Durable Objects, where each object can keep state and handle requests. Dahl's stated aim is to make scaling part of the programming model, reducing the infrastructure decisions each application must solve separately.

Cloudflare's joint announcement makes the technical gap explicit. Its workerd runtime is open source, but Cloudflare says workerd's Durable Objects support has been limited to a single instance, suitable for local testing but unable to scale across machines. Deno built celld to address that self-hosting problem. The teams now intend to combine celld's work with workerd so developers can run the model on Cloudflare or on their own infrastructure.

Cloudflare is bringing in a team that has spent years building developer tooling around a runtime, then extended its work into hosting and self-hosting. In Cloudflare's account, the missing piece was the surrounding production tooling and services that make an open-source runtime usable beyond a local development environment. Dahl's experience operating Deno Deploy showed him the cost of assembling that infrastructure: he describes a system of multiple public clouds, databases and tightly connected services. Celld's design aims to reduce that burden.

Deno's wider product line will not all follow the runtime and hosting service out the door. The JSR package registry will continue operating, with its infrastructure moving to Cloudflare. Deno also says it will continue supporting rusty_v8 and work toward integrating it into workerd. The runtime itself will remain open source, and Deno says others can continue its development after Deno's support period ends.

Deno's thesis moves to Cloudflare

Deno's original thesis was that server-side JavaScript could be easier to use if it followed web standards and included more of the development toolchain. When Deno announced its formation in 2021, Dahl and co-founder Bert Belder said they wanted to build commercial applications on top of open-source technology rather than reserve core runtime features for paid customers. The new plan retains that emphasis on reusable infrastructure, while moving Deno's engineering effort into Cloudflare's platform.

Investors had backed Deno's independent effort: Sequoia Capital led its $21 million Series A, announced on June 21st, 2022, with participation from Nat Friedman, Insight Partners, Automattic, Netlify and others. The announcement does not provide current revenue, customer or usage figures, so that round is historical context rather than a measure of Deno's present scale.

Dahl says Durable Objects could also fit applications that need persistent state, WebSockets and serverless execution, including AI agent systems. That is a use case the companies want to explore, not evidence of customer adoption. Their concrete commitment is to make the Workers model easier to run outside Cloudflare, with the Deno team and celld's work now inside the effort.

The move also gives Deno's users two different continuity paths. JSR is transferring onto Cloudflare infrastructure, while Deno Deploy customers are being directed toward Workers. Runtime users get a defined maintenance window and an open-source project that may outlive Deno-sponsored development. For Dahl, the independent runtime was one answer to simplifying server software; the next attempt is to make a distributed application platform simpler to operate.