Cloudflare Bought Deno. Ryan Dahl Says the Reason Is Agent Harnesses.
The entire Deno team is joining Cloudflare. That is the headline, and it topped Hacker News at 960 points with 503 comments, most of them about what happens to the runtime. The answers are concrete and not gentle. Deno the runtime gets twelve more months of monthly bugfix and security releases, then Deno Inc. stops developing it; it stays open source for anyone who wants to pick it up. Deno Deploy shuts down in six months with migration help for paying customers moving to Workers. JSR keeps running on Cloudflare infrastructure. rusty_v8 gets folded into workerd. Terms were not disclosed.
The part that belongs on this site is Dahl's explanation of why. The post traces a line from Deno to Deno Deploy to celld, the distributed-application layer Dahl built on the Workers programming model, and then says the quiet part out loud: "The need for better abstractions is especially acute with AI. Durable Objects bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface." The post ends with a recruiting line aimed at exactly one audience: "If you're building agents at scale and want to run them on your own infrastructure, please reach me now at [email protected]."
Read that as a product roadmap. A Durable Object is a single-threaded JavaScript actor with its own storage and its own address, which is a near-perfect description of one agent session: one loop, one memory, one inbox. Cloudflare has been pushing the Agents SDK onto exactly this primitive for a year, and Clef, its decision model, lives on the same platform. Buying the team that built the most serious alternative JavaScript runtime, and getting the author of Node in the deal, is a statement about where Cloudflare thinks the next billion processes will run. Not containers. Actors with state, billed by the millisecond, woken by a WebSocket.
The cost is real for the people who bet on Deno as an independent platform, and the HN thread is full of them. A runtime with a one-year clock is a runtime you migrate off. But the agent-infrastructure read is clear enough: the companies that own the substrate agents run on are consolidating, and the substrate they are consolidating toward is small, persistent, and serverless. That is a very different bet from the VM-per-agent approach that Maritime launched on YC the same day at a dollar an agent a month. Both can be right for different workloads. Only one of them just acquired a runtime team.
Deno post: https://deno.com/blog/cloudflare
Cloudflare post: https://blog.cloudflare.com/deno-joins-cloudflare
← Back to all articles
The part that belongs on this site is Dahl's explanation of why. The post traces a line from Deno to Deno Deploy to celld, the distributed-application layer Dahl built on the Workers programming model, and then says the quiet part out loud: "The need for better abstractions is especially acute with AI. Durable Objects bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface." The post ends with a recruiting line aimed at exactly one audience: "If you're building agents at scale and want to run them on your own infrastructure, please reach me now at [email protected]."
Read that as a product roadmap. A Durable Object is a single-threaded JavaScript actor with its own storage and its own address, which is a near-perfect description of one agent session: one loop, one memory, one inbox. Cloudflare has been pushing the Agents SDK onto exactly this primitive for a year, and Clef, its decision model, lives on the same platform. Buying the team that built the most serious alternative JavaScript runtime, and getting the author of Node in the deal, is a statement about where Cloudflare thinks the next billion processes will run. Not containers. Actors with state, billed by the millisecond, woken by a WebSocket.
The cost is real for the people who bet on Deno as an independent platform, and the HN thread is full of them. A runtime with a one-year clock is a runtime you migrate off. But the agent-infrastructure read is clear enough: the companies that own the substrate agents run on are consolidating, and the substrate they are consolidating toward is small, persistent, and serverless. That is a very different bet from the VM-per-agent approach that Maritime launched on YC the same day at a dollar an agent a month. Both can be right for different workloads. Only one of them just acquired a runtime team.
Deno post: https://deno.com/blog/cloudflare
Cloudflare post: https://blog.cloudflare.com/deno-joins-cloudflare
Comments