Persistent Firecracker microVMs for coding agents with $0.0385/vCPU-hr active compute billing, 100 GB sparse NVMe disks, and true scale-to-zero auto-pause.

Visit Fly.io Sprites

At a glance

  • From $0.03
  • DR 64

Best unit economics for persistent, long-running coding agents that sit idle waiting on LLM calls.

Persistent Firecracker microVMs with $0.0385/active CPU-hr billing and auto-pause, cutting 85%-idle agent costs to ~$2.06 per 1,000 runs.

Pros

  • Lowest active-CPU rate ($0.0385/CPU-hr) with automatic scale-to-zero compute billing
  • Persistent 100 GB sparse NVMe filesystem survives pauses across multi-day coding tasks
  • Estimated $2.06 compute per 1,000 five-minute 85%-idle agent runs when auto-paused

Cons

  • Requires setting up and managing a Fly.io organization and billing account
  • 300ms-1s restore is slightly slower than sub-100ms ephemeral container pools
  • Not focused on massive multi-GPU RL rollout clusters like Modal

Pricing

From $0.03

Pay-as-you-go ($0.0385/active CPU-hr, $0.021875/GB-hr RAM, ~$0.02/GB-mo paused storage) or $20/mo Adventurer tier

Fly.io Sprites are persistent Linux Firecracker microVMs designed for long-running coding agents like Claude Code, Codex, and Gemini CLI, combining 100 GB sparse NVMe disks with true scale-to-zero active-CPU billing.

Why Sprites stand out on Idle Tax

Autonomous coding agents spend 70% to 90% of wall-clock time waiting on LLM token streams. Most dedicated sandbox clouds bill wall-clock compute until you manually call a pause endpoint. Fly.io Sprites auto-pause into a cold state and charge strictly for active compute:

  • Active CPU: $0.0385/vCPU-hr (the lowest verified active-CPU rate among major sandbox clouds).
  • Memory: $0.021875/GB-hr while active.
  • Storage: ~$0.50/GB-month hot storage, dropping to ~$0.02/GB-month when paused.
  • Idle-Tax math: Across 1,000 five-minute agent runs (85% LLM-wait idle, 2 vCPU / 4 GiB), auto-paused compute totals roughly $2.06 (or $8.25 if RAM stays warm continuously), versus $13.80 on unpaused wall-clock sandboxes.

Trade-offs

Sprites are built for persistent per-agent computers (300ms to 1s checkpoint/restore) rather than sub-100ms ephemeral one-shot script executions or massive GPU RL clusters, and require managing a Fly.io organization.

Verdict

The strongest unit-economics choice for long-running coding agents that pause and resume across multi-hour tasks without paying an idle tax.

Editorial Standards & Proof

Reviewed 2026-11-22
Ilias Ism
Reviewed byIlias IsmFounder & Lead Reviewer

Software engineer and founder (15+ years building web apps). Every listing is verified against live product checks, official pricing pages, and real usage limits before publication.

Product checks
Live domain, active software, and editorial review passed
Editorial independence
Zero paid verdicts; pros, cons, and limits are checked directly
Last updated

Share:

Similar to Fly.io Sprites