# Quivvo vs Fly Sprites

Quivvo and Fly Sprites are both Linux computers for AI agents, and they bill differently. Sprites charge for the CPU and memory you actually use ($0.0385 per CPU-hour and $0.021875 per GB-hour of use), so a mostly idle machine can cost very little. Quivvo charges for what a machine is allocated while it runs: $0.054 an hour for 2 vCPUs and 4 GiB. Quivvo itself runs on Fly.io's infrastructure, on Fly Machines.

## How do they compare?

| | Quivvo | Fly Sprites |
| --- | --- | --- |
| Billing | Allocated CPU and memory, per second while running | Actual CPU and memory use |
| 2 vCPU + 4 GiB, busy for a full hour | $0.054 | Up to about $0.165 |
| While suspended or asleep | Disk only | Storage only |
| Disk | $0.20 per GiB-month | About $0.50 per GB-month awake, $0.02 asleep |
| Saving state | Snapshots and forks of the disk; suspend keeps memory when it can | Whole-disk checkpoints |
| Public URLs | Publish a port on the machine's URL | One HTTPS URL per Sprite, routed to port 8080 |
| Hosted MCP server | Yes | Yes, a [remote MCP server](https://docs.fly.io/sprites/integrations/remote-mcp) |

Sprites' figures come from [its site](https://fly.io/sprites) and [docs](https://docs.fly.io/sprites), read on 30 October 2026.

## When should I choose Fly Sprites?

Choose Sprites if your agents sit idle most of the time and you want to pay only for actual use, or if whole-disk checkpoints are central to how you work. It also has the backing of Fly.io directly, where Quivvo is a layer on top of it.

## When should I choose Quivvo?

Choose Quivvo if your machines are busy while they run, because a flat allocated rate then costs less: a machine busy for the full hour costs about a third as much. An agent with no browser can also sign itself up for you to approve.

See the [full pricing comparison](https://tryquivvo.com/compare/sandbox-pricing).