Tech • AI • Robotics • Game
Deno is extinct?!
7/10TL;DR
Cloudflare is acquiring the Deno team after the rapid emergence of CelD, an open-source implementation of Workers and Durable Objects, in a deal that effectively ends active development of the Deno runtime while advancing Cloudflare’s push to make its edge model more portable.
KEY POINTS
A two-month turnaround
Ryan Dahl, creator of Node.js and Deno, unveiled CelD on August 5 as a self-hosted, distributed implementation of Durable Objects and Workers. By October 9, Deno announced that its team was joining Cloudflare, with CelD central to the move. The speed of that sequence made the deal unusual even by software industry standards.
Why Deno existed in the first place
Deno began in 2018 as a reaction to design choices in Node.js that Dahl later criticized, especially around package management and security. He had argued that JavaScript should run in a tighter sandbox and that tools such as linters should not automatically gain broad access to a machine or network. Deno was positioned as a fresh start rather than a compatible replacement.
How Deno drifted back toward Node
Over time, market pressure pushed Deno toward Node compatibility. Dahl had once argued that trying to stay compatible would simply recreate Node, yet that is increasingly what happened. By the last year, roughly 50% of commits and about half of generated lines were reportedly tied to Node compatibility work, overshadowing the original ambition to redefine server-side JavaScript.
The durable objects idea
Durable Objects, introduced by Cloudflare in 2021, became a major influence on Dahl’s thinking. The model combines a single-threaded, addressable compute instance with built-in persistent storage, typically backed by SQLite. That lets developers treat each object like a small stateful server, which is easier to reason about than many distributed systems and well suited to chat rooms, collaboration tools and long-lived WebSocket sessions.
What CelD set out to do
CelD was designed to reproduce much of the Cloudflare Workers architecture in open source, including V8-based execution, object storage comparable to R2, SQLite-backed state and experimental containers. It was released under the Apache 2.0 license and presented as a path for running this style of application outside Cloudflare’s network. That directly addressed one of the biggest objections to Durable Objects: fear of vendor lock-in.
Cloudflare’s strategic logic
Rather than treating CelD as a threat, Cloudflare embraced it because a portable implementation lowers adoption risk. Companies can develop against the same architectural model on their own infrastructure, then move workloads to Cloudflare if they want global scale and managed operations. For Cloudflare, that creates a broader on-ramp for developers who would otherwise avoid a platform they could not self-host or easily exit.
What happens to Deno now
The Deno runtime will receive one year of monthly bug-fix and security releases, after which the team plans to stop active development. The code will remain open source for any outside maintainers who want to continue it. Deno Deploy will keep operating for six months, with migration support for paying customers moving to Cloudflare Workers.
Why the reaction has been sharper than usual
Acquisitions of open-source companies often trigger fears that products will be sidelined, but the response here has been stronger because the company openly signaled the end of its own flagship runtime. For users who adopted Deno as a distinct alternative to Node, the announcement confirms that the project’s center of gravity has shifted elsewhere. For Cloudflare and Dahl, however, the move aligns around a shared view of stateful edge computing.
CONCLUSION
The acquisition marks the practical sunset of Deno as a company-led runtime and the elevation of Durable Objects as the more important long-term idea. For Cloudflare, the deal turns a potential portability challenge into a growth strategy built around open-source compatibility.
Ask a question