Deno joins Cloudflare: what the Celld era means for the JavaScript runtime
On October 9, Ryan Dahl announced that the entire Deno team is joining Cloudflare. The friendly part: Dahl and co-founder Bert Belder will pour their energy into Celld, the distributed-app platform Deno launched in August, merging it into workerd, Cloudflare's open-source Workers runtime. The harder headline: development of the Deno runtime itself ends in about a year.
What Celld actually is
Celld is a platform built on the Cloudflare Workers programming model, with Durable Objects, for building distributed applications — compute, storage, and communication together. It ships as a single Rust binary: run several instances against one object-storage bucket, and the software handles placement, routing, and persistence.
The point: scaling lives in the programming model, not in infrastructure each app assembles itself. Each Durable Object is a small, addressable server with its own SQLite database, single-threaded JavaScript, and WebSocket support. One object per chat channel shards both data and connections. The same pattern fits persistent, real-time apps — collaborative editors, or a tiny virtual pet that keeps its state across sessions.
Dahl frames it as an inevitability: Deno, then Deno Deploy, then Celld. Operating Deploy taught him how complicated cloud infrastructure gets — multiple clouds, multiple databases, deeply entangled services. Celld strips all that out. The goal, he wrote, is to make the Workers programming model "the default way to build servers, whether you run on Cloudflare's network or your own infrastructure."
What Cloudflare gets
Cloudflare's workerd has been open source since 2022 but awkward to self-host. Kenton Varda admitted the company "never quite cracked" the developer experience around a self-hosted runtime; workerd's Durable Objects ran as a single instance — fine for local testing, not production. Celld solves exactly that gap. Dahl and Belder will lead the merge of the two projects, and the result is expected to stay open source.
What happens to Deno
The timeline from the announcement:
- The Deno runtime gets one more year of monthly releases with bug fixes and security updates — 2.9.x LTS through October 2027 — then development ends. The code stays MIT-licensed and the team welcomes community maintainers. Dahl on Hacker News: "If people want to carry it forward, I'd like that."
- Deno Deploy keeps running for six months, then shuts down. Paying customers get migration support to Cloudflare Workers.
- JSR, the TypeScript-first package registry, continues operating; its infrastructure moves to Cloudflare.
- rusty_v8 work continues, aiming for integration into workerd.
The timing stings
Deno 2.9 shipped on June 25 with deno desktop — native desktop apps from the web stack, no Electron boilerplate — and deno install now reads npm, pnpm, yarn, and Bun lockfiles directly. A few months earlier the runtime looked like it was expanding, not winding down. Teams that bet on Deno for its built-in TypeScript and clean tooling now face a year of maintenance followed by a community-maintained future.
A consolidating market
The bigger story: the independent JavaScript runtime is a lonely category now. Deno's team goes to Cloudflare, Bun's to Anthropic, and Cloudflare itself bought VoidZero, the company behind Vite, in June. Node.js 26 remains the active LTS — the gravity well that, as Dahl now says, pulled Deno into near-total Node compatibility. His conclusion is blunt: reimplementing Node is not the interesting problem anymore. Distributed state is.
For developers, the path is clear. Deno keeps working, gets a year of fixes, and stays MIT. If you are on Deno Deploy, plan the move to Workers while migration help exists. And watch workerd — the interesting work is moving there, where the runtime is a detail and the programming model is the product.