July 9, 2026
Durable Objects? Durable drama
Why we're moving off Cloudflare Durable Objects
Wire ditched part of Cloudflare, and the comments instantly turned into a trust fight
TLDR: Wire rebuilt part of its system off Cloudflare to make it faster, more flexible, and easier to run in different places. Commenters were far less impressed by the speed claims than by the move to Fly.io, with trust, uptime fears, and blog-post roast jokes stealing the spotlight.
Wire says it is not breaking up with Cloudflare entirely, but the internet heard, “We’re moving out,” and the replies got spicy fast. The company builds little private knowledge spaces for artificial intelligence helpers, and it says Cloudflare’s system was easy to build on but hit four big limits: slower lookups, too many handoffs, fixed location, and no way for customers to run it themselves. So Wire rebuilt the guts of the system on its own setup, claiming faster response times and better search results while keeping the same public-facing tools.
But in the court of public opinion, the benchmark was only half the story. The real drama? They moved part of the stack to Fly.io, and several commenters reacted like someone had traded a luxury jet for a folding scooter. One person flatly called it an “instant nope,” saying Cloudflare’s global reliability is the whole appeal. Another basically offered thoughts and prayers: “May your downtime be minimal…” Ouch.
Not everyone was throwing tomatoes. One commenter said they had to read twice before the product finally “clicked,” and could see the idea getting more useful as documents get messier and bigger. Still, the biggest laugh came from the drive-by roast: “Why do all this work and then let an AI write the blog post.” And the award for dad-joke brutality goes to: “The objects are durable, but not endurable.” Community verdict: the engineering may be serious, but the comment section came for blood, memes, and uptime jokes.
Key Points
- •Wire rebuilt its AI container runtime and moved the first workspaces from Cloudflare Durable Objects to a self-built data plane while keeping other services on Cloudflare Workers.
- •The company cites four main limits with Durable Objects for this workload: external vector indexing, inability to run enough compute next to data, fixed-at-creation placement with shared compute, and lack of self-hosting.
- •In the new architecture, each organization runs one Bun host process on Fly Machines, and each container is a SQLite file with an embedded vector index using sqlite-vec.
- •Wire says warm tool calls improved to about 0.3 seconds from about 0.4 seconds with previous latency spikes above 2 seconds, and idle wake time improved to 1.4 seconds from 3.7 seconds.
- •To restore durability guarantees after leaving Durable Objects, Wire implemented continuous WAL shipping to object storage and says writes are acknowledged only after WAL frames are stored, with group commit adding about 100 ms.