Cloudflare acquires Deno to strengthen Workers' programming model
Cloudflare announced the acquisition of Deno, creator of the JavaScript runtime of the same name and co-founded by the creator of Node.js, to accelerate the evolution of the programming model behind Cloudflare Workers.
Cloudflare closes the deal to acquire Deno
Cloudflare announced on Friday, October 9, 2026, the acquisition of Deno, the startup behind the JavaScript and TypeScript runtime of the same name. The announcement was confirmed by Kenton Varda, principal engineer at Cloudflare Workers, and reported by TechCrunch. The financial terms of the deal were not disclosed.
According to Varda, the goal of the acquisition is to use Deno's team and technology to improve the programming model and the platform of Cloudflare Workers, the service that lets developers build and run software on Cloudflare's edge network.
Who is Deno and why it matters
Deno was co-founded by Bert Belder and Ryan Dahl, the same creator of Node.js. The runtime set out to fix design decisions from Node.js: native TypeScript support, a more restrictive permissions model by default, and greater compatibility with browser Web APIs. The startup had raised $26 million in total, including a Series A round led by Sequoia.
Recently, Deno released celld, an open-source implementation of the Cloudflare Workers model. According to Varda, the project impressed Cloudflare's team a great deal.
The lock-in debate
Varda used the announcement to push back on a recurring criticism of Cloudflare Workers: that the company had deliberately designed a programming model different from other clouds to lock customers into the platform. He argued the opposite.
Being open source and giving people an escape hatch is good business.
Kenton Varda, principal engineer at Cloudflare Workers
Ryan Dahl commented on the acquisition along the same lines:
joining Cloudflare to make the Workers programming model a mainstream way to build servers.
Ryan Dahl, co-founder of Deno and creator of Node.js
What changes for those running JavaScript at the edge
For those already using Cloudflare Workers, the most immediate practical effect is organizational: the team that built Deno, and before that helped create Node.js, now works directly on the runtime that powers Workers. This should accelerate the evolution of supported Web APIs, the performance of V8 isolates, and compatibility with existing Node.js code, an area where Deno had already invested heavily.
For those using Deno as a standalone runtime, whether running scripts, APIs, or services outside Cloudflare, the picture is less clear. The materials released talk about improving the Workers model, not about continuing to develop the Deno runtime as a standalone product.
What remains unclear
TechCrunch does not confirm, and Cloudflare has not publicly detailed, what happens to the deno runtime as a standalone project, outside the context of Workers.
Dahl describes the team's goal as making the Workers programming model mainstream, not the Deno runtime itself. That's a hint about where the team's focus will likely shift going forward, but it's not confirmation that anything is being discontinued. As of this writing, there is no formal statement about the runtime's future outside Cloudflare.
Why this matters outside the United States
Cloudflare Workers is one of the edge computing platforms most widely used by Brazilian developers, given the reach of Cloudflare's global network. For those who depend on Workers or closely follow the ecosystem of JavaScript runtimes positioned as alternatives to Node.js, the Deno acquisition is another sign of market consolidation, even though no concrete technical changes have been announced so far.
The move also reinforces a trend of consolidation between edge computing platforms and JavaScript runtimes positioned as alternatives to Node.js: after years of competition between Deno, Bun, and Node.js itself for developer mindshare, one of the contenders has just been absorbed by one of the world's largest edge infrastructure players.
Translated from the Brazilian Portuguese original · Read the original
WSL3 Is Up to 61% Faster Than WSL2 in Memory, But Only 4% in Real-World Builds
An independent benchmark compared WSL's kernel 6.6 and kernel 6.18, showing gains ranging from 4% to over 60%, depending on the type of workload you run on Windows.