Why Wire Is Moving Off Cloudflare Durable Objects for Better AI Performance
Why we're moving off Cloudflare Durable Objects
We are rebuilding Wire's container runtime to solve four structural limits of Cloudflare Durable Objects, specifically around vector indexing, compute proximity, and self-hosting. By moving to our own infrastructure on Fly Machines with embedded SQLite, we achieve faster retrieval and true isolation. While we still rely on Cloudflare for our API and control plane, this shift allows us to offer dedicated capacity and better durability for regulated teams.
Durable Objects hand you durability and single-writer consistency for free, and leaving means buying them back.
- zuzululu
> What we built
> Each organization gets one host process (Bun) on Fly Machines for all its containers.
Well that is an instant nope from me. Fly.io's uptime/availability isn't something I trust and I am not alone. Part of what makes cloudflare durable objects great is the sheer availability and consistency at a true global scale
- stephantul
Why do all this work and then let an ai write the blog post.
- PUSH_AX
The thought of moving back to Fly after CF is completely absurd to me, each to their own. May your downtime be minimal...