Confirmed 9 Oct 2026 · Infrastructure A one-minute read

Cloudflare took the Deno team, and Deno's runtime gets one more year of support.

On October 9 the Deno team joined Cloudflare, and Deno Deploy shuts down in 6 months. The runtime gets 12 months of fixes, then development ends; terms were not disclosed.

Until now

Two independent JavaScript runtimes compete, one funded to stay independent.

Now

The edge provider owns both, and one of them has an end date.

Why it matters

Agent-written code has to run somewhere sandboxed, and the runtime is that somewhere. Cloudflare now controls both codebases that compete for the job, and will merge celld into workerd so Workers can be self-hosted. The second runtime does not survive the merge.

Established

  • The whole Deno team joined Cloudflare, announced October 9.
  • Deno runtime support ends after one year of monthly releases.
  • Deno Deploy operates 6 more months; JSR's infrastructure moves to Cloudflare.

Not established

  • What Cloudflare paid. Neither post gives terms or a price.
  • That agents drove it. Neither post names AI as a reason.
  • That Deno continues. Others may fork it; nobody has committed.
The five-minute readThe record, the timeline, the weight and 4 sources

The record

Two posts on October 9, 2026 carry this. Cloudflare published Deno is joining Cloudflare at 12:50 UTC, modified 20:39 UTC, written jointly by Kenton Varda and Ryan Dahl and tagged Acquisitions. Dahl: "The Deno team is joining Cloudflare, and we're merging workerd and celld!" Varda, quoted in the post: "We're joining Cloudflare to make the Workers programming model a mainstream way to build servers." Varda says Dahl and Bert Belder "will be leading a new effort to make workerd self-hosting a first-class supported way" to run Workers, with code and ideas from celld merged back into workerd. Varda names the gap that motivates it: workerd's Durable Objects support is limited to a single instance, which he calls a barrier to production readiness, and says he tried and failed to close it last spring. The post promises "more announcements about this work in the coming months" with no date, and gives no deal terms. Deno's own post, Deno is joining Cloudflare, by Ryan Dahl, carries the deadlines. "Today we're announcing that the entire Deno team is joining Cloudflare to take that work further." On the runtime: "We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates," and "After that year we will end our development of the Deno runtime." It adds that Deno "will remain open source, and we welcome others who want to continue its development." On the hosting business: "Deno Deploy will continue operating for six months before shutting down," with migration support to Cloudflare Workers for paying customers. On the registry: "JSR will continue operating, with its infrastructure moving to Cloudflare." Support for rusty_v8 continues, with work toward integrating it into workerd and no date given. Not addressed in either post: the price, whether any staff did not transfer, what happens to Fresh and deno.land, how many Deno Deploy customers are affected, who if anyone will maintain the Deno runtime after the year, and the status of Deno's litigation over the JavaScript trademark. The celld runtime the two teams are merging was released by Deno in August.

How it got here

  1. Aug

    The Deno team releases celld, a runtime for self-hosted serverless execution. Cloudflare's Kenton Varda later says the team was delighted by it, and that it closes a gap in workerd that he had tried and failed to close.

  2. Oct 2

    Supabase buys another database company because software agents, not people, now create most of its new databases. The first clear sign that agent volume, not human developers, was reshaping developer infrastructure. Edition 040.

  3. Oct 9

    Cloudflare publishes Deno is joining Cloudflare at 12:50 UTC. Deno publishes its own post the same day with the dates: 12 months of runtime fixes then an end to development, 6 months for Deno Deploy, JSR moving to Cloudflare.

  4. Oct 9

    Neither post discloses terms. Cloudflare tags the post Acquisitions; Deno's own post uses the word joining. Ryan Dahl and Bert Belder are named as co-leads of the self-hosting effort.

Who has to react

Every team running Deno Deploy, which has 6 months; maintainers of packages on JSR, whose registry now sits on a competitor's infrastructure; the Node.js project, which outlasted its challenger; Vercel, Fastly and Netlify, who sell the same edge execution; and the AI coding products whose generated code has to run in one of these two sandboxes.

What to watch

  • Would strengthen itCloudflare ships self-hosted workerd with multi-instance Durable Objects support, or publishes celld code merged into workerd, by June 30, 2027.
  • Would weaken itA funded organisation or foundation commits publicly to maintaining the Deno runtime past October 2027, with named maintainers, by October 9, 2027.
  • Would strengthen itAnother runtime or code-sandbox company is acquired by a cloud or AI provider, with agent code execution named as a reason, by December 31, 2027.

Why it weighs this much

Signal strength
CostHigh
CommitmentHigh
ReversibilityLow
PersistenceStructural

Cost is high even unpriced: acquiring an entire engineering team, taking on a year of support for a runtime you intend to end, and absorbing a registry's infrastructure are all costs paid before any benefit arrives. Commitment is high: two posts on the same day from both sides, named leads, and published deadlines that customers will plan against. Reversibility is low. A shutdown date announced to paying customers cannot be taken back without damage, and a dispersed team cannot be reassembled. Persistence is structural rather than dated, because the outcome is one fewer independent runtime, and runtime consolidation has historically not reversed.

The words

JavaScript runtime
The program that actually executes JavaScript outside a browser. Node, Deno and Cloudflare's workerd are runtimes, and whichever one wins decides how server code is written.
Self-hosting
Running the same software on your own machines instead of a vendor's cloud. For Workers it means a customer could leave Cloudflare and keep the programming model.
Durable Objects
Cloudflare's way of giving a piece of code its own persistent state and a single owner. Hard to run outside Cloudflare, which is the gap celld helps close.
JSR
A package registry Deno built for JavaScript and TypeScript. Registries are chokepoints: whoever hosts one sees and gates what everyone installs.

Sources

Your call

Which explanation do you believe?

A call is final. Other people's calls show after yours.

8 contributions. Thank you.

You have built
a record here.

Keep it: create an account to verify your contributions and put your name to the answers you choose. Your record stays yours.

Keep my record ↗
Optional: help show whose perspectives are missing
Kept with your answers under a random id, never with your name. Used for one thing: showing you, on your record, where you stand next to people like you, once at least 20 of them have answered.

Add your signature

Stand behind your judgment.

Create an account to attach your name to this answer. Your other answers show no name unless you sign them too.

Sign up to add your name ↗

Already have an account?