The Deno team is joining Cloudflare, and Deno Deploy will shut down
The team behind the Deno runtime is joining Cloudflare. Deno Deploy closes in six months, and the standalone runtime gets one more year of security releases.
The team behind Deno, the JavaScript and TypeScript runtime, is joining Cloudflare, and Deno is winding down its hosted service. Ryan Dahl, who created Deno and Node.js, announced the move in a Deno post dated Oct. 9, 2026, and Cloudflare published its own post the same day. The sources reviewed do not give financial terms.
Deno Deploy will run for six months before it shuts down, with migration support for paying customers moving to Cloudflare Workers. The standalone Deno runtime gets one more year of monthly bug-fix and security releases, after which its development ends. The JSR package registry keeps operating, with its infrastructure moving to Cloudflare.
What changes first for Deno Deploy customers
If the six months run from the Oct. 9, 2026 announcement, they end on April 9, 2027. The sources reviewed do not give an end date. Deno's post describes migration support for paying customers, but the sources reviewed do not say what that support includes.
The New Stack's headline described Deno as a startup that copied Cloudflare's serverless playbook. Deno's post says the team will put its future development work into a shared platform, rather than a separate runtime and hosting service. RuntimeWire describes that platform as built around celld and workerd.
The three products change on different schedules, so the dates that apply depend on which of them a project uses.
Runtime and registry timelines
The Deno runtime has a longer clock. Deno's post says it will receive monthly bug-fix and security releases for one year, after which runtime development ends. If counted from Oct. 9, 2026, that window closes in October 2027.
The code stays open source, and Deno's post invites others to continue the project. Ecosistema Startup reports that the project is open to outside maintainers. The sources reviewed do not name any outside group taking that work on.
JSR keeps running, with its infrastructure moving to Cloudflare. Deno's post says rusty_v8 support continues, with the work aimed at integrating it into workerd, Cloudflare's Workers engine.
The sources do not conflict on these dates. Cloudflare's post covers the team move and the self-hosting plan but does not state the Deno Deploy or runtime dates. Those dates appear in Deno's post, in The New Stack, in RuntimeWire and in Ecosistema Startup.
Cloudflare's self-hosting plan
Cloudflare's post says the team will merge celld into workerd, Cloudflare's open-source Workers runtime. RuntimeWire describes celld as Deno's system for self-hosting distributed applications. Ryan Dahl and Bert Belder will lead an effort to make self-hosting workerd a first-class way to build and run Workers-style apps.
Ryan Dahl wrote in the joint post that workerd's Durable Objects support is limited to a single instance. The post frames the joint work as a way to make distributed applications radically easy to build and operate on your own infrastructure.
Cloudflare says more announcements will follow in the coming months. The post also says celld and workerd can be self-hosted now.
“For a team on Deno Deploy, the hosted clock is shorter than the runtime clock.”
Platform-risk lessons from a wound-down host
For a team on Deno Deploy, the hosted clock is shorter than the runtime clock. The hosted service ends after six months, while the runtime receives a year of security work. A team's exposure depends on which of those it relies on.
The migration target named in the sources is Cloudflare Workers. The self-hosting path runs through workerd, which the post says is the same code Cloudflare runs in production.
Ecosistema Startup reports that Cloudflare announced its purchase of VoidZero on June 4, 2026.
As of Oct. 11, 2026, the sources reviewed do not state a deal value. They also contained no update to the dates in Deno's post.
