Cloudflare Will End Deno Runtime Development After One Year, and Deno Deploy Closes in Six Months

Cloudflare will stop developing the Deno JavaScript runtime one year after the October 9 announcement that the Deno team is joining the company, and Deno Deploy, the hosting service, closes after six months.

Ryan Dahl, Deno's founder, wrote the announcement on Deno's blog. The post says the whole Deno team is joining Cloudflare and that the runtime gets monthly releases with bug fixes and security updates for the year. Developer Simon Willison, quoting the announcement on his blog, reports the line on what follows: "After that year we will end our development of the Deno runtime."

Both posts frame the news as a team joining a company. The runtime's end of life is a line inside that story.

What ends, and when

Deno stays open source under the MIT licence, and the announcement says others are welcome to continue its development. The repository has 108,700 stars and 1,300 open issues. Neither post names a successor maintainer or a fork.

Piece	What the Deno post says	Timing
Deno runtime	Monthly bug and security releases, then development ends	One year
Deno Deploy	Shuts down; paying customers get migration help to Cloudflare Workers	Six months
JSR	Keeps operating, infrastructure moves to Cloudflare	No end date
rusty_v8	Support continues, with work toward integrating it into workerd	No end date

Neither post gives a price or any deal terms. Cloudflare's own post is tagged "Acquisitions" but describes the move as the team joining.

What Cloudflare is building instead

Cloudflare is merging its open-source Workers runtime, workerd, with celld, a project the Deno team released in August. Kenton Varda wrote the Cloudflare side of the post and says workerd is "the same code we run in production." Dahl and Bert Belder will lead an effort to make self-hosting workerd a supported way to run Workers-model applications.

The celld repository is licensed Apache-2.0 and has 5,300 stars. Its README describes "self-hosted, distributed Durable Objects": each object becomes a named server with its own SQLite database, and long-term state sits in an S3-compatible, Google Cloud Storage or Azure Blob Storage bucket of your own. Cloudflare's post says it is a single Rust binary whose only external dependency is object storage.

The README is blunt about limits. A product that "needs the Cloudflare network, a GPU, or a browser farm is out of scope." One node waits for a bucket round trip on every write, so a single-node setup writes much more slowly than a fleet of two or more. The default V8 heap limit is 128 MB per isolate, and the Containers feature is marked experimental. Pull requests are disabled; contributors email a git format-patch file.

Who has to move

For a team running Deno in production, the six-month Deploy clock is the one that bites first. Paying Deploy customers get migration support to Workers, which means rewriting a deployment target, not only a config file.

Deno's own APIs raise the cost of leaving. In the Hacker News thread, which passed 1,300 points, user cscheid wrote that a team using Deno since 2022 found it "turned out unfortunately to be a miss." Other commenters argued that moving is manageable because Deno added npm compatibility, while Deno-specific APIs such as Deno.serve and KV create real lock-in.

User tech234a wrote that yt-dlp uses Deno as its default JavaScript runtime. A commenter who said they work at Netlify wrote that Netlify still runs the Deno runtime but no longer uses its managed infrastructure. Neither claim was confirmed by the projects named.

Simon Willison, who writes about developer tools, called the one-year end date "the bad news" and named Deno's permissions system as his favourite feature. Node.js added a permissions model in v20.0.0 and has called it stable since v22.13.0, he wrote, but it cannot allow-list specific network hosts. Networking is on or off.

Willison also quoted Dahl's Hacker News comment that Deno "has been sucked into the gravity well of node compatibility."

What is still missing

The posts do not say what happens to Fresh, the web framework, or to Deno's own tooling after the runtime ends. They give no date for celld and workerd merging, and Cloudflare's post promises more announcements without naming a month. Self-hosting is also a live question elsewhere on the site's beat: Unison Cloud went MIT with a local-run guide that still pulls from a private repository, and Supabase bought Turso alongside a $150 million raise. The next checkpoint here is Deno Deploy's shutdown, six months after October 9.