Deno Deploy to shut in six months as Deno team joins Cloudflare

Deno Deploy to shut in six months as Deno team joins Cloudflare

9 October 2026: The whole Deno team is joining Cloudflare, and the company is winding down its own products to do it. Deno Deploy, its serverless hosting service, will keep running for six months and then shut down, and the Deno runtime itself will get one more year of monthly releases with bug fixes and security updates before Deno ends its development. Ryan Dahl, who created both Node.js and Deno, announced the move on Deno's blog.

What happens to each product

Dahl's post sets out the plan product by product:

• Deno runtime: supported for another year with monthly releases containing bug fixes and security updates, after which Deno ends its development. The runtime stays open source, and Dahl says others are welcome to continue it.
• Deno Deploy: operates for six more months, then shuts down. Paying customers will get migration support for a move to Cloudflare Workers.
• JSR, the TypeScript-first package registry: continues operating, with its infrastructure moving to Cloudflare.
• rusty_v8, the Rust bindings to the V8 engine that many projects use: still supported, with work towards integrating it into workerd, the runtime behind Workers.

"We know this is a consequential change for people who have built on Deno," Dahl wrote.

Why the team is moving

Dahl ties the decision to celld, a system Deno built on the Cloudflare Workers programming model to make distributed applications simpler to build and operate. At Cloudflare the team will combine that work with the Workers and Durable Objects teams, aiming to make the model "the default way to build servers", on Cloudflare's network or on a customer's own infrastructure. He singles out AI agents as the main use, because Durable Objects combine cheap serverless execution with persistent state and WebSockets. Cloudflare's own post, written jointly by Dahl and Cloudflare's Kenton Varda, says more announcements about running the platform on one's own infrastructure will follow in the coming months.

What Deno users should plan for

Neither post gives calendar dates, only the periods. Counting from the announcement on 9 October, Deno Deploy would close around April 2027 and runtime support would end around October 2027, but customers should confirm the exact dates with Deno. Teams hosting on Deno Deploy have the shorter deadline and should start testing their applications on Workers or another host now. Teams running the Deno runtime themselves have a year, after which they depend on whoever takes over the open-source project, or they move to Node.js or Bun. Anything that pulls packages from JSR is unaffected for now.

Cloudflare and Deno in our catalogue

We list Deno and Cloudflare as companies.

Related on TrustList:

• Deno joins Cloudflare: Deno Deploy shuts down in six months
• Next.js flaw in next/og ImageResponse allows remote code execution: upgrade to 16.3.6
• Next.js 16.4.1 fixes two critical flaws that need no login to exploit

Sources

• Deno: Deno is joining Cloudflare (Ryan Dahl), 9 October 2026
• Cloudflare: Deno joins Cloudflare (Kenton Varda and Ryan Dahl), 9 October 2026
• heise online: Cloudflare stoppt Deno-Runtime, 14 October 2026