Why we're moving off Cloudflare Durable Objects
usewire.io
July 9, 2026
4 min read
🔥🔥🔥🔥🔥
44/100
Summary
Wire is transitioning from Cloudflare Durable Objects to a newly rebuilt container runtime for its context containers used by AI agents. The new data plane has been benchmarked against the previous system using identical data and queries.
Key Takeaways
- Wire has transitioned from using Cloudflare Durable Objects to a self-built container runtime to address structural limitations in data retrieval and processing.
- The new architecture allows for in-process candidate retrieval, reducing latency from 3.7 seconds to 1.4 seconds for idle containers.
- Each organization now has a dedicated host process on Fly Machines, enabling better data placement and isolation for containers.
- The new system implements continuous Write-Ahead Logging (WAL) to ensure durability and consistency of data writes.
Community Sentiment
Positives
- Cloudflare Durable Objects are praised for their unmatched availability and consistency on a global scale, making them the gold standard for reliability.
- The new infrastructure offers more control, which could lead to better performance in the long run if durability is achieved.
Concerns
- Fly.io's uptime and availability are seen as unreliable, raising serious doubts about moving away from Cloudflare's robust offerings.
- The comment about AI writing the blog post suggests a lack of authenticity and concern over the quality of communication from the team.
