BusinessMarkets, money & strategy
Cloudflare acquires Deno, will close Deno Deploy in six months and end official Deno runtime development after a year
Cloudflare is buying Deno and will fold celld, Deno's Rust daemon for self-hosting Workers and Durable Objects, into its open-source workerd runtime. Deno Deploy shuts down in six months. The Deno runtime will get a final year of maintenance releases.
QuietHow it’s measured
Hacker News · 3 likes
Reach blends public engagement (views, likes, comments, shares, stars) from the platforms where the story or its original source lives: YouTube, Hacker News, GitHub, Substack and similar. A video and the article written from its transcript share one score, taken from the video. Platforms with no data are left out rather than counted as zero, and the age of a story never lowers its score.
AT Pulse research deskPublished · 5 min read · AI-assisted analysisThe deal winds down Deno's own products. Deno Deploy closes in about six months. The Deno runtime will get only bug-fix and security releases for one year, then official development stops, though the code stays open source and community maintainers are welcome. Financial terms were not disclosed. Ryan Dahl said the decision was made jointly and that Deno had been pulled into matching Node's behavior instead of solving bigger problems. [2] [8] [3] [1]
The main asset is celld. It is an alpha, Apache-2.0 daemon that runs Workers and Durable Objects on servers the user controls. Each object gets its own SQLite database, replicated to an object-storage bucket. Nodes coordinate only through conditional writes to that bucket, with no control plane. Merging celld into workerd would add distributed, sharded Durable Objects, where workerd currently supports only single-instance objects. [6] [8] [7]
The performance and cost figures are not settled. The project's own measurements put writes to region-local storage at about 90 ms and reads of active objects at about 1 ms median. Claims of large savings rest on density figures that contradict each other and were measured only on Apple M-series hardware. The cheaper option also flips depending on how often objects are active. No third-party benchmarks were found. [6] [10] [4]
Deno Deploy users need a migration plan. Deno.serve() maps to a Worker fetch handler, Deno.cron() to a scheduled handler, and KV atomics to Durable Objects, and KV data should be exported early. Teams on the Deno runtime have about 12 months to move to Node or rely on a community fork, and no fork exists yet. [9] [2] [4]
Deploy customers have about six months to migrate, and Deno runtime users have about a year. If self-hosted celld matures inside workerd, teams could run the Workers programming model off Cloudflare, which would weaken platform lock-in concerns.
Sources gathered and cross-checked; writing the dossier now.
Executive brief
Cloudflare is acquiring Deno, and the Deno runtime itself is being wound down. The runtime will get bug-fix and security releases for one year, then official development stops. Deno Deploy, the hosted service, closes in six months (Deno blog). What Cloudflare wants is celld, Deno's Rust daemon that runs Workers and Durable Objects on your own servers. Ryan Dahl and Bert Belder will merge it into workerd, Cloudflare's open-source runtime (The New Stack). Bun went to Anthropic in December 2025. After this deal, Node.js is the only mainstream JavaScript runtime with independent governance (byteiota).
What changed and event timeline
Workerd open-sourced
Cloudflare released workerd, the runtime code behind Workers, and described it as usable for self-hosting, local testing or as a programmable proxy ().
Celld announced
Deno released celld, an Apache-2.0 daemon that runs Workers and Durable Objects on your own machines. Each object gets its own SQLite database, replicated to an object-storage bucket the user controls (;).
Acquisition announced
Dahl and Kenton Varda of Cloudflare co-wrote the announcement. Financial terms were not disclosed. Deno had raised $26M in total, including a $21M Series A led by Sequoia (;).
Dahl explains
On Hacker News, Dahl said the decision was made jointly and that he agrees with it. In his view Deno got pulled into matching Node's behavior exactly and was not solving big problems ().
Official runtime development ends
Deno stays open source, and the team welcomes community maintainers ().
Capabilities and access
- celld v0.1.0 (alpha, Apache-2.0) is a single Rust binary. Its only external dependency is object storage (Cloudflare blog; GitHub).
- Cloudflare says users can self-host celld or workerd today. Merged features are expected "in the coming months" (Cloudflare blog).
- JSR, Deno's package registry, keeps running on infrastructure that moves to Cloudflare (Deno blog).
Read the full section
- celld v0.1.0 (alpha, Apache-2.0) is a single Rust binary. Its only external dependency is object storage (Cloudflare blog; GitHub).
- Cloudflare says users can self-host celld or workerd today. Merged features are expected "in the coming months" (Cloudflare blog).
- JSR, Deno's package registry, keeps running on infrastructure that moves to Cloudflare (Deno blog).
- The reviewed sources say nothing about Fresh, Deno's web framework.
Technical analysis for researchers and developers
- Coordination: nodes coordinate only through the storage bucket, with no control plane and no consensus service.
- Durability: a single node confirms a write by uploading it to the bucket.
- What workerd gains: today workerd supports only single-instance Durable Objects. celld adds distributed, sharded objects (Cloudflare blog).
Read the full section
- Coordination: nodes coordinate only through the storage bucket, with no control plane and no consensus service. Conditional writes to the bucket ensure exactly one node owns each cell at a time. SQLite changes are captured in LTX format, and a new owner recovers the previous owner's log before taking over (GitHub).
- Durability: a single node confirms a write by uploading it to the bucket. In a fleet, a write counts as durable once a peer node has it on disk, and the upload happens afterward (GitHub).
- What workerd gains: today workerd supports only single-instance Durable Objects. celld adds distributed, sharded objects (Cloudflare blog).
- Scope: anything that needs Cloudflare's network, GPUs or a browser farm is out of scope (GitHub).
Claims and evidence
- Latency (README, project-measured): about 90 ms per write to region-local storage.
- Reads: about 1.1 ms median and 7 ms at p99 for active cells (Xenospectrum).
- Cost: byteiota reports "roughly 88% lower cost" (byteiota).
Read the full section
- Latency (README, project-measured): about 90 ms per write to region-local storage. One lab fleet measured about 600 ms against non-local storage and about 25 ms once a second node held the write (GitHub).
- Reads: about 1.1 ms median and 7 ms at p99 for active cells (Xenospectrum).
- Cost: byteiota reports "roughly 88% lower cost" (byteiota). Xenospectrum points out that the density figures behind such comparisons contradict each other (2,500 vs 1,000 cells per $48 node), were measured only on Apple M-series hardware, and that the cheaper option flips depending on how much of the time objects are active (Xenospectrum).
- No third-party benchmarks were found.
Context and prior work
- celld copies the Durable Objects model, which is why The New Stack calls Deno the startup that "copied" Cloudflare's playbook (The New Stack).
- Deno's best-known feature is its permissions system, which can allow-list specific files and network hosts.
- Both companies frame stateful Durable Objects as a good fit for AI agents that need persistent memory (Deno blog; byteiota).
Read the full section
- celld copies the Durable Objects model, which is why The New Stack calls Deno the startup that "copied" Cloudflare's playbook (The New Stack).
- Deno's best-known feature is its permissions system, which can allow-list specific files and network hosts. Node added a permissions model in v20.0.0 (April 2023) and marked it stable in v22.13.0 (January 2025), but Node's network permission is still all-or-nothing (Simon Willison).
- Both companies frame stateful Durable Objects as a good fit for AI agents that need persistent memory (Deno blog; byteiota).
Limitations, safety and contested findings
- Disputed feature coverage: the README lists KV, Queues, D1, R2 and Workflows as supported (GitHub).
- Security: the project says celld is not safe for multi-tenant use with adversarial code.
- Operations: there is no automatic rebalancing, and each cluster serves only one application.
Read the full section
- Disputed feature coverage: the README lists KV, Queues, D1, R2 and Workflows as supported (GitHub). Xenospectrum reports that D1, Workflows, Queues, KV and R2 are unimplemented (Xenospectrum). Check the current docs before relying on any of them.
- Security: the project says celld is not safe for multi-tenant use with adversarial code.
- Operations: there is no automatic rebalancing, and each cluster serves only one application. Several S3-compatible stores are incompatible, including MinIO Community, Backblaze B2, Hetzner and DigitalOcean Spaces (Xenospectrum).
- No community fork of the Deno runtime exists yet (byteiota).
Business and practitioner implications
- Deno Deploy users: migrate before about April 2027 and export Deno KV data early.
- Teams using the Deno runtime: budget for a move to Node, or bet on a community fork, within 12 months.
- Platform buyers: if self-hosting becomes a supported option, the Workers programming model gets an exit path off Cloudflare, which weakens lock-in concerns.
Read the full section
- Deno Deploy users: migrate before about April 2027 and export Deno KV data early. Map
Deno.serve()to a Workerfetchhandler,Deno.cron()to ascheduledhandler, and KV atomics to Durable Objects (DEV Community). - Teams using the Deno runtime: budget for a move to Node, or bet on a community fork, within 12 months.
- Platform buyers: if self-hosting becomes a supported option, the Workers programming model gets an exit path off Cloudflare, which weakens lock-in concerns. Cost advantages depend on workload.