Cloudflare Couldn't Self-Host Its Own Best Abstraction, So It Bought the People Who Did

Cloudflare announced on October 9 that the entire Deno team is joining the company. The acquisition headline is Ryan Dahl, the creator of Node.js, landing at a cloud vendor. The part worth reading closely is Kenton Varda's confession buried mid-post: workerd, the open-source Cloudflare Workers runtime, has never had production-grade Durable Objects. Its implementation is single-instance only, "good enough for local testing, but unable to scale," with TODO comments in the code going back to the original release. Varda admits he tried to fix it himself last spring and, in his words, "embarrassingly, it didn't work." So when Dahl's team released celld in August — an open-source implementation of Workers and Durable Objects built for self-hosting, one Rust binary whose only external dependency is an object storage bucket — Cloudflare's honest reaction was delight, followed by hiring the whole crew.

The plan is to merge celld's ideas and code back into workerd, with Dahl and co-founder Bert Belder leading a first-class self-hosting effort. The costs, meanwhile, land on Deno's own users. The Deno runtime gets monthly bug-fix and security releases for one more year, after which official development ends — it stays open source, and Cloudflare says it welcomes others to continue it. Deno Deploy shuts down after six months, with migration support for paying customers moving to Cloudflare Workers. JSR survives with its infrastructure moving to Cloudflare, and rusty_v8 gets folded into workerd. Financial terms weren't disclosed; Deno had raised $26 million, including a Sequoia-led Series A. Varda frames the whole thing against the perennial "Workers is lock-in" criticism: Shopify only signed on after the runtime went open source, some customers have already left using workerd, and in his telling an escape hatch is simply good business. Dahl's stated ambition is to make the Workers programming model — distributed singletons, each with its own SQLite database and single-threaded JavaScript — the default way to build servers on Cloudflare's network or your own infrastructure, and he explicitly names agent harnesses as the target workload.

Source article image
Source image 1

For anyone who runs their own boxes, this is the most interesting platform story of the week. The actor model — one addressable object, one database, no shared-state headaches — is a sane foundation for real-time apps and agent systems, and "one binary plus an S3 bucket" is a far more believable operational story than the tangle of public clouds and databases Dahl himself described building under Deno Deploy. The tension is in the ownership: the escape hatch from Cloudflare lock-in is now maintained by Cloudflare. The production-grade self-hosted implementation of the exit door will be built, prioritized, and roadmapped by the very vendor you bought the door to avoid. Dahl's contact address in his own announcement is, tellingly, ry@cloudflare.com. If you're designing agent infrastructure today, do you adopt the Workers model because the primitives are genuinely good and trust the vendor to keep the self-hosted version honest — or do you wait for a neutral implementation? What's your actual trust model for an escape hatch owned by the company you're hedging against?

Source article image
Source image 2

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

Enterprise AI Is Quietly Becoming a Systems Integration Problem

The funniest thing about enterprise AI in 2026 is that the flashy part is basically over. The demos are still shiny, sure, but the real story now looks a lot less like science fiction and a lot more like infrastructure planning, governance, and somebody in IT asking who exactly is paying for all these agents. Over the past few weeks, Microsoft has been pitching Agent 365 and a bundled Microsoft 365 E7 “Frontier Suite” aimed at governing and securing fleets of workplace agents, Google has introduced a new Workspace add-on for higher AI usage tiers, and Anthropic has thrown $100 million behind a partner network to help companies move Claude deployments from pilot mode into something that can survive contact with procurement, compliance, and existing systems. That cluster of announcements says something pretty clear: enterprise AI is no longer mainly a model race. It is becoming a packaging, controls, and implementation race. The clever model still matters, obviously, but once every vendo...
Read more