Two Clocks Started On 9 October
Cloudflare's deal for the whole Deno team, announced on 9 October, starts two migration clocks for anyone who runs software on Deno.
| Item | What was announced | Date it implies |
|---|---|---|
| Deno Deploy | Keeps operating for six months, then shuts down; paying customers get migration support to Cloudflare Workers | About April 2027 |
| Deno runtime | Monthly bug-fix and security releases for one more year, then Deno ends its own development | About October 2027 |
| JSR registry | Keeps operating, with its infrastructure moving to Cloudflare | No end date given |
| rusty_v8 | Support continues, with work toward integrating it into workerd | No end date given |
The right-hand column is our arithmetic from the announcement date, not a date either company published. Neither blog post states a price, and The New Stack reports that the terms were not disclosed. It adds that Deno had raised around 26 million US dollars across two rounds.
The Gap Cloudflare Bought Its Way Across
Cloudflare says the missing piece was self-hosting. Its open-source Workers runtime, workerd, supports Durable Objects only as a single instance, good enough for local testing but unable to scale, and Kenton Varda wrote that to-do comments about it date back to the original release.
Deno's answer was celld, released in August: a single Rust binary that needs only an object-storage bucket as an external service. Ryan Dahl and Bert Belder will now lead an effort to make workerd self-hosting a first-class supported way to run the Workers model, merging code and ideas from celld back into workerd.
The commercial logic is stated plainly. Varda told The New Stack that if the Workers model is exclusive to Cloudflare it narrows the company's addressable market, so making it work on every provider benefits Cloudflare. Dahl said the combined project is expected to remain open source, likely under the Apache 2.0 licence that celld already uses.
Promised Is Not Shipped
Self-hosting at scale is a promise for the coming months, not a product today. Cloudflare's post says you can self-host celld or workerd now, but workerd alone still cannot spread Durable Objects across machines.
For European buyers weighing sovereignty the prospect is real. A supported runtime with the same API as Cloudflare's own platform, run on your own servers, would be an exit route from Cloudflare's network, and Varda argues that open source and an escape hatch are good business. That route does not exist in supported form yet, so judge it on features shipped, not on blog posts.
What To Do This Quarter
List every project running on Deno Deploy, with its owner and traffic, and choose its destination before the end of March 2027. Cloudflare Workers is the path with migration support for paying customers, but any host that runs standard JavaScript is an option.
If you run the Deno runtime on your own servers, you have a year of monthly security updates. Pin the version and decide between a move to Node.js and a community fork. Dahl says Deno's growing Node.js compatibility had left it maintaining another implementation of the same technology, and that anyone is welcome to carry the runtime forward.
If you publish packages on JSR, nothing changes today. Keep publishing, and note that the registry's infrastructure is moving to Cloudflare.
Read next: Cloudflare Now Writes Your AI Training Rules for You | IMF Finds $1.4tn of Revenue Commitments in 14 AI Deals
