The news
Deno joins Cloudflare: on October 9, 2026, Deno, the company behind the Deno JavaScript runtime, said its team is joining Cloudflare (NET), with a mission to make Cloudflare's Workers programming model a mainstream way to build servers, including on companies' own hardware.
The news came in a Cloudflare blog post written by Ryan Dahl, who created both Node.js and Deno, and Kenton Varda, a Distinguished Engineer at Cloudflare. Dahl becomes a Senior Principal Engineer at Cloudflare. Deno co-creator Bert Belder is also part of the effort. Neither company disclosed a price or other terms, and the post describes the team as joining rather than using the word acquisition.
The technical center of the move is celld, an open-source implementation of Workers and Durable Objects built by the Deno team. According to the post, celld is a single binary written in Rust whose only outside dependency is object storage, and it spreads Durable Objects (Cloudflare's building block for stateful apps) across many machines while handling placement, routing and storage.
Cloudflare said celld's ideas will be merged into workerd, the open-source runtime that powers Cloudflare Workers. Varda wrote that workerd is the same code Cloudflare runs in production. Dahl and Belder will lead a new effort to make self-hosting workerd a first-class, supported way to run Workers applications.
Varda also took on the lock-in question directly, arguing in the post that being open source and giving customers an escape hatch is good business. Deno's own blog now carries a banner announcing the move, and its most recent runtime release, Deno 2.9, came out on June 25, 2026. The Cloudflare post did not say what changes, if any, are planned for Deno's hosted service, Deno Deploy, or the JSR package registry.
The numbers
- Deal price
- Not disclosed
- Announcement date
- October 9, 2026
- Latest Deno release before the move
- Deno 2.9, June 25, 2026
Why CEOs should care
For CTOs and platform leaders, the main promise is portability. Serverless platforms are fast to build on but tend to tie code to one provider. If Cloudflare delivers a supported way to run Workers and Durable Objects on your own servers, the same code could run in Cloudflare's network, in a private data center or in a regulated environment. Ask your Cloudflare account team for a timeline, a support model for self-hosted workerd, and which features will differ between the hosted and self-hosted versions.
Teams that run on Deno or Deno Deploy should ask direct questions now, because the announcement did not address them. What is the roadmap for Deno Deploy? Will the Deno runtime and JSR keep their current release pace and open-source governance? Is there a migration path into Workers, and on what pricing? Get answers in writing before renewing contracts or starting large new projects.
For CFOs and procurement teams, a credible exit option strengthens negotiating power even if you never use it. A supported self-hosted path is a reason to revisit serverless contracts with any provider, and to ask competing clouds what portability they offer.
The bigger picture
Cloudflare has spent years building a full developer platform around Workers, its compute service that runs code close to users across its network, alongside storage and database products. Hiring the team behind a rival runtime, and the creator of Node.js, adds credibility as it competes with the largest cloud providers for application workloads. The self-hosting pitch also answers a common objection from large enterprises: that adopting a single vendor's runtime is a one-way door.
What’s next
Watch for a public roadmap for celld and self-hosted workerd, for clarity on Deno Deploy and JSR, and for whether Cloudflare prices or packages support for self-hosted deployments. Customers should also watch whether the Deno runtime keeps shipping on its own schedule.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error
Companies in this story
