Sprites
Fly.io's persistent Firecracker microVMs for AI coding agents: 100 GB disk, one-second checkpoints, sleep when idle, pay only while awake
Overview
Sprites are persistent Linux computers from Fly.io, built for AI coding agents and other untrusted code. Each Sprite is a Firecracker microVM with a 100 GB persistent POSIX volume, its own HTTPS URL that wakes the machine on request, and a sleep mode that stops compute billing when nothing is running. The headline feature is checkpoints: copy-on-write snapshots of the whole filesystem in about a second without pausing the VM, taken automatically after sustained work, on idle and on shutdown. Restoring a checkpoint rewinds files but does not resume a paused process. Connectors let agents reach GitHub, OpenRouter or Slack without holding the credentials themselves, and an outbound DNS allow and deny policy limits where code can connect. At launch in January 2026, Sprites came with Claude Code, Codex CLI, Gemini CLI, Python 3.13 and Node preinstalled. You drive them with a CLI, a REST API, or SDKs for JavaScript, Go, Python and Elixir. Sprites are CPU-only; GPU work stays on Fly Machines. sprites.dev now redirects to fly.io/sprites, and the product shares billing and the $1 trial credit with the rest of Fly.io. Thoughtworks put Sprites in the "Assess" ring of its Technology Radar. For hosted serverless compute, also see Modal.
The Verdict
Who Should Use Sprites?
Best For
- Running Claude Code or Codex in a disposable, isolated machine
- Agent platforms that need per-user sandboxes with saved state
- Bursty workloads that sleep most of the time
Not Ideal For
- GPU workloads (CPU-only)
- Always-on heavy machines, which get expensive at hourly rates
What's Great
- Persistent state plus fast checkpoints and rollback
- Cheap for bursty agent use: pay only while awake
- Agent CLIs preinstalled; more polished than expected per HN users
Watch Out For
- CPU-only; no GPUs
- Round-the-clock 8 CPU / 8 GB use estimated at about $655/month
- Still early: Thoughtworks rates it "Assess"; some HN users cite Fly API complexity
Pricing
View all features & details
Key Features
- Firecracker microVM per Sprite
- 100 GB persistent POSIX volume, billed on use
- Checkpoints in about a second, copy-on-write
- Per-Sprite HTTPS URL that wakes on request
- Connectors for GitHub, OpenRouter and Slack
- Outbound DNS allow and deny policy
- CLI, REST API and SDKs for JS, Go, Python and Elixir
Use Cases
- Sandboxed coding-agent sessions (about $0.46 for a 4-hour session, per Fly)
- Per-user agent workspaces
- Low-traffic web apps (about $4/month, per Fly)
How It Compares
| Feature | Sprites | Modal |
|---|---|---|
| Model | Persistent VM that sleeps | Serverless functions |
| GPUs | No | Yes |
| Billing | Per CPU-hour and GB-hour while awake | Per second of use |
Sources: Fly.io Sprites (fetched Nov 2026) · Docs · Fly.io pricing · Simon Willison (Jan 2026) · DevClass (Jan 2026)
Is this your tool? Add a badge