BuildIndependently confirmed2 publishers3 min readPublished
Cloudflare takes in the Deno team behind celld, the open-source implementation of Workers and Durable Objects
Deno's entire team is joining Cloudflare and taking celld, its open-source implementation of Workers and Durable Objects, along with it. For teams on Workers, the code they would use to leave now comes from the company they would be leaving.
The Engineer · Build desk

What happened
- Cloudflare says its open-source Workers runtime, workerd, runs Durable Objects only as a single instance, which is enough for local testing but cannot scale.
- Deno says celld builds on the Workers programming model and concentrates on Durable Objects, with scaling built into the model itself.
- Deno will ship monthly bug-fix and security releases of its runtime for one more year, then end development and leave the code open source for others.
- Deno Deploy, the company's hosting service, will keep running for six months and then shut down.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- exposure Teams on Workers now rely on one company for both the platform and the open-source code they would use to leave it. The exit stays open only while Cloudflare has a commercial reason to keep it open.
- capability The single-instance limit on Durable Objects is the main thing stopping a scaled Workers app from running elsewhere. A full team now works on it inside the company that owns the production routing code.
- decision Committing to Durable Objects now depends on large customers continuing to refuse closed runtimes. With Deno's independent sponsorship gone, that pressure is what keeps Cloudflare maintaining the exit.
Leaving a platform takes two things: a runtime that executes your code somewhere else, and replacements for the services the platform wired in. Workers has had the first for some time. Its runtime, workerd, is open source, and Cloudflare says it is the same code it runs in production [9]. "As a matter of fact, we have former customers that migrated away from us by using workerd," Cloudflare wrote in the joint post Kenton Varda co-authored with Deno [10][6].
Scaled Durable Objects were the missing piece. Cloudflare says it has wanted to fix workerd's single-instance limit since the original release, and the TODO comments in the code go back that far [12]. It names its production Durable Object routing as the obstacle [12]. The services around the runtime are thin as well. "Frankly, we haven't done a great job of building out the ecosystem of adjacent services and tooling to make it really work," the post says [13]. A few teams run workerd in production, "but so far, not that many," by Cloudflare's own account [14].
Deno released celld in August to close that gap [2][3]. At Cloudflare, the Deno team will combine that work with the Workers and Durable Objects teams [5]. It will also work toward integrating rusty_v8 into workerd [16]. "We want to make this programming model the default way to build servers, whether you run on Cloudflare's network or your own infrastructure," Deno wrote [4].
So the people who wrote the scaled exit now work for the platform it exits [1]. I think that matters less than it first appears, and Cloudflare's own post gives the reason. When Cloudflare pitched Workers for Platforms to customers including Shopify in 2022, those customers said they could not build on it unless the runtime was open source, so Cloudflare open-sourced it [15]. An exit that stays open because large buyers demand one lasts as long as they keep demanding it. I'd weight that requirement above the post's broader claim that Workers differs from other platforms because it is better [19].
Until now, celld's independent steward was Deno. Deno is ending separate work on its own runtime and hosting service [5]. Deploy shuts down six months before the runtime's support year runs out [21]. Paying Deploy customers get migration support to Cloudflare Workers, so anyone who picked Deploy as the non-Cloudflare option is being moved onto Cloudflare [20].
Deno's post does not say whether celld stays a separate project or folds into workerd, and it does not include a date for scaled Durable Objects outside Cloudflare. A Durable Objects app can only move if that code runs objects on more than one machine you control. The bindings Workers uses to reach external resources also have to point at services you can host [18]. Cloudflare's post says it released the runtime and hoped the community would adapt it to every environment, and that did not happen [17].
What to watch
- Whether celld continues as a standalone open-source repository under Cloudflare or is merged into workerd, and under what license.
- A dated release of Durable Objects that scale beyond a single instance on infrastructure outside Cloudflare's network.
- Whether any group takes over Deno runtime development when the one-year support window closes.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence55
- Adoption15
- Hype gap+30
- Incentives85
- Confidence60
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
The entire Deno team is joining Cloudflare.
- [2]
The Deno team released celld in August; Cloudflare describes it as an open-source implementation of Workers and Durable Objects.
- [3]
Deno says celld builds on the Cloudflare Workers programming model, focuses on Durable Objects, and builds scaling into the programming model.
- [4]
"We want to make this programming model the default way to build servers, whether you run on Cloudflare's network or your own infrastructure."
- [5]
At Cloudflare, Deno will combine its work with the Workers and Durable Objects teams and put future development into that shared platform instead of continuing a separate runtime and hosting service.
- [6]
The Cloudflare blog post on the move is a joint post by Kenton Varda and the author of Deno's announcement.
- [7]
Deno will support the Deno runtime for another year with monthly releases containing bug fixes and security updates, then end its development of the runtime; Deno will remain open source and others are welcome to continue its development.
- [8]
Deno Deploy will continue operating for six months before shutting down.
- [9]
Cloudflare's Workers Runtime, workerd, is open source, and Cloudflare says it is the same code it runs in production, not a parallel implementation.
- [10]
"As a matter of fact, we have former customers that migrated away from us by using workerd."
- [11]
"Workerd implements them, but only in a single-instance way, good enough for local testing, but unable to scale."
- [12]
Cloudflare says it has always wanted to fix workerd's single-instance Durable Objects, that TODO comments in the code go back to the original release, and that the problem is its production implementation of Durable Object routing.
- [13]
"Frankly, we haven't done a great job of building out the ecosystem of adjacent services and tooling to make it really work."
- [14]
Cloudflare says a few people have used workerd in production, 'but so far, not that many.'
- [15]
Cloudflare says that when it pitched Workers for Platforms to customers like Shopify in 2022, they said they could not build on it unless the Workers Runtime was open source, so Cloudflare open-sourced it.
- [16]
Deno will continue supporting rusty_v8 and work toward integrating it into workerd.
- [17]
Cloudflare says it released the runtime and hoped the community would adapt it to every possible environment, and that this has not happened.
- [18]
Cloudflare describes bindings as Workers' live environment design for configuring access to external resources.
- [19]
Cloudflare says the theory that Workers was designed for lock-in is wrong and that Workers is different because it is better.
- [20]
Deno will provide migration support for paying Deno Deploy customers moving to Cloudflare Workers.
- [21]
Deno Deploy shuts down about six months before the Deno runtime's one-year support period ends.
Sources
2 independent publishers whose own reporting we read for this story.
- blog.cloudflare.comDeno is joining Cloudflare
1 article · October 9, 2026
- Deno is joining Cloudflare
deno.com
1 article · October 9, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Product deprecationFollow
- JavaScript runtimesFollow
- Serverless and edge computingFollow
- Proprietary Tooling and Vendor Lock-InFollow
- Self-HostingFollow