Fly.io replaces Sprites' homemade filesystem after checkpoint failures

Founder Kurt Mackey built the earlier storage stack; Fly.io says a 5,000-cycle test exposed failures the new block device is designed to avoid.

By · Published

Primary source: Fly.io

Why it matters

Sprites sell persistence and rollback as core features for agent workloads. Fly.io's storage rewrite addresses a failure mode in the system beneath both, while its migration guide says customers must initiate upgrades for older environments.

Fly.io replaces Sprites' homemade filesystem after checkpoint failures — Founder Kurt Mackey built the earlier storage stack; Fly.io says a 5,000-cycle test exposed failures the new block device is designed to avoid.

Fly.io is replacing the storage system beneath Sprites after a stress test left some environments unable to create checkpoints, exposing a failure in one of the product's core promises: a persistent Linux computer that can sleep, move between servers and keep its files. In a post published October 22nd, Fly.io described the replacement, the Sprites Block Device (SBD), as the standard filesystem for the service going forward.…

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

Reader comments

Conversation for this story loads after sign-in.