Published: October 10, 2026 | Reading Time: ~5 minutes | Channel: techminute
On Friday, October 9, the entire Deno team announced it is joining Cloudflare — and the fine print landed like a trapdoor: the Deno runtime gets just one more year of monthly maintenance before official development ends, Deno Deploy shuts down in six months, and the team's energy shifts entirely to merging celld — Deno's newest project — into Cloudflare's workerd runtime. The announcement hit #1 on Hacker News within hours and was still sitting on the front page a day later with 1,273 points and 655 comments. Ryan Dahl, the man who invented server-side JavaScript twice, has effectively conceded that the standalone-runtime war is over.
From Deno's own announcement, posted October 9 by Dahl himself:
Deal terms were not disclosed. Neither announcement names a price, and no one should invent one.
The numbers behind the wound-down project are striking: the Deno GitHub repo sits at 108,718 stars and 6,424 forks — a genuinely beloved project by any measure, created back in May 2018. It's not dying of irrelevance. It's dying of geometry.
The actual acquisition target isn't the runtime at all. It's celld — "self-hosted, distributed Durable Objects," released in August, already at 5,320 stars, written in Rust as a single binary whose only external dependency is an object storage bucket.
Here's the context. Cloudflare's Durable Objects are the quietly brilliant core of Workers: each one is an addressable, single-threaded JavaScript server with its own synchronous SQLite database and WebSocket support. Build a chat app with one DO per channel and you've sharded your data and connections by design — scaling is in the programming model, not in an infrastructure project you assemble at 2 a.m. The problem, as Cloudflare's Kenton Varda admits in a candid co-post: workerd, the open-source Workers runtime, has only ever supported Durable Objects in a single-instance mode — fine for local testing, useless for scale. There are, in his words, TODO comments in the code going back to the original release. Varda even attempted a distributed version last spring; "embarrassingly, it didn't work."
Then the team that built Node.js and Deno shipped exactly that missing piece — as an open-source, self-hostable implementation of Cloudflare's own programming model. Varda: "Deno Land was building it for us!" Celld now merges into workerd, with Dahl and Deno co-founder Bert Belder leading a new effort to make workerd self-hosting "a first-class supported way" to run Workers-style apps on your own hardware. Dahl's ask is characteristically direct: if you're building agents at scale and want them on your own infrastructure, email him — now at [email protected].
The most honest sentence of the whole affair came from Dahl in a Hacker News comment — Simon Willison's writeup collects it:
"It ultimately is not solving big problems. It has been sucked into the gravity well of node compatibility, which forces it to behave exactly as Node does. Why reimplement Node? It works. Marginal performance or UX or security benefits are not enough."
That's the creator of Node.js explaining why a second runtime can't exist next to the first. Deno launched in 2018 as "Node done right" — secure by default, TypeScript native, web-standard APIs. To survive, it spent years adding npm and Node compatibility, until it had to behave like the thing it was built to replace. Meanwhile Node absorbed Deno's best idea: a permissions model shipped in Node v20 in April 2023 and declared stable in v22.13.0 in January 2025 (Node still lacks Deno's per-host network allowlisting). There's real melancholy here — and some irony in Dahl saying he's most excited about Durable Objects for agent harnesses: cheap serverless execution, persistent state, WebSockets, one JavaScript interface. The runtime lost; the ideas got absorbed.
Varda's half of the joint post is a direct rebuttal of the internet's favorite Workers theory — that Durable Objects are a lock-in trap. His argument: Workers is different because it's better, the architecture is genuinely more efficient, and the escape hatch has existed since 2022, when customers like Shopify said they couldn't build on Workers-for-Platforms unless the runtime was open source. "Being open source and giving people an escape hatch is good business." He concedes the self-hosting ecosystem around workerd never materialized — which is precisely the gap celld fills. His promised proof of confidence: "I will personally be using it to host an instance of Cloudflare OS in my home."
Skeptics will note that an escape hatch you have to be an elite infrastructure company to operate isn't much of one — until now, maybe. Watch the workerd repo, not the press releases.
All claims verified against Gold-tier sources (official Deno and Cloudflare announcements, GitHub API data, Hacker News Algolia API) and Silver-tier sources (Simon Willison, The New Stack) on October 10, 2026. Each source URL was scraped and confirmed accessible. Community-sourced claims are labeled as such. Deal price: not disclosed by either party.
