The Deno team's move to Cloudflare was announced on October 9, 2026, by Deno founder Ryan Dahl on the official Deno blog, and Cloudflare confirmed the plan in a post on its own blog the same day. This is no ordinary talent shuffle: as the whole team moves over, Deno's own hosting service, Deno Deploy, starts a shutdown countdown, and the standalone runtime enters its final year of official maintenance.
What Cloudflare actually lacks is a self-hostable Durable Objects
Cloudflare was unusually candid about the gap in its same-day post. Its open-source runtime workerd shares its codebase with production, but the Durable Objects implementation in workerd is single-instance only: fine for local testing, unable to scale for self-hosting. Cloudflare's own production routing system for objects, meanwhile, depends on hundreds of locations and a stack of external services, which makes it a poor fit for a customer's own data center. Celld, released by the Deno team in August 2026, fills exactly that hole: it is an open-source implementation of Workers and Durable Objects designed from the start for self-hosting and horizontal scaling. Ryan Dahl and Bert Belder will now lead the work of merging celld's code and ideas back into workerd, making self-hosting a first-class way to run the Workers programming model, with more detail promised in the coming months.
Two countdowns: six months for Deploy, one year for the runtime
For teams currently running on Deno, the timetable matters more than the vision. Deno Deploy will keep running for six months and then shut down, with migration support for paying customers moving to Cloudflare Workers. The Deno runtime will keep receiving monthly bug-fix and security releases for one more year, after which the original team ends development; the code stays open source and the community can carry it forward. The JSR package registry keeps operating, with its infrastructure moving to Cloudflare, and the rusty_v8 component will continue, with the goal of integrating it into workerd. Counting six months forward, services still running on Deploy around April 2027 must be migrated by then, and that window started on announcement day.
Why agent builders are watching this too
Dahl pointed specifically at the agent scenario in his announcement: Durable Objects pack cheap serverless execution, persistent state and WebSocket connections into a single object, which is close to the substrate that long-running agent harnesses need, and he invited teams building agents at scale to contact him directly. Read alongside the Cloudflare agent traffic figures covered on this site earlier — agent traffic has already overtaken human traffic — where the execution layer consolidates directly shapes agent products' cost structure and deployment boundaries. If Workers can run identically on Cloudflare's network and on a customer's own servers, agent vendors no longer have to choose between platform convenience and keeping data inside their own network.
Until the promises ship, though, all of this remains a roadmap. The tooling around self-hosted workerd is precisely what Cloudflare admits it has neglected, and whether the Deno team can close that gap depends on what actually ships in the next few months. For Deno users the decision is simpler: prepare migrations against the Deploy shutdown date first, then judge whether the self-hosted workerd is worth following.
