The Pulse
Cloudflare Brings Deno’s Team Aboard; Runtime Gets One More Year of Updates
Deno says its runtime will receive monthly bug-fix and security releases for another year before the company ends its development. Deno Deploy will close after six months, while JSR will continue operating.
AI.info Team · Written with AI ·
“We’ve decided to put our future development work into this shared platform rather than continuing to develop a separate runtime and hosting service.”
Ryan Dahl, author of Deno’s announcement
Deno announced on October 9 that its entire team is joining Cloudflare, with a major consequence for developers who use its JavaScript and TypeScript runtime: Deno will stop developing that runtime after a year of monthly bug-fix and security releases. The software will remain open source, and Deno says it welcomes others who want to continue its development.
Deno’s runtime gets one more year of updates
The announcement sets out separate timelines for Deno’s products. The Deno runtime will receive monthly releases containing bug fixes and security updates for another year; after that, Deno says it will end its development of the runtime. The company does not say the project will be deleted or made proprietary: it says the runtime will remain open source.
Deno Deploy, its hosting service, has a shorter runway. It will continue operating for six months before shutting down, and Deno says it will help paying customers migrate to Cloudflare Workers. The announcement does not give a specific shutdown date for either product beyond those timelines.
Other parts of Deno’s work have a different path. JSR, the TypeScript-focused package registry, will continue operating, with its infrastructure moving to Cloudflare. Deno also says it will continue supporting rusty_v8 and work toward integrating it into workerd, Cloudflare’s open-source runtime for Workers.
Cloudflare wants self-hosted Workers and Durable Objects
The companies frame the move around making Cloudflare’s Workers programming model easier to run outside Cloudflare’s network. In a joint post, Ryan Dahl and Cloudflare’s Kenton Varda say the teams will combine work on workerd and celld, a project for running distributed applications built around Workers and Durable Objects.
Cloudflare says workerd is the same runtime code it uses in production, but its existing Durable Objects support outside Cloudflare is limited to a single instance. Dahl’s celld project aims to support distributed instances, with the platform managing placement, routing and durable storage. The joint post says Ryan and Bert will lead work to make self-hosting workerd a first-class option, bringing code and ideas from celld into it.
The shift is from a standalone runtime to Cloudflare’s stack
The deal changes Deno’s stated development focus from maintaining its own runtime and hosting service to building around Cloudflare’s Workers model. That leaves the runtime open for community development, but the announcement offers no commitment from an outside group to take over its releases. Users who depend on Deno’s own supported updates will need to weigh that one-year support period against the prospect of moving to another runtime or maintaining a fork.
For Deploy customers, the immediate decision is more specific: Deno says it will provide migration support to Workers before Deploy closes in six months. JSR, meanwhile, remains in service under the new arrangement. The companies’ stated engineering plan is to combine celld and workerd; Deno’s own runtime will receive monthly fixes for a year, then its official development will end.