Cloudflare Acquires Deno Team, Signals End of Runtime Development in One Year
Cloudflare’s acquisition of Deno’s engineering staff brings a year of maintenance updates before the JavaScript runtime ceases active development.
Key points
- Cloudflare is acquiring the entire Deno development team, effective October 9.
- The runtime will receive monthly bug fixes and security patches for twelve months before support ends.
- Deno Deploy will shut down in six months, with paying customers migrating to Cloudflare Workers.
Cloudflare announced on October 9 that it has acquired the entire Deno development team, a move that will end active development of the popular JavaScript and TypeScript runtime within one year. Ryan Dahl, the creator of both Node.js and Deno, confirmed that the team is joining the cloud infrastructure provider, marking a significant shift for the open-source project.
The acquisition includes a commitment to provide monthly bug fixes and security updates for the runtime for another twelve months. After this maintenance period, the team will cease all development work on the software. This timeline gives developers a defined window to plan for the eventual discontinuation of the platform they may rely on for their applications.
View the original post on X
View the original post on X
Strategic Shift and Celld Integration
The deal is driven by Cloudflare’s interest in celld, an open-source project created by Deno that implements the Workers and Durable Objects programming model for self-hosted infrastructure. Celld combines JavaScript execution with persistent state in individually addressable objects backed by SQLite, allowing distributed applications to run with less infrastructure complexity.
Cloudflare identified a gap in its own ecosystem, noting that its open-source runtime, workerd, supported Durable Objects only on single instances. The company’s production implementation relied on proprietary infrastructure that self-hosters could not replicate. According to Cloudflare engineer Kenton Varda, the company had previously released workerd with the hope that the community would build the surrounding ecosystem, a strategy he now acknowledges may have been naive.
Dahl stated that operating Deno Deploy revealed the hidden complexity of hosting services, including multiple clouds and interconnected databases. Celld emerged from his desire to simplify this machinery. When Deno released celld in August, Cloudflare recognized that the team was building exactly what the company needed to fill its self-hosting gap.
Developer Reaction and Forking Efforts
The announcement has sparked significant concern among developers who built applications on Deno, prompting questions about the risks of relying on venture-backed open-source software. Some users expressed feeling misled by the acquisition messaging, which highlighted a partnership between Deno and Cloudflare while burying the news of the runtime’s development end in the fine print.
Community members are already organizing forks to ensure the runtime’s survival under independent stewardship. One Hacker News commenter, who described their investment in the technology as extensive, stated they can no longer trust such projects. Others argued that the situation highlights the fragility of free software, while some pushed back against the complaints, suggesting expectations should be realistic.
This development follows a period of uncertainty for Deno. Less than eighteen months prior, Dahl published a blog post titled “Reports of Deno’s Demise Have Been Greatly Exaggerated” to address concerns about the company’s momentum. At that time, he reported that adoption had more than doubled since the release of Deno 2 and assured users that the team was winding up, not down.
What should you do?
The end of active development means new features and architectural improvements will cease. However, the one-year maintenance window provides time for assessment. Developers should evaluate their dependency on the runtime and consider migration paths to alternative platforms like Node.js or Bun, or potentially to Cloudflare Workers if their workload fits that model.
What to do and how to stay safe: Deno
- Audit all projects currently using Deno to determine their criticality and compatibility with alternative runtimes.
- Review the timeline for Deno Deploy shutdown and plan migration strategies for any hosted services before the six-month deadline.
- Monitor community forks that may emerge, assessing their stability and long-term viability as potential successors to the official runtime.
- Verify that any security updates released during the maintenance period are applied promptly to mitigate risks before support ends.
Step-by-step guide: Mobile Device Security: How to Protect Data Beyond Passwords
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Will Deno receive security updates after Cloudflare acquires the team?
Yes, the runtime will receive monthly bug fixes and security updates for one year after the acquisition before support ends.
When will Deno Deploy shut down?
Deno Deploy will shut down in six months, with migration assistance provided for paying customers moving to Cloudflare Workers.
Why is Cloudflare acquiring the Deno team?
Cloudflare wants the celld project, which allows self-hosted implementation of Workers and Durable Objects, to fill a gap in its infrastructure capabilities.
