Deno team joins Cloudflare, Deno Deploy shuts down in six months
Deno is merging its self-hosted Workers runtime with Cloudflare workerd. Deno Deploy closes in six months and the open-source Deno runtime gets one more year of fixes.
The entire Deno team is joining Cloudflare, Ryan Dahl announced on Deno’s blog on 9 October. The move merges Deno’s self-hosted Workers runtime, celld, with Cloudflare’s own workerd, aiming at one way to build and run apps on the Workers programming model, whether that is hosted on Cloudflare or on your own infrastructure.
For anyone running on Deno’s own platforms, there is now a clock. Deno Deploy keeps operating for six months before it shuts down, and Cloudflare is offering migration help to paying customers who move to Workers. The Deno runtime itself gets one more year of monthly bug fix and security releases before development on it stops, though it stays open source and the community can continue it. JSR, Deno’s package registry, keeps running, with its infrastructure moving to Cloudflare. Support for rusty_v8 continues too, folded into work on integrating it with workerd.
Why it matters: if you deploy on Deno Deploy, you have six months to move, and Workers is the obvious landing spot now that Cloudflare is funding the migration path. If you run the open-source Deno runtime in production, you have a year of official fixes before you are relying on volunteers to keep it patched.
The caveat: the announcement does not say what happens to Deno’s own CLI and developer tooling beyond the runtime itself, or how JSR’s roadmap changes once it sits on Cloudflare’s infrastructure.