Key points
- Cloudflare is acquiring the Deno team, with plans to cease runtime development after one year of support.
- Deno Deploy will shut down in six months, with paying customers migrating to Cloudflare Workers.
- Creator Ryan Dahl announced the move on October 9, reversing previous assurances about the project's growth.
Cloudflare is acquiring the team behind the Deno runtime, a decision that ends the project’s active development after one final year of bug fixes and security updates. This acquisition signals a definitive shift for the JavaScript and TypeScript environment, leaving the broader community to determine its future. The move has sparked immediate concern among developers who relied on the platform’s stability and independent stewardship.
How it unfolded
- On October 9, Ryan Dahl, the creator of Deno and Node.js, announced that the entire Deno team is joining Cloudflare.
- Eight days prior, on October 1, Dahl discussed celld, an open source project that combines JavaScript execution with persistent state.
- In August, Deno released celld, which Cloudflare identified as a solution for scalable self-hosting of its Workers model.
Who is affected
Developers who built applications on Deno face uncertainty about the long-term viability of their infrastructure. The runtime gained popularity by simplifying TypeScript development through built-in formatting, linting, and testing tools. Its security model also allowed developers to restrict code access to files, networks, and environment variables by default. The sudden end of development disrupts teams that depended on these integrated features and the project’s previously stated commitment to growth.
View the original post on X
View the original post on X
What happens next
Deno will provide monthly bug fixes and security updates for twelve months before ending support entirely. Deno Deploy will shut down in six months, with migration assistance available for paying customers moving to Cloudflare Workers. The acquisition centers on celld, an implementation of the Workers and Durable Objects programming model. Cloudflare viewed celld as a way to fill a gap in its open source workerd runtime, which lacked distributed implementation for self-hosting.
The background in plain language
Open source software often relies on community contributions or corporate sponsorship to survive. When a company acquires a team, the project’s goals may shift to align with the buyer’s commercial interests. Runtimes like Deno provide the environment for code to execute, so ending development means no new features or security patches. Teams using such tools must assess their dependency level and prepare for potential migration to alternative platforms or community-maintained forks.
What to do and how to stay safe: Deno
- Audit your infrastructure to identify all services and applications currently running on the Deno runtime.
- Review your deployment strategy to determine if you rely on Deno Deploy or self-hosted Deno instances.
- Monitor official communication channels for migration guides and timelines regarding the shift to Cloudflare Workers.
- Evaluate alternative runtimes or community forks that may emerge to maintain the software’s functionality.
Step-by-step guide: Mobile Device Security for Small Business: Control Without Cost
General security guidance from the Circuit Observer newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
When will Deno stop receiving updates?
Deno will receive bug fixes and security updates for one year after the acquisition before support ends.
What happens to Deno Deploy?
Deno Deploy will shut down in six months, with migration assistance provided for paying customers.
Why is Cloudflare acquiring the Deno team?
Cloudflare is acquiring the team primarily for celld, a project that enables self-hosting of Workers and Durable Objects.
