Cloudflare Acquires Deno to Integrate Durable Objects and celld into its Edge Platform

Cloudflare has acquired Deno, the secure JavaScript and TypeScript runtime originally created by Node.js founder Ryan Dahl, to merge its distributed computing architecture directly into the Cloudflare Workers platform. The deal integrates Deno’s open-source celld project into Cloudflare’s infrastructure, allowing developers to run distributed applications on their own hardware, while “Deno Deploy will shut down after six months” and the core Deno runtime will receive one additional year of support.

How Cloudflare and Deno are merging Durable Objects

Cloudflare’s Durable Objects provide a powerful abstraction described as a distributed singleton with a SQLite database. Each object acts as an individually addressable server with local relational storage, single-threaded JavaScript execution, and native WebSocket handling. While Cloudflare’s workerd runtime is already open source, its Durable Objects support was previously limited to a single instance. Deno’s celld project solves this by providing the distributed version, handling placement, routing, and durable storage across multiple machines. By bringing celld and workerd together, the combined entity aims to make the Workers programming model a standard way to build and operate distributed servers outside of Cloudflare’s proprietary network.

Why Ryan Dahl built celld before joining Cloudflare

The architectural shift traces back to Dahl’s early experiments with Node.js, which he originally introduced using a 500-line JavaScript IRC server. He later created Deno to improve the JavaScript development experience, but found that the surrounding infrastructure for networked applications remained complex. Building and operating Deno Deploy exposed the team to the realities of managing multiple public clouds, databases, and deeply entangled services.

celld was engineered as the antithesis of that complexity: a single binary written in Rust, requiring only an object storage bucket as an external dependency.

"What excites me is the leverage this model gives developers: compute, relational databases, queues, and real-time communication primitives designed for applications distributed across machines." — Ryan Dahl, via the Cloudflare blog

What the acquisition means for Deno Deploy and runtime users

The transition timeline requires immediate action for current users. Developers relying on Deno Deploy have a six-month window to migrate their workloads, while those using the standalone Deno runtime have one year before official support concludes. The acquisition also directly addresses long-standing industry debates regarding vendor lock-in. Kenton Varda, a key engineer at Cloudflare, noted the popular theory that the company designed Workers to trap developers, particularly those using Durable Objects. By open-sourcing the distributed capabilities through celld, Cloudflare is providing a migration path that allows applications to run on alternative infrastructure. Furthermore, developers already using community tools like Denoflare to develop and deploy Cloudflare Workers will benefit from tighter alignment, as Deno’s secure-by-default design and native ESM module support make it a natural fit for the Workers environment (LogRocket).

How Cloudflare Workers and Durable Objects shift the serverless landscape

Historically, serverless platforms like Cloudflare Workers and Deno Deploy relied on ephemeral execution models. In this architecture, the process serving a client request is not long-lived, and consecutive requests might be handled by entirely different isolates (Hacker News). This ephemeral nature forces developers to rely heavily on external, centralized databases to maintain state, adding latency and infrastructure overhead.

By standardizing Durable Objects via celld, this acquisition shifts the paradigm toward stateful edge computing. Developers can now build applications with local SQLite databases and persistent WebSocket connections directly within the compute isolate. This reduces the need for complex external service orchestration, offering a practical middle ground between traditional long-lived server processes and purely ephemeral serverless functions, ultimately redefining how distributed state is managed at the edge.