Cloudflare is acquiring the Deno team to make its Workers programming model easier to run outside Cloudflare’s network. The companies announced on October 9, 2026, that the team will work on combining celld, Deno’s self-hosting project for distributed applications, with workerd, Cloudflare’s open-source Workers runtime. The goal is to let developers run Workers and Durable Objects on infrastructure they operate themselves.
The announcement also changes the road map for Deno’s existing products. Deno says it will continue maintaining its standalone runtime for another year, then end its own runtime development. Deno Deploy will continue operating for six months before shutting down, while JSR, its JavaScript and TypeScript package registry, will continue with its infrastructure moving to Cloudflare.
Why Cloudflare wants to combine celld and workerd
Cloudflare Workers lets developers run JavaScript and WebAssembly code in isolated environments across Cloudflare’s network. Its open-source runtime, workerd, can also run outside that network, but Cloudflare says its current Durable Objects implementation is limited to a single instance and is not designed for distributed self-hosting at production scale.
Durable Objects give an application a way to associate code with persistent state. Each object can handle requests and WebSocket connections while accessing its own SQLite database. That can simplify features such as real-time collaboration, chat rooms, and applications that need a consistent state for a particular user or group.
Deno created celld to address the operational side of running this model on a developer’s own infrastructure. Cloudflare says the combined effort will bring celld’s ideas and code into workerd and make self-hosting a supported way to build and operate applications using the Workers programming model. The companies have not announced a release date for the combined work.
What self-hosted Workers could mean for developers
Self-hosting could give teams more control over where their applications run and how they manage their infrastructure, while retaining programming concepts used by Cloudflare Workers. It could also make it easier to operate distributed applications that need compute, persistent data, queues, and real-time communication without assembling each component as a separate infrastructure project.
That does not mean every Workers application can move to any server today without changes. The announced work is intended to improve self-hosting, and the final compatibility, deployment process, operational requirements, and supported configurations remain to be detailed.
Developers following Cloudflare’s broader work on software for AI agents can also read Saganote’s coverage of Cloudflare Kitesurf, a browser designed for AI agents. For background on another portable runtime technology, see What Is WebAssembly and Why Do Developers Care?.
What happens to Deno Runtime and Deno Deploy?
Deno’s announcement gives its current products different timelines. The company says:
- Deno runtime: Monthly releases with bug fixes and security updates will continue for another year. Deno will remain open source, and the company says other developers can continue its development after that period.
- Deno Deploy: The hosted service will continue operating for six months before shutting down. Deno says it will provide migration support for paying customers moving to Cloudflare Workers.
- JSR: The package registry will continue operating, with its infrastructure moving to Cloudflare.
- rusty_v8: Deno says it will continue supporting the Rust bindings for V8 and work toward integrating them into workerd.
For developers running production workloads on Deno Deploy, the six-month shutdown timeline is the most immediate planning issue. Teams should review their deployment setup and watch for migration guidance rather than assume that moving to Workers will require no code or configuration changes.
Why the deal is about more than a JavaScript runtime
Deno began as an alternative JavaScript and TypeScript runtime with its own tooling and security model. Its work later expanded into hosting applications through Deno Deploy and into celld, which focuses on operating distributed applications with fewer infrastructure dependencies. The Cloudflare announcement puts the team’s future development effort behind the Workers and Durable Objects model instead of continuing to build a separate runtime and hosting platform.
Cloudflare’s announcement frames the work around making its programming model easier to run on developers’ own infrastructure, not simply adding another runtime to its product lineup. That could broaden the environments where Workers-style applications can operate, but the practical impact will depend on the implementation details and support that emerge in the coming months.
The companies say further details will follow. For now, the confirmed changes are the planned celld and workerd integration, the Deno runtime maintenance period, the Deno Deploy shutdown timeline, and JSR’s continuation under Cloudflare infrastructure.
