Deno team joins Cloudflare: runtime gets one more year, Deploy six months
Victoria Shinder2 min readThe whole Deno team is joining Cloudflare, Ryan Dahl and Kenton Varda announced on 9 October in a joint post on the Cloudflare blog, with a companion post on the Deno blog that spells out what happens to existing Deno users.
What the move is for. In August the Deno team released celld, an open-source, self-hostable implementation of the Cloudflare Workers programming model with distributed Durable Objects — one Rust binary whose only external dependency is an object storage bucket. Cloudflare's own runtime, workerd, is already open source and is the same code Cloudflare runs in production, but Varda concedes its Durable Objects support has always been single-instance: good for local testing, not for scale. The plan is to merge celld's ideas back into workerd, with Dahl and Bert Belder leading an effort to make self-hosted workerd "a first-class supported way" to run Workers apps.
What it means if you run Deno today — the concrete list from Dahl's post:
- Deno runtime: one more year of monthly releases with bug fixes and security updates. After that, Deno Land ends its development of the runtime; it stays open source for anyone who wants to continue it.
- Deno Deploy: keeps operating for six months, then shuts down. Paying customers get migration support to Cloudflare Workers.
- JSR, the package registry: continues, with its infrastructure moving to Cloudflare.
- rusty_v8: still supported, and the team will work toward integrating it into workerd.
The lock-in argument. Varda uses the post to answer the common claim that Workers is different from other platforms in order to trap customers. His counter: Workers for Platforms customers such as Shopify would not sign in 2022 unless the runtime was open source, so Cloudflare open-sourced it — and some former customers have since left by running workerd themselves. What was missing, he writes, was the surrounding tooling and a scalable Durable Objects story; that is the gap the Deno team is hired to close.
What to do now. If you deploy on Deno Deploy, you have a six-month clock: inventory what depends on Deploy-specific APIs (KV, cron, queues) and decide between Workers and another host. If you run the Deno runtime on your own servers, nothing breaks today, but a one-year support horizon belongs in your platform roadmap — Node.js compatibility work you did for Deno is the obvious bridge. If you were waiting for a credible self-hosted Durable Objects, celld and workerd are both available to try now; Cloudflare promises more announcements "in the coming months".
Sources: Cloudflare Blog, "Deno is joining Cloudflare", 9 October 2026 — https://blog.cloudflare.com/deno-joins-cloudflare ; Deno Blog, "Deno is joining Cloudflare", 9 October 2026 — https://deno.com/blog/cloudflare