Deno Team Joins Cloudflare, Deno Deploy to End Within Six Months
The entire Deno team is joining Cloudflare. The Deno runtime will receive a year of maintenance updates, while Deno Deploy will be discontinued and paying customers are expected to receive help migrating to Cloudflare Workers.
The Deno team is joining Cloudflare, as officially announced on October 9, 2026. The change also includes ending the managed Deno Deploy platform and limiting Deno runtime development to a one-year maintenance period.
Deno said it will release monthly runtime updates over the next 12 months. These are expected to include bug fixes and security fixes. After this period, in-house runtime development is expected to end, but the project is expected to remain open source.
The Deno Team, Cloudflare, and the End of the Deploy Platform
The most immediate change concerns Deno Deploy users. The service is expected to remain operational for another six months and then be shut down. Deno promises to help paying customers migrate to Cloudflare Workers.
The announcement does not yet provide a precise migration schedule, available tools, or technical conditions for moving applications. Teams running projects on Deno Deploy therefore remain advised to follow further migration guidance.
Deno also confirmed that JSR will continue. Its infrastructure is expected to move to Cloudflare.
The Deno Runtime Faces a Year of Maintenance
The Deno runtime will not be abandoned immediately. Monthly updates, including security fixes, are expected during the one-year maintenance period. Deno also said it will continue supporting the rusty_v8 project, which provides Rust bindings for the V8 JavaScript engine.
After the year ends, in-house development of the Deno runtime is expected to end. However, it has not been confirmed who might subsequently take over its long-term maintenance or further development. The announcements also do not specify whether an independent team or foundation will be created to oversee the project.
Cloudflare Wants to Connect celld and workerd
Cloudflare said it wants to merge work on the celld project with workerd. The goal is to make self-hosting Cloudflare Workers and Durable Objects a supported deployment option.
Durable Objects provide persistent state and, together with WebSockets, are described by Cloudflare and Deno as suitable building blocks for agent systems. Cloudflare therefore links the arrival of the Deno team to the development of technologies for running Workers outside its own managed edge platform as well.
The terms of the transaction were not disclosed. The announcements do not state the price, legal structure, or complete contractual details, so they cannot be used to infer how the Deno team is joining Cloudflare.
What to Watch Next
- migration tools, deadlines, and conditions for Deno Deploy customers,
- further information about the future of the open-source Deno runtime after the one-year maintenance period,
- Cloudflare’s technical plans for integrating celld into workerd and for self-hosted Durable Objects.
Sources
- Deno blog – Confirms that the entire Deno team is joining Cloudflare, one year of runtime maintenance, six months of Deno Deploy operation, migration for paying customers, the continuation of JSR, and support for rusty_v8.
- Cloudflare Blog – Confirms the Deno team’s arrival at Cloudflare and the intention to merge work on celld and workerd, with an emphasis on self-hosting Workers and Durable Objects.
Verified and updated: 10/10/2026 15:23
