Cloudflare Acquires Deno: Standalone Runtime Deprecated in 12-Month Sunset as Engineering Merges with Workers
The entire Deno team is joining Cloudflare to integrate their work with the Cloudflare Workers and Durable Objects platforms, ending development on the standalone Deno runtime after a one-year maintenance window. Deno Deploy will shut down in six months, while JSR infrastructure and `rusty_v8` integration effort will transition into Cloudflare's ecosystem.
Platform Consolidation and Strategic Shift
On October 9, 2026, Deno founder Ryan Dahl announced that the entire Deno team is joining Cloudflare. The acquisition marks a definitive shift away from maintaining a standalone JavaScript runtime and independent cloud hosting platform. Instead, the team will integrate their distributed runtime engineering with Cloudflare’s Workers and Durable Objects organizations.
The transition follows the team's internal development of `celld`, a project built on top of the Cloudflare Workers programming model designed to handle distributed applications with native scaling primitives. The combined team plans to advance this combined model as a standard for building backend services across both Cloudflare’s managed network and self-hosted infrastructure.
Runtime Deprecation and Infrastructure Timelines
The transition introduces explicit sunset schedules and operational changes for Deno's core software portfolio:
- Deno Runtime: Maintained for 12 additional months, receiving monthly point releases restricted to bug fixes and security patches. Primary development by the original authors will cease after one year, though the repository remains open-source for community forks.
- Deno Deploy: Fully shuts down in six months. Paying customers will receive technical migration support to shift workloads to Cloudflare Workers.
- JSR (Package Registry): Remains operational as a TypeScript-first ESM registry, with primary infrastructure operations transferring to Cloudflare.
- rusty_v8: Core engineering support continues, with active effort shifting toward integrating `rusty_v8` bindings directly into `workerd`.
Runtime Integration for Stateful Agents and Workerd
A major technical objective of the acquisition is optimizing execution runtimes for AI agent workloads. These agent harnesses demand tight coupling between ephemeral, low-cost serverless compute, persistent state, WebSockets, and high-level JavaScript runtime environments.
Rather than requiring operators to assemble decoupled storage, compute, and networking layers, the team is focusing development on Durable Objects and `workerd`. Combining Deno's runtime abstractions with Cloudflare's edge execution layer aims to provide a unified programming target for stateful, distributed microservices.