Deno joins Cloudflare; Deno Deploy shuts in six months

The entire Deno team is joining Cloudflare, Deno announced on October 9, 2026. Deno Deploy, the company's hosting service, will keep running for six months and then shut down. The Deno runtime, a JavaScript and TypeScript runtime, gets one more year of monthly bug-fix and security releases before official development ends. For every team that runs code on Deno Deploy, the migration clock has started.

"Today we're announcing that the entire Deno team is joining Cloudflare to take that work further," Deno creator Ryan Dahl wrote on Deno's blog. Neither company disclosed a price or how the deal is structured. Cloudflare files its post on the move under acquisitions.

What happens to each Deno product

The two announcements and the coverage agree on the timelines:

Product	What happens
Deno runtime	Monthly bug-fix and security releases for one more year, then official development ends. It stays open source, and others may carry it on
Deno Deploy	Keeps running for six months, then shuts down. Paying customers get help moving to Cloudflare Workers
JSR	The JavaScript package registry keeps running, and its infrastructure moves to Cloudflare
rusty_v8	Deno keeps supporting it and will work on bringing it into workerd

Neither post says what happens to Deno KV, the company's database service, or to the Fresh web framework. Deno's post lists Fresh among its open-source projects, but gives no plan for it.

Deno raised a $21 million Series A led by Sequoia Capital in June 2022, RuntimeWire notes.

The plan: Workers you can run yourself

The joined team will work on running Cloudflare's model outside Cloudflare's own network. Workers is Cloudflare's platform for running code across its network. Durable Objects is its building block for apps that need to keep state.

Two pieces of software are being merged, the Cloudflare blog explains:

• workerd is Cloudflare's open-source Workers runtime. Today its Durable Objects run as a single instance, which works for local testing but cannot scale.
• celld is Deno's system for self-hosting distributed apps. It is one Rust binary whose only outside dependency is object storage. To scale, you run several celld instances against one storage bucket.

Code and ideas from celld will move into workerd. Dahl, now a senior principal engineer at Cloudflare, will lead the effort with Bert Belder. The goal is to make self-hosted workerd a fully supported way to run apps built on the Workers model.

"We're joining Cloudflare to make the Workers programming model a mainstream way to build servers," Dahl wrote. Cloudflare distinguished engineer Kenton Varda added: "We released workerd genuinely intending for people to use it in production." Self-hosters will run "the same code we run in production," not a separate copy, he wrote. Cloudflare promises more details "in the coming months."

What this means for developers

• Deno Deploy users: start planning now. Six months is short for a production move. List every project, domain, cron job and environment variable on Deploy this week.
• Paying customers: ask for migration help early. Cloudflare is offering support for moves to Workers. Get on that list before the deadline crowd does.
• Check your Deno KV data. The announcements do not say what happens to Deno KV. Ask Deno directly before you plan, and keep an export ready.
• Runtime users: you have a year of security fixes. Deno stays open source, but official development ends after that. Decide whether to stay, move to Node.js or another runtime, or wait to see if a community fork forms. Deno says Node.js compatibility was an important part of its work, which may make a move to Node easier.
• JSR publishers: no action needed yet. The registry keeps running on Cloudflare infrastructure.
• Self-hosters: watch workerd. If the celld merge lands, you could run the Workers model on your own servers instead of only on Cloudflare.

The first deadline that matters is Deno Deploy's shutdown, six months from October 9.