AI Potluck
Infrastructure / Deployment

Fly Sprites

Fly.io

Gives an AI agent its own persistent Linux computer rather than an ephemeral sandbox. Each Sprite is a Firecracker microVM with its own kernel and a 100 GB POSIX volume that survives sleep and moves between host machines, plus live copy-on-write checkpoints an agent can roll back to. Fly.io operates it as a managed service with CLI, REST and language SDK clients and an outbound API gateway.

The product page moved from sprites.dev to fly.io/sprites during 2026 and was rewritten around persistence; the isolation mechanism now appears on the Sprites overview rather than the product page. Verified 2026-08-13 via fly.io/sprites and the Fly.io Sprites overview.

Openness

1 high confidence
1.0
license
Proprietary
service
proprietary(Fly.io managed)
source
closed
clients
CLI/REST/JS/Go SDKs (client libs only, no open runtime)
isolation
Firecracker(Firecracker itself is OSS/AWS, but the Sprites product/orchestration is proprietary)

Proprietary managed sandbox SaaS; no open source runtime published (only client SDKs). Underlying Firecracker is OSS but the product is not. The product page (now fly.io/sprites) ships only client surfaces - a CLI installer, a REST API, and JavaScript, Go, Elixir and Python SDKs - against a hosted Fly.io control plane, with metered CPU, memory and storage pricing and no self-hostable runtime or source release.

  • https://sprites.dev/ recorded 2026-08-13

    Sprites = hardware-isolated Firecracker execution env for arbitrary code; managed service, CLI/REST/JS/Go clients; no self-hostable open runtime

Adoption

1 low confidence
1.0

Launched in January 2026 as Fly.io’s answer to E2B, and still early. No user, customer or usage counts are disclosed on the product page or in launch coverage; the product is positioned for AI coding-agent sessions (Claude Code, Codex). Placed at 1 on reported traction, with low confidence pending real numbers. The product page (now fly.io/sprites) publishes no user, customer, session or sprite count of any kind; the only numbers on it are the per-CPU-hour, per-GB-hour and per-GB-hour-storage prices, $0.07 per CPU-hour among them. Because there is no count to band on, no reach figure is recorded.

Capability

4 medium confidence
4.0

Top-tier microVM isolation plus persistent stateful sandboxes (explicitly anti-ephemeral) is a strong, differentiated feature set. It is not a 5 only because the product is brand-new with unproven scale against the incumbents; isolation and persistence are best-in-class. The product page is now written around persistence and checkpointing - tiered storage backed by object storage, a 100 GB POSIX volume, live copy-on-write checkpoints taken automatically on idle and shutdown, per-sprite URLs and an outbound API gateway - and it no longer states the isolation mechanism or the 1-12s cold and sub-1s restore latencies. Those rest instead on the vendor Sprites overview, which states that each Sprite is a Firecracker microVM with its own kernel and filesystem, isolated in hardware from every other Sprite, and that it spins up in seconds. No bounded cold-start figure is published anywhere in the vendor prose.

  • https://sprites.dev/ recorded 2026-08-13

    persistent 100 GB ext4/POSIX volume surviving sleep and machine moves, live copy-on-write checkpoint and restore, arbitrary Linux code, usage-metered pricing; no isolation mechanism or latency figure stated

  • https://fly.io/agents-need-a-computer/ recorded 2026-08-13

    each Sprite is a Firecracker microVM with its own kernel and durable Linux filesystem, isolated in hardware from every other Sprite, spinning up in seconds and sleeping when idle

Verified 2026-08-13