Cloudflare acquires Deno, absorbing Node.js creator's team to rebuild its Workers platform

Cloudflare said Friday it is acquiring Deno, the company behind the open-source JavaScript and TypeScript runtime of the same name, bringing the entire Deno team — including Ryan Dahl, the original creator of Node.js, and co-founder Bert Belder — onto Cloudflare's payroll. The move, announced in twin posts on Cloudflare's and Deno's blogs, folds a decade-long argument over how server-side JavaScript should work into a single engineering effort, and sets a firm shutdown date for a product Deno had spent years building.

Financial terms of the deal were not disclosed. TechCrunch, which reported the news Saturday morning, noted that Deno had raised a total of $26 million, including a $21 million Series A round led by Sequoia in 2022 — money raised specifically to build Deno Deploy, the hosted runtime service that Cloudflare is now closing down.

A fix for a gap Cloudflare left open for years

The technical core of the deal is a merger between two pieces of open-source infrastructure: workerd, the runtime Cloudflare uses to power Workers, its serverless edge-computing platform, and celld, a project the Deno team released in August as a self-hosted implementation of Durable Objects — Cloudflare's model for giving each unit of an application its own small, stateful, single-threaded slice of compute and storage.

In Cloudflare's post, principal engineer Kenton Varda explained why that merger was necessary rather than cosmetic: Cloudflare open-sourced workerd years ago, but it only ever supported running a single Durable Object, fine for local testing but useless at any real scale, because the code that actually places, routes to, and durably stores thousands of distributed objects across Cloudflare's network was never released. "Frankly, we haven't done a great job of building out the ecosystem of adjacent services" needed to self-host Workers, Varda wrote, adding that an earlier internal attempt to close that gap had failed.

Dahl, in Deno's own post, described building celld as a direct response to the operational complexity he had encountered running Deno Deploy himself: one binary, written in Rust, with object storage as its only external service dependency. Rather than keep competing with Cloudflare's hosted product, he is now bringing that design into Cloudflare directly. As he put it in the companies' joint announcement:

"The Deno team is joining Cloudflare, and we're merging workerd and celld! ... We're joining Cloudflare to make the Workers programming model a mainstream way to build servers." — Ryan Dahl, Cloudflare Blog, Oct. 9, 2026

Varda, for his part, used the post to address a recurring criticism of Cloudflare Workers — that its unusual architecture exists to lock developers in. "We built Workers differently because we believe it is a better way to build web applications," he wrote, pointing to Cloudflare's 2022 decision to open-source the runtime after enterprise customers — he named Shopify specifically — said they would only build on Workers for Platforms if the underlying code was open. "It turns out, being open source and giving people an escape hatch is good business," Varda wrote.

Who is affected, and on what timeline

The clearest near-term consequences land on Deno's existing users rather than on Cloudflare's. According to Deno's own announcement, the standalone Deno runtime will continue to receive monthly bug-fix and security-patch releases for one more year before development stops; after that, the project remains open source and Cloudflare is inviting outside contributors to carry it forward. Deno Deploy, the paid hosting service, will keep running for six months before shutting down, and Cloudflare says paying customers will get migration assistance onto Cloudflare Workers. JSR, Deno's package registry, continues operating, with its infrastructure moving onto Cloudflare; support for rusty_v8, the Rust bindings for Chrome's V8 engine that underpin Deno, also continues, with an eye toward folding it into workerd as well.

For the broader developer community, the practical change Cloudflare is promising is that self-hosting the Workers programming model — running the same bindings, Durable Objects and storage primitives Cloudflare runs in its own data centers, but on a company's own servers — becomes a supported, documented path rather than a side project. The celld project on GitHub, which had already drawn more than 5,000 stars since its August release, becomes the starting point for that work, published under an Apache 2.0 license.

How the rivalry became a merger

The two projects' histories are intertwined almost from the start. Dahl built Node.js in 2009 and stepped away from the project in 2012; by 2018 he had grown critical of decisions baked into Node's early design and started Deno as a cleaner alternative, adding a built-in permissions system and native TypeScript support. Deno Deploy, launched commercially in 2022, was for years pitched as the most direct rival to Cloudflare Workers — Dahl himself once named Workers as Deno Deploy's closest competitor. The two companies had even collaborated on shared JavaScript API standards as far back as 2022, a sign the rivalry was never entirely adversarial.

What changed, by Dahl's own account, was his assessment of where the interesting problems in server software now sit — not in the runtime itself, but in distributing computation, coordinating state and autoscaling across machines, problems he felt Durable Objects solved more elegantly than anything Deno had built independently. Developer and open-source commentator Simon Willison, writing shortly after the announcement, flagged a comment attributed to Dahl describing Deno as having been pulled into "the gravity well of node compatibility" — a dynamic that pushed the runtime toward mimicking Node rather than pursuing the kind of new abstractions Durable Objects represent. Willison called Deno's permissions model, which lets a script be restricted to specific files, folders and network hosts, one of its best features, and noted that Node.js has only recently added a comparable system, and a cruder one.

What happens next

Cloudflare has not published a technical roadmap beyond saying more detail is coming "in the coming months," and neither company's post addressed pricing for self-hosted Workers deployments or gave a release date for the merged runtime. Cloudflare also flagged, almost in passing, an interest in agent workloads: Durable Objects' combination of persistent state, WebSocket support and serverless execution is being pitched as a fit for running AI agents at scale on infrastructure a company controls itself, rather than inside a vendor's cloud. For now, the concrete dates are the ones affecting existing Deno customers — a year of maintenance for the runtime, six months of life left for Deno Deploy — while the more consequential promise, a genuinely self-hostable version of Cloudflare's edge-computing model, remains a work in progress.