Rapid News Brief — Deno announced on Oct. 9, 2026, that its entire team is joining Cloudflare, with a transition plan that gives customers different timelines for its runtime and hosting service. Organizations using Deno Deploy will need to plan for a shutdown, while users of the open-source runtime face an end to the team’s continued development.
Two products, two transition windows
In a public announcement, Deno creator Ryan Dahl said the runtime would receive monthly bug fixes and security updates for another year. After that period, the team will stop developing it. The code will remain open source, and Dahl invited others to continue its development.
Deno Deploy will operate for six more months before shutting down. The company says paying customers moving to Cloudflare Workers will receive migration support. Its announcement also says JSR will remain operational as its infrastructure moves to Cloudflare.
The engineering direction shifts
Cloudflare’s joint announcement by Dahl and Kenton Varda describes a planned effort to improve self-hosting for the Workers programming model. That work will bring code and ideas from Deno’s celld project into workerd, Cloudflare’s runtime.
The companies frame this as a way to use similar application-building primitives on Cloudflare’s network and on independently operated infrastructure. Cloudflare says further announcements will follow in the coming months. That is a development direction, not evidence that every existing Deno application can move without changes.
What customers should separate
The operational implication is to inventory runtime dependencies separately from hosted services. Continued access to open-source code does not, by itself, extend a managed hosting service’s operating period or establish a replacement maintenance commitment.
Teams evaluating a move should confirm their support eligibility, application compatibility and testing requirements with the provider. These are planning considerations, not claims about the ease or cost of migration. The announcements provide transition windows; they do not demonstrate a completed customer migration or guarantee identical behavior across environments.