Cloudflare Acquires Deno to Make Workers Easier to Run Anywhere

Cloudflare is acquiring Deno, the startup behind the Deno programming runtime. The transaction was announced on October 9, 2026, in parallel posts from both companies titled "Deno is joining Cloudflare," and reported on October 10, 2026. TechCrunch

Financial terms were not disclosed. Deno had raised a total of $26 million, with its Series A round led by Sequoia. The entire Deno team is joining Cloudflare as part of the deal.

Deno was co-founded by Bert Belder and Node.js creator Ryan Dahl. Before the acquisition, Deno had launched celld, an open source implementation of Workers that developers can inspect and run themselves. Cloudflare said it plans to bring celld and workerd, its own Workers runtime, together as Deno joins the company. Cloudflare

The stated objective is to improve the Workers programming model and platform. Workers allows customers to build and run software on Cloudflare's network rather than on their own servers. Cloudflare's Workers engineering effort includes principal engineer Kenton Varda.

More specifically, the Deno team is joining Cloudflare to simplify self-hosting Workers and Durable Objects. Durable Objects are Cloudflare's building blocks for software that needs to keep track of state. Cloudflare said developers will be able to use the same Workers and Durable Objects primitives, the basic parts, in more places. Deno said its team will combine its work with Cloudflare's Workers and Durable Objects teams, with the goal of making the programming model usable both on Cloudflare's network and on developers' own infrastructure. Deno

Ryan Dahl said the Deno team is joining Cloudflare "to make the Workers programming model a mainstream way to build servers." Deno subtitled its announcement "Putting ourselves in the best place to build the future of the web."

The broader context here is portability without forcing developers to maintain two versions. Self-hosted Workers and Durable Objects have been usable. But keeping a managed edge runtime and code running on a developer's own infrastructure in sync is operationally difficult. Small differences in interfaces, behavior under load, and separate tools tend to accumulate. A converged celld and workerd codebase addresses that maintenance problem directly.

In my view, the hiring matters as much as the code. Small runtime teams that join larger platform organizations can struggle with different release schedules and compatibility requirements. Here the structure described is explicit combination of the Deno team with the existing Workers and Durable Objects teams, rather than a separate side project. That gives the portability work a clearer path into the core parts instead of leaving it as an outside compatibility layer.

For teams building on Workers today, it is worth flagging the scope of the promise. The goal articulated is same primitives in more places, on Cloudflare's network and on owned infrastructure. For architects weighing stateful edge patterns, durable execution, and local development, that is the metric to watch. If celld and workerd convergence delivers identical behavior for Workers and Durable Objects across environments, local testing, disaster recovery options, and hybrid deployments all get simpler. If differences persist, developers will continue to treat self-hosting as adjacent rather than equivalent.

Looking at the longer term, the picture is encouraging. A widely used server programming model that runs unchanged across a global network and a single machine would lower the cost of starting small and scaling out. That is the kind of infrastructure consolidation that lets small teams use capabilities once reserved for platform groups.