Cloudflare Acquires Deno

October 9, 2026

Cloudflare is acquiring Deno. Ryan Dahl announced it today on the Deno blog: the entire Deno team is joining Cloudflare to merge their runtime work with Cloudflare Workers and Durable Objects.[1] The HN post has 817 points and climbing.

This is a big deal for JavaScript infrastructure. Deno was Dahl's do-over of Node.js, launched in 2018 with TypeScript support, a standard library, and a permission-based security model. It was supposed to fix everything Node got wrong. Eight years later, it is joining the company that runs a significant chunk of the internet's edge compute.

Why Cloudflare Wants Deno

Cloudflare Workers already runs JavaScript at the edge using V8 isolates. But Workers has a constrained programming model. You write single functions, not full servers. Deno brings a complete runtime with file system access, subprocess support, and a module system. Combining the two gives Cloudflare a story that goes beyond serverless functions to full edge applications.[1]

Dahl's post mentions "celld," a system he was building to simplify the infrastructure layer under Deno Deploy. The idea is to make distributed applications as straightforward to write as single-process ones, with scaling built into the programming model rather than bolted on with Kubernetes and load balancers. That work will now happen inside Cloudflare, combined with Workers and Durable Objects.[1]

What Happens to Deno

Dahl says the Deno team will put their future development into the combined platform rather than continuing a separate runtime. Deno Deploy, the commercial hosting service, will presumably fold into Cloudflare's offering. The open source Deno runtime will continue, but the strategic direction shifts.[1]

This is the part that will worry Deno users. Open source projects acquired by large companies have a mixed track record. Sometimes the acquisition accelerates development (React at Meta). Sometimes the project slowly dies (too many examples to list). Deno's community will be watching closely to see whether the runtime gets sustained investment or becomes a footnote in Cloudflare's enterprise pitch.

The Node.js Angle

The irony is thick. Dahl created Node.js in 2009, left the project over disagreements about its direction, and built Deno as a clean-slate alternative. Now Node.js is the most widely used JavaScript runtime in the world, and Deno is being absorbed into an edge computing company. The runtime Dahl built to replace Node may end up as a feature inside a platform rather than a standalone product.[2]

But that might be the right outcome. The standalone runtime market is brutal. Bun raised money to compete on speed. Node keeps adding features (native TypeScript support is coming). Deno could not win on runtime merits alone, because the runtimes are all good enough now. The differentiator became infrastructure, and that is Cloudflare's core business.

The Bigger Picture

This acquisition continues the consolidation of JavaScript infrastructure. Vercel acquired Turbopack's predecessor and builds Next.js. Cloudflare has Workers, now Deno. Bun has its own runtime and bundler. The era of independent JavaScript runtimes competing purely on technical merits is ending. The competition is now between platforms: Vercel, Cloudflare, Bun, and whoever else builds the full stack from runtime to deployment.

For developers, this is probably fine. More integrated platforms mean fewer moving parts. The tradeoff is lock-in. When your runtime, your deploy target, and your CDN are all the same company, switching costs get high. That is the deal Cloudflare is betting developers will accept in exchange for simplicity.[1]

Footnotes

[1] Deno Blog: Deno is joining Cloudflare
[2] Wikipedia: Node.js