When does Deno Deploy shut down?

Deno Deploy keeps operating for six months after the October 9, 2026 announcement that the Deno team is joining Cloudflare, and then it shuts down. Deno says it will give migration support to paying customers who move to Cloudflare Workers. Free users get the same six-month window but no promised migration help, so they should plan a move early.

Can I keep using the Deno runtime after the Cloudflare deal?

The Deno runtime stays open source, and the Deno team will ship monthly releases with bug fixes and security updates for one more year. After that year, Deno says it will end its own development of the runtime, though it welcomes others who want to continue the project. Existing Deno apps keep working, but long-term maintenance becomes a community question.

What happens to JSR and rusty_v8 after Deno joins Cloudflare?

JSR, the JavaScript package registry built by the Deno team, will keep operating, with its infrastructure moving to Cloudflare. The rusty_v8 project, which binds Google's V8 engine to Rust, will keep being supported, and the team will work toward integrating it into workerd, the open-source runtime behind Cloudflare Workers.

What is celld and how does it relate to workerd?

celld is Ryan Dahl's open-source implementation of Cloudflare Workers and Durable Objects, built for self-hosting and scaling. Dahl describes it as one Rust binary with object storage as its only external dependency; it was released in August 2026. Cloudflare says celld is being merged into workerd, with Dahl and Bert Belder leading work to make self-hosted workerd a first-class option.

Why does the Deno acquisition matter for AI agents?

Ryan Dahl writes that the need for better abstractions is especially acute with AI, and that Durable Objects bring together features that suit agent harnesses, such as cheap serverless execution, persistent state and WebSockets. He invites teams building agents at scale on their own infrastructure to get in touch, which places the Deno team's next work on self-hostable agent infrastructure.

Cloudflare · 2026-10-09 · major

Deno joins Cloudflare — Deno Deploy shuts down in six months

The whole Deno team is joining Cloudflare. Deno Deploy shuts down in six months, and the Deno runtime gets one more year of bug-fix and security releases before Deno's own development ends. Ryan Dahl says agents drove the move.

Deno and Cloudflare logos side by side for the 'Deno is joining Cloudflare' announcement

Cloudflare takes in the Deno team, and Deno Deploy users have six months to move.

Quick facts

Deal	Entire Deno team joins Cloudflare
Deno Deploy	Runs 6 more months, then shuts down
Deno runtime	1 year of monthly fix releases, then development ends
License	Deno stays open source
JSR	Keeps running, moves to Cloudflare infrastructure
Migration help	For paying Deno Deploy customers, to Workers
Announced	October 9, 2026

What is it?

Deno, the JavaScript and TypeScript runtime created by Node.js author Ryan Dahl, is joining Cloudflare with its entire team. Deno Deploy, the company's hosting service, will run for six more months and then shut down. The Deno runtime gets monthly bug-fix and security releases for one year, after which the Deno team ends its development; the code stays open source for anyone who wants to continue it.

How does it work?

Instead of a separate runtime and hosting service, the team will build into one shared platform with Cloudflare's Workers and Durable Objects groups. Dahl's celld, a single Rust binary that self-hosts Workers-style apps with object storage as its only dependency, is being merged into Cloudflare's open-source workerd runtime. Dahl and Bert Belder will lead work to make self-hosted workerd a first-class way to run these apps, and rusty_v8 will be integrated into workerd. JSR, the JavaScript package registry, keeps running on Cloudflare infrastructure.

Why does it matter?

Teams that host on Deno Deploy now have a hard deadline, with migration support to Cloudflare Workers offered only to paying customers. Dahl writes that "the need for better abstractions is especially acute with AI" and says Durable Objects suit agent harnesses, so the deal points a known runtime team at self-hostable infrastructure for running agents. Projects built on the Deno runtime should plan for its end of development in about a year.

Who is it for?

Deno and Deno Deploy users, JavaScript backend teams, people running agents on Workers

Frequently asked questions

When does Deno Deploy shut down?: Deno Deploy keeps operating for six months after the October 9, 2026 announcement that the Deno team is joining Cloudflare, and then it shuts down. Deno says it will give migration support to paying customers who move to Cloudflare Workers. Free users get the same six-month window but no promised migration help, so they should plan a move early.
Can I keep using the Deno runtime after the Cloudflare deal?: The Deno runtime stays open source, and the Deno team will ship monthly releases with bug fixes and security updates for one more year. After that year, Deno says it will end its own development of the runtime, though it welcomes others who want to continue the project. Existing Deno apps keep working, but long-term maintenance becomes a community question.
What happens to JSR and rusty_v8 after Deno joins Cloudflare?: JSR, the JavaScript package registry built by the Deno team, will keep operating, with its infrastructure moving to Cloudflare. The rusty_v8 project, which binds Google's V8 engine to Rust, will keep being supported, and the team will work toward integrating it into workerd, the open-source runtime behind Cloudflare Workers.
What is celld and how does it relate to workerd?: celld is Ryan Dahl's open-source implementation of Cloudflare Workers and Durable Objects, built for self-hosting and scaling. Dahl describes it as one Rust binary with object storage as its only external dependency; it was released in August 2026. Cloudflare says celld is being merged into workerd, with Dahl and Bert Belder leading work to make self-hosted workerd a first-class option.
Why does the Deno acquisition matter for AI agents?: Ryan Dahl writes that the need for better abstractions is especially acute with AI, and that Durable Objects bring together features that suit agent harnesses, such as cheap serverless execution, persistent state and WebSockets. He invites teams building agents at scale on their own infrastructure to get in touch, which places the Deno team's next work on self-hostable agent infrastructure.

Try it

https://deno.com/blog/cloudflare