Cloudflare Acquires Deno to Strengthen Its Developer Platform

Cloudflare announced on October 9, 2026 that the entire Deno team is joining the company.** The move brings the people behind one of the best-known JavaScript runtimes into the business that runs the Workers serverless platform.

Both companies published posts the same day. Their wording is "joining." Technology reporting, including TechCrunch's coverage, describes the arrangement as an acquisition.

Who is Deno?

Deno is a runtime: software that lets JavaScript and TypeScript code run on servers and laptops instead of inside a web browser. It was co-founded by Ryan Dahl, the creator of Node.js, and Bert Belder.

Deno set out to rethink parts of server-side JavaScript. Its team says that work covered how modules are distributed, what security a runtime can guarantee, what a complete toolchain should include, and how apps can ship as standalone executables. It also stayed compatible with the Node.js ecosystem.

What Workers brings

Cloudflare Workers lets developers deploy code that runs on Cloudflare's global network without managing servers. Cloudflare says the design makes it simple and inexpensive to operate an application in hundreds of locations.

A related feature, Durable Objects, gives each unit of an application its own small server with a private SQLite database. A chat app, for instance, can assign one object to each channel, which spreads both data and live connections across the network.

The celld and workerd plan

In August, Deno released celld, an open-source implementation of Workers and Durable Objects built for self-hosting. Dahl describes it as a single Rust program whose only outside dependency is an object-storage bucket.

Cloudflare already publishes workerd, an open-source runtime it says is the same code that runs in production. But workerd's Durable Objects work only as a single instance. Cloudflare engineer Kenton Varda says that suits local testing but cannot scale.

Dahl and Belder will now lead an effort to make self-hosting workerd a first-class option, merging code and ideas from celld into it. Cloudflare promised more announcements in the coming months. It has not given a release date or product details.

Why self-hosting matters

Many businesses want the option to run software on their own infrastructure. Common reasons include cost, regulation, data location, or avoiding dependence on one vendor. Open-source runtimes make that option more credible.

Cloudflare addressed the vendor lock-in criticism directly. It argues that Workers is built differently because it is better, and that an open-source escape hatch is good business. That is the company's position. Developers will judge it by how easy self-hosting turns out to be.

Dahl said the goal is to make Workers "a mainstream way to build servers." He also pointed to AI agents as a use case, citing Durable Objects' low-cost execution, persistent state and WebSocket support.

What happens to Deno's products

According to Deno's announcement:

• Deno runtime: Monthly bug-fix and security releases continue for another year. After that, the team will end its development. The code stays open source, and others are welcome to continue it.
• Deno Deploy: The hosting service runs for six months, then shuts down. Paying customers get migration support to Cloudflare Workers.
• JSR: The package registry keeps operating, with its infrastructure moving to Cloudflare.
• rusty_v8: Support continues for Deno's Rust bindings to the V8 engine, with work toward integrating them into workerd.

Possible benefits and open concerns

The benefits below are possibilities, not commitments. A well-resourced, self-hostable Workers runtime could give teams a more portable route to distributed applications. Keeping JSR and rusty_v8 alive also protects pieces that other projects rely on.

The concerns are more concrete. Deno users now face a clear end date for the team's work on the runtime, and Deploy customers face a shorter deadline. Some developers online have described the news as the end of Deno as an independent product. Depending on their needs, teams may weigh Node.js, workerd or a community-maintained version of Deno.

Questions also remain about JSR. The announcement mentions only an infrastructure move.

Financial terms

Neither company has disclosed the financial terms. Reporting notes that Deno had raised $26 million in total, including a Series A led by Sequoia. That figure reflects past funding, not the value of this deal.

What it means for developers

For developers choosing where to run applications, the news points to a Workers-style model of small, stateful units spread across machines. It could run on Cloudflare's network or on a team's own servers. If the promised workerd and celld merger delivers, the choice may become less about lock-in and more about who wants to operate the infrastructure.

Until details arrive, teams on Deno Deploy should start planning migrations. Teams on the Deno runtime should set a review date within the year. Anyone curious about Durable Objects can try self-hosting celld or workerd today, as Cloudflare suggests.