The Deno team joins Cloudflare; Deno Deploy shuts down in six months and runtime development ends in a year
Ryan Dahl's company is folding its Workers implementation, celld, into Cloudflare's open-source workerd to make self-hosting Workers and Durable Objects a supported path -- with agent harnesses named as a target use case.
Deno founder Ryan Dahl announced on October 9 that the entire Deno team is joining Cloudflare; neither company disclosed deal terms. The move comes with fixed end dates for Deno's own products. Deno Deploy keeps running for six months and then shuts down, with migration support for paying customers moving to Cloudflare Workers. The Deno runtime gets one more year of monthly bug-fix and security releases, after which Deno will end its development of it, though the code stays open source. The JSR package registry keeps operating, with its infrastructure moving to Cloudflare.
What Cloudflare gets
The joint Cloudflare post, written by Dahl and Cloudflare's Kenton Varda, says the aim is to "radically simplify self-hosting Workers and Durable Objects," by merging Cloudflare's open-source workerd runtime with celld, Deno's own implementation of those primitives. On the Deno blog, Dahl ties the decision partly to AI -- "The need for better abstractions is especially acute with AI" -- and singles out Durable Objects as a fit for agent harnesses, since they combine cheap serverless execution, persistent state, WebSockets and a high-level JavaScript interface.
Why it matters
For teams that built on Deno Deploy, this is a dated migration project, not a headline: six months to move production workloads, and a one-year runway before the runtime stops getting upstream fixes. More broadly, it's another case of a platform underneath AI workloads changing hands with a fixed sunset attached. When you count what an agent stack really costs, include the re-platforming work a vendor's exit can force on you, alongside per-token and per-seat spend.