Deno team joins Cloudflare, Deploy shuts down

The entire Deno team is joining Cloudflare, and the deal comes with hard dates. Cloudflare will support the Deno runtime for one more year with monthly releases carrying bug fixes and security updates, then stop developing it. Deno Deploy, the hosting product, keeps running for six months and then shuts down. Deno stays open source, so anyone can pick up the runtime after Cloudflare steps back.

That timeline is the part worth acting on. If you run production workloads on Deno Deploy, you have roughly six months to migrate, and Cloudflare is offering migration support to paying customers moving to Workers. If you run the open-source runtime yourself, you have a year of security patches from the current team before that stops. After that the project continues only if the community carries it.

JSR, the JavaScript registry Deno built, keeps operating; its infrastructure moves to Cloudflare. rusty_v8, the Rust bindings to V8 that the runtime depends on, will continue to be supported, with work toward folding it into workerd, Cloudflare’s Workers runtime.

The reasoning Ryan Dahl gives for the move is a progression: Deno the runtime, then Deno Deploy the hosting service, then celld, a system built on the Workers programming model that lets you write distributed applications with scaling built into the model rather than bolted on by each application. Cloudflare already has the Workers and Durable Objects teams working the same ground. Rather than maintain a separate runtime and a separate hosting service, the Deno team is pointing its effort at that shared platform. Dahl frames the goal as making this programming model the default way to build servers, on Cloudflare’s network or your own infrastructure.

The AI angle is explicit. Durable Objects combine cheap serverless execution, persistent state, WebSockets, and a high-level JavaScript interface, and Dahl argues that set of properties maps well onto agent harnesses, long-lived processes that hold state and talk over sockets. celld is built around Durable Objects for that reason. Dahl’s joint post with Kenton Varda covers it, and he’s asking people building agents at scale who want to run on their own infrastructure to contact him at [email protected].

For a team standing on Deno today, the runtime is not disappearing, but the people who wrote it are leaving, and the paid hosting is on a six-month clock. Node compatibility was one of Deno’s selling points, which gives migrations an escape hatch that does not necessarily route through Cloudflare. The open-source license guarantees the code survives. It does not guarantee anyone keeps shipping security fixes once the year is up.