Deno Joins Cloudflare: What Happens to the Runtime, Deno Deploy and JSR

The entire Deno team is joining Cloudflare. The Deno runtime gets one more year of monthly fixes before development ends, Deno Deploy shuts down in six months, and the JSR registry keeps running on Cloudflare infrastructure.

Deno Joins Cloudflare: What Happens to the Runtime, Deno Deploy and JSR

Deno announced on October 9 that its entire team is joining Cloudflare, per Deno. Financial terms were not disclosed. Deno is the JavaScript and TypeScript runtime co-founded by Ryan Dahl, who also created Node.js.

The runtime gets 12 more months of monthly bug-fix and security releases, and then development by the team ends. The code stays open source, and Deno says it welcomes others who want to continue it. Deno Deploy, the hosting service, keeps operating for six months and then shuts down. Paying customers get migration support to Cloudflare Workers. That puts the shutdown around April 2027.

Two pieces continue. JSR, the package registry, keeps operating and its infrastructure moves to Cloudflare. The team will keep supporting rusty_v8, the Rust bindings for the V8 engine, with the aim of folding it into workerd, Cloudflare's open source Workers runtime. The post makes no commitment about Fresh, Deno's web framework.

The team's new work is celld, a way to run Workers-style code on your own servers. Dahl wrote that "we want to make this programming model the default way to build servers." For Cloudflare, that answers the standing objection to Workers: code written for it runs in one company's cloud. For Deno users, the practical fact is a clock. A runtime with a published end date is a migration project, however good the code is.

Deno Deploy has about six months and the runtime has about a year of fixes. If you run production workloads on Deploy, start the move to Workers or to Node now, while migration support exists. If you only publish packages to JSR, nothing changes for you yet.