Deno team joins Cloudflare; runtime gets one year, Deploy shuts down in six months

Deno is moving to Cloudflare

Deno has announced that its entire team is joining Cloudflare, ending the company's run as an independent JavaScript runtime and hosting provider. According to the announcement on Deno's blog, which surfaced on the front page of Hacker News, future development effort will be directed into a shared platform built with Cloudflare's Workers and Durable Objects teams, rather than into a separate runtime and hosting service.

The post frames the move as the continuation of Deno's trajectory. The runtime questioned how modules are distributed, what security guarantees a JavaScript runtime can provide, and how easily an application can ship as a standalone executable, while also adding compatibility with Node.js so users could keep using the existing JS ecosystem. Deno Deploy pushed further toward making deployment simple, and the team's newest project, celld, builds directly on the Cloudflare Workers programming model, letting developers build distributed applications with scaling built into the programming model rather than assembled per application.

What happens to Deno's products

The announcement sets concrete timelines:

• The Deno runtime will be supported for another year, with monthly releases containing bug fixes and security updates. After that year, Deno will end its development of the runtime. The project remains open source, and the team welcomes others who want to continue its development.
• Deno Deploy will continue operating for six months before shutting down. Paying customers will receive migration support to move to Cloudflare Workers.
• JSR, Deno's package registry, will continue operating, with its infrastructure moving to Cloudflare.
• Work on rusty_v8, Deno's Rust bindings for the V8 engine, will continue, with a goal of integrating it into workerd, the runtime that powers Cloudflare Workers.

The post acknowledges that this is a consequential change for people who have built on Deno, and thanks contributors, businesses and users who trusted the project's direction.

An AI-driven motivation

A significant part of the rationale is AI workloads. According to the announcement, Durable Objects combine capabilities that are particularly useful for agent harnesses: inexpensive serverless execution, persistent state, WebSockets, and a high-level JavaScript interface. That is why celld focuses on Durable Objects, and why the team's stated ambition at Cloudflare is to make this programming model the default way to build servers, whether running on Cloudflare's network or on a developer's own infrastructure. A joint post with Kenton Varda on the Cloudflare blog covers the technical details, and the post's author invites teams building agents at scale who want to run on their own infrastructure to reach out.

Why it matters

This consolidates two of the most prominent serverless JavaScript runtimes under one roof. Deno was one of the most serious attempts to rethink server-side JavaScript, from its permission model and integrated toolchain to its later Node.js compatibility work, and its exit as an independent platform narrows the field of options for developers choosing where to run JS at the edge. Cloudflare Workers now stands to absorb both Deno Deploy's customers and, potentially, some of its underlying technology: folding rusty_v8 into workerd could carry Deno's engine-level work into Cloudflare's platform, while JSR continuing under Cloudflare infrastructure keeps a notable npm alternative alive. For existing users, the deadlines are short — six months for Deploy, one year of runtime maintenance — so migration planning starts now. The silver lining is that Deno stays open source, leaving the door open for the community to fork or carry the runtime forward independently.