GoKawiilFly.io replaces custom JuiceFS setup with new Sprites Block Device filesystem
Fly.io has introduced the Sprites Block Device (SBD), a new filesystem replacing the modified JuiceFS system it built at launch for its Sprites product. The original setup used a rewritten SQLite metadata backend kept durable with Litestream, storing a single 100GB disk image mounted as a loop device backed by object storage. SBD keeps the same core design—object storage as the root of a Sprite's disk so it can sleep and wake across servers—but replaces the custom tooling with a simpler, more reliable implementation.
GoKawiil's interpretation of the reporting above, not reported fact.
The move suggests Fly.io concluded that its original bespoke filesystem, while clever, introduced complexity and reliability risks that a more standard approach could avoid—echoing the post's framing of infrastructure design as favoring simplicity over cleverness. For users, the company indicates the practical effect should mainly be improved reliability rather than a change in how Sprites behave.
- Fly.io is replacing its custom JuiceFS-based filesystem with a new system called SBD.
- The design still relies on object storage as the durable root of a Sprite's disk, unchanged from the original architecture.
- The company frames the change as trading cleverness for reliability and simplicity.
Source: fly.io, 2026-10-22
Published there as: “SBD: We Have a Filesystem at Home”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.