Cloudflare Acquires Deno: Deploy Shutdown, Runtime Future

Cloudflare is acquiring Deno, the company behind the JavaScript and TypeScript runtime created by Node.js inventor Ryan Dahl, and the entire Deno team is moving to Cloudflare. The deal was announced on Friday, October 9, 2026, in coordinated posts on the Deno and Cloudflare blogs. Financial terms were not disclosed.

The acquisition effectively ends Deno as an independent platform. The hosted Deno Deploy service will shut down within six months, and the standalone Deno runtime will receive one year of bug-fix and security releases before official development stops. The team’s focus shifts to making Cloudflare’s Workers platform something developers can run on their own servers.

The terms and timelines

According to the two companies’ announcements and coverage by TechCrunch and The New Stack, the deal sets out the following:

• Deno runtime: Monthly bug-fix and security releases continue for 12 months. After that, the Deno team ends its development of the runtime. The code remains open source, leaving the door open to community maintenance.
• Deno Deploy: The serverless hosting service shuts down in six months. Cloudflare says it will provide migration assistance for paying customers, who are being steered to Cloudflare Workers. The companies have not detailed what that assistance includes.
• JSR: The JavaScript Registry, Deno’s TypeScript-first package registry, continues to operate, now on Cloudflare infrastructure.
• Team: Dahl and Deno co-founder Bert Belder will lead the integration work inside Cloudflare.

Deno had raised roughly $26 million in total, including a Series A led by Sequoia Capital.

Why Cloudflare wanted Deno: celld

The strategic asset in the deal is less the Deno runtime than a recent Deno project called celld. Deno’s team released celld as an open-source, Rust-based single binary that runs Workers-style applications — including the stateful Durable Objects model — on a company’s own hardware, with object storage as its only dependency. It is licensed under Apache 2.0.

Under the deal, celld will be merged into workerd, the open-source runtime that powers Cloudflare Workers. Cloudflare said the goal is to make self-hosting Workers and Durable Objects straightforward. Dahl wrote that combining celld and workerd is meant to make distributed applications easy to build and run on one’s own infrastructure.

Cloudflare open-sourced workerd in 2022, but running it outside Cloudflare’s network has been impractical for production use, because much of the surrounding machinery — storage, coordination, deployment — lives inside Cloudflare’s own systems. According to The New Stack, Cloudflare distinguished engineer Kenton Varda, the lead engineer on Workers, acknowledged that the company had not built the tooling needed to make workerd practical off its network.

Varda said the acquisition will strengthen the Workers programming model and platform. Asked about the long-standing criticism that Workers locks customers in, he rejected the idea that the platform was designed to trap users, arguing that being open source and offering an escape hatch is good business, according to TechCrunch’s report.

Why Deno is folding its own platform

Dahl’s explanation centers on convergence. Deno launched in 2018 as a corrective to design choices Dahl said he regretted in Node.js — implicit file and network access, a centralized package manager, no native TypeScript. Over time, however, Deno added extensive Node.js and npm compatibility to win adoption, a shift that culminated in Deno 2 in 2024.

According to coverage of Dahl’s post, that compatibility push meant Deno had effectively become another implementation of the same technology the rest of the ecosystem already ran. Rather than maintain a separate runtime and a separate hosting service, Dahl said, the team will put its work into a shared platform.

Deno Deploy itself had followed Workers’ architecture closely: V8 isolates distributed across a global network, priced per request. The New Stack characterized the deal as Cloudflare acquiring a startup that had copied its serverless playbook.

A short history of Deno

Dahl introduced Deno in a 2018 JSConf EU talk titled 10 Things I Regret About Node.js, presenting it as a clean-slate runtime built on V8, Rust and the Tokio async runtime. Its early pitch was distinct: code ran in a permission sandbox by default and had to be granted explicit flags such as --allow-net or --allow-read; TypeScript ran without a build step; and modules were imported by URL rather than through a central registry.

Deno reached 1.0 in May 2020, and Dahl and Belder formed the Deno Company the following year to build commercial products on top of the open-source runtime. The two main ones were Deno Deploy, a globally distributed serverless host, and Deno KV, a built-in key-value database. The company also maintained Fresh, a web framework built around islands architecture, and launched JSR in 2024 as an alternative to npm designed for TypeScript-first packages.

Adoption stayed well behind Node.js. The release of Deno 2 in October 2024, which leaned heavily into npm and Node compatibility, was widely read as an acknowledgment that developers would not abandon the existing ecosystem to get Deno’s cleaner defaults. Bun, which launched as a speed-focused, Node-compatible runtime, competed for the same audience.

Market reaction

Shares of Cloudflare (NYSE: NET) rose about 6% in afternoon trading after the announcement, according to Yahoo Finance, which described the move as a sign investors saw the news as meaningful but not one that fundamentally changes the company’s outlook.

What happens to Deno users

The practical impact splits along product lines:

• Deno Deploy customers face a hard deadline. Applications built on Deno-specific APIs — such as Deno KV or the Deno.serve handler model — will need porting to Workers or another host within six months. Apps written against web-standard APIs like fetch, Request and Response should move with less effort, since Workers uses the same primitives.
• Runtime users have a year before official updates stop. Teams running Deno in production, for scripts, CLIs or servers, will need to decide whether to stay on a community-maintained fork or move to Node.js or Bun. The relative trade-offs are covered in our comparisons of Deno vs Node.js and Bun vs Deno.
• JSR publishers are unaffected for now, with the registry continuing under Cloudflare.

Developers already deploying to Workers — for example, with a Hono API on Cloudflare Workers — stand to gain if celld delivers a supported way to run the same code on their own servers.

The broader Cloudflare push

The deal extends Cloudflare’s expansion of its developer platform, which has added databases, object storage, queues, AI inference and agent tooling around Workers over the past several years. We tracked that growth in our look at Cloudflare’s expanding developer platform. Acquiring the team behind a rival runtime and its self-hosting technology gives Cloudflare an answer to one of the most common objections enterprises raise about serverless platforms: what happens if they need to leave.

What it means

The JavaScript runtime field narrows to two independent players. With Deno winding down as a standalone project, server-side JavaScript consolidates around Node.js, the incumbent, and Bun, the performance-focused challenger. Deno’s ideas — secure-by-default permissions, built-in TypeScript, web-standard APIs — largely survive, because Node and Bun adopted many of them. But one of the three runtimes driving that competition is leaving the field.

Cloudflare’s real target is lock-in objections, not runtime market share. A self-hostable Workers runtime lets Cloudflare tell large customers that code written for its platform can run in their own data centers. That makes Workers an easier sell, and it gives Cloudflare a credible open-source story against hyperscaler serverless products like AWS Lambda. The risk for Cloudflare is execution: a self-hosted runtime is only useful if the storage, Durable Objects and deployment tooling around it are production-grade.

Deno Deploy users are the clear losers. Six months is a short window for teams with production workloads, and migration help has not been specified. The open question is how much of Deno’s developer goodwill transfers to Cloudflare, and how much leaks to Vercel, Netlify or Bun-based hosts.

What to watch next. The first merged celld-workerd release and its license; Cloudflare’s detailed migration guide for Deno Deploy customers; whether a community group or foundation forms to maintain the Deno runtime past the 12-month cutoff; and whether Deno KV gets a Workers-compatible successor.