Deno joins Cloudflare: Deno Deploy closes in six months, and celld is merging into workerd
The whole Deno team joined Cloudflare on October 9: Deno Deploy shuts down after six months with migration support to Workers, the Deno runtime gets one year of fixes, and celld merges into workerd so self-hosting Workers becomes a supported path.
Decision: On October 9, 2026, the entire Deno team joined Cloudflare, and Cloudflare said it will merge celld back into workerd so the same Workers code can run on machines you own. 1
Two clocks came with that announcement, and they decide who has work to do. Deno Deploy keeps running for six months before it shuts down, with migration support for paying customers moving to Cloudflare Workers. 2
The Deno runtime gets one more year of monthly bug and security releases, after which Cloudflare ends its development. The code stays open source, and the team invites others to carry it on. 2
If you run Workers or Durable Objects on Cloudflare's network, this announcement asks nothing of you this week. The self-hosting path behind it exists as an open-source daemon you can pilot today, and the merged version has no release date. 13
The quick read
| Aspect | Before October 9, 2026 | Now | Action, and when |
|---|---|---|---|
| Deno Deploy (Deno's managed application host) | Running Deno apps for paying and free accounts | Operates six more months, then shuts down; migration support for paying customers | List every service you host there this week, because the window closes around April 2027 2 |
| Deno runtime | Actively developed by Deno Land | Monthly bug and security releases for one year, then development ends; stays open source | Pin the version you build against now; nothing to move this quarter 2 |
| JSR (Deno's package registry) | Run by Deno Land | Keeps operating, with its infrastructure moving to Cloudflare | Nothing 2 |
| celld (open-source Workers runtime for your own machines) | A separate Deno Land project, released in August | Its code and ideas merge into workerd | Pilot it on one app if lock-in was your blocker 1 |
| workerd (Cloudflare's open-source runtime) | Self-hostable, with Durable Objects limited to one instance | Ryan Dahl and Bert Belder lead the merger into it, and first-class self-hosting is promised | Wait for the merged release; today it suits local testing 14 |
| Workers and Durable Objects on Cloudflare | Runtime, limits, and prices as published | Unchanged | Nothing this week 1 |
What was announced
Both posts went up on October 9. Ryan Dahl, who created Deno and co-created Node.js, and Kenton Varda, who designed Durable Objects, wrote the Cloudflare post together. 1 Ryan Dahl's post on the Deno blog carries the dated terms, because the shutdowns are Deno's to announce. 2
- The Deno runtime receives monthly bug and security releases for another year, and Cloudflare ends its development after that. The code stays open source, and others are welcome to continue it. 2
- Deno Deploy runs for six more months and then shuts down. Cloudflare provides migration support for paying customers moving to Workers. 2
- JSR, Deno's registry for JavaScript and TypeScript packages, keeps operating, with its infrastructure moving to Cloudflare. 2
- rusty_v8, the Deno team's V8 bindings for Rust, stays supported and is headed into workerd. 2
Dahl's post states the wider goal: Workers should become the default way to build servers, on Cloudflare's network or your own infrastructure. 2 Varda describes celld as an implementation of Workers and Durable Objects built to be compatible with Cloudflare's and aimed at self-hosting. 1
The concrete plan is narrower than the goal. Dahl and Bert Belder will lead an effort to make self-hosting workerd a supported way to build and run Workers applications. 1 Cloudflare promises more announcements in the coming months, and points at celld and workerd as things you can start self-hosting today. 1
The clock, if you run on Deno Deploy
Deno Deploy is Deno's managed application-hosting service, built so that running an app takes as little setup as possible. 25 It has six months left, and the announcement states no date beyond that window. 2
Six months from October 9 lands around April 2027. Migration support is promised to paying customers, so billing status is the first thing to check on each project you host there. 2
The work that falls to you is an inventory: every service running on Deploy, what it stores, and which of them move to Workers. 2 Cloudflare's support covers moves to Workers; a move to another host is yours to plan.
What it changes for a team on Workers
The runtime you deploy to today does not change. What changes is the answer to a question teams weigh before betting on Workers: whether this code can run somewhere else. 1
workerd is the JavaScript and WebAssembly runtime Cloudflare runs in production, published under Apache 2.0 and installable through npm as
npx workerd. 4 Its README describes it as the same code that powers Workers, usable as an application server for self-hosted Workers applications. 4One gap kept it out of production for self-hosters. Durable Objects in workerd run as a single instance, which Cloudflare calls good enough for local testing and unable to scale. 1 Cloudflare's own Durable Objects routing depends on services it operates, and Varda writes that the company never built the self-hosted version. 1
celld is the piece that closes that gap, which is why Cloudflare is merging it in rather than writing its own. 1
What self-hosting looks like today
celld is an open-source daemon that runs a Workers application on machines you own. It covers Workers handlers, Durable Objects, KV, Queues, D1, R2, Workflows, Cron Triggers, static assets, and Dynamic Workers. 36
You run a 58 MB static executable or a container image, and you need one S3-compatible bucket. 3 The bucket holds cell state and ownership: a conditional write assigns each cell to a node, and the fleet runs without a membership protocol, failure detector, or consensus service. 3
| Service | What it is | celld status |
|---|---|---|
| Workers | Stateless request handlers | Supported 6 |
| Durable Objects (cells) | Single-threaded actors with durable storage | Supported 6 |
| Durable Object facets | Child objects inside a Durable Object | Supported 6 |
| KV | Key-value store | Supported 6 |
| Queues | Message queue | Supported 6 |
| D1 | SQL database | Supported 6 |
| R2 | S3-style object storage | Supported 6 |
| Workflows | Durable multi-step execution | Supported 6 |
| Cron Triggers | Scheduled handlers | Supported 6 |
| Static assets | Files served from a directory | Supported 6 |
| Dynamic Workers | Workers loaded at runtime | Supported 6 |
| Containers | A container supervised by a Durable Object | Experimental 6 |
Anything that needs Cloudflare's network, its GPUs, or browser automation falls outside what celld runs, and its compatibility page lists the remaining differences. 6
celld also publishes its own cost comparison. Cloudflare Durable Objects cost Workers Paid plus $4.15 per resident cell-month; celld costs roughly $0.02 per resident cell-month on $48 nodes with 8 GB of RAM, capped at 2,500 cells each. 3 Those base figures leave out the compute and bucket traffic your application generates, and node prices of your own change the second number. 3
Where the self-hosting story stops
- The merged runtime does not exist yet. celld belongs to Deno Land today, Cloudflare's commitment is to merge its code and ideas into workerd, and the announcement gives no date. 13
- Scaled Durable Objects are the work still to be done. workerd's support for them stays single-instance until the merge lands, which is why celld is being folded in at all. 14
- workerd is not a hardened sandbox. Its README tells you to run possibly-malicious code inside a virtual machine, because workerd alone lacks defences against implementation bugs. 4
- Coverage has edges. Containers are experimental in celld, and per-application compatibility needs testing rather than assuming. 6
- You become the operator. celld's page puts nodes, bucket provider, and operations in your hands, and offers no reliability guarantee of its own. 3
What to do this week
- On Deno Deploy: list your services and each one's billing status. Paying customers get migration support to Workers, and the six-month window closes around April 2027. 2
- On the Deno runtime: pin the version you build against. Monthly fixes continue for a year, and the code stays open source after that. 2
- On Workers: change nothing in production. If vendor lock-in was what stalled the decision, pilot celld on one non-critical Worker, since the merge is what turns that pilot into a supported path. 13
- Choosing a host now: a project started on Deno Deploy starts on a service with six months left. 2
Verdict: one deadline, one pilot, one watch item
Treat this as work if you run on Deno Deploy. Six months is the shortest window in the announcement, it covers a service that stops existing, and paying customers can get help moving to Workers. 2
Treat it as a pilot if lock-in to Workers was the blocker. celld runs Workers code against the
wrangler.json you already have, on nodes you control with one bucket, and the merged workerd is the version Cloudflare will support. 13Treat it as a watch item if you deploy to Cloudflare today. Runtime, limits, and prices for Workers and Durable Objects hold where they were, and the self-hosting work carries no date to plan against. 1
References
- 1Deno is joining Cloudflare
blog.cloudflare.com
- 2Deno is joining Cloudflare
deno.com
- 3
- 4cloudflare/workerd
github.com
- 5Deno Deploy
deno.com
- 6celld: Cloudflare compatibility
celld.dev
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.