Cua Fleets vs Fly.io Sprites

Cua Fleets costs $0.044625 per vCPU-hour and Fly.io Sprites costs $0.0385 per vCPU-hour. Cua Fleets runs gVisor. Fly.io Sprites runs microVMs.

Updated Oct 14, 2026

Cua Fleets

Hosted Linux and Windows sandboxes for computer-use agents.

Isolation: gVisor
Free tier: Not listed
Max session: Not listed

Visit site Cua Fleets profile

Fly.io Sprites

Persistent Linux computers that sleep when idle.

Isolation: MicroVM
Free tier: $30 trial credit
Max session: Not listed

Visit site Fly.io Sprites profile

What is different

8 fields differ. The rest are the same or not listed.

Field

Cua Fleets

Fly.io Sprites

vCPU, per hour: Cua Fleets: $0.044625; Fly.io Sprites: $0.0385
RAM, per GiB-hour: Cua Fleets: $0.0223125; Fly.io Sprites: $0.021875
Storage: Cua Fleets: Free; Fly.io Sprites: $0.000683 per GiB-hour
Billing: Cua Fleets: Per second; Fly.io Sprites: Active CPU time only
Isolation: Cua Fleets: gVisor; Fly.io Sprites: MicroVM
Pause and resume: Cua Fleets: No; Fly.io Sprites:
SDKs: Cua Fleets: Python, TypeScript, Rust; Fly.io Sprites: Python, JavaScript / TypeScript, Go
Integrations: Cua Fleets: OpenAI Agents SDK, MCP; Fly.io Sprites: MCP, OpenAI Agents SDK

Full comparison

18 fields, at each provider's list price

Cua Fleetscua.ai/#pricing

Fly.io Spritesfly.io/pricing

Pricing

vCPU, per hour: Cua Fleets: $0.044625; Fly.io Sprites: $0.0385
RAM, per GiB-hour: Cua Fleets: $0.0223125; Fly.io Sprites: $0.021875
Storage: Cua Fleets: Free; Fly.io Sprites: $0.000683 per GiB-hour
Free tier: Cua Fleets: Not listed; Fly.io Sprites: $30 trial credit
Paid plan from: Cua Fleets: Not listed; Fly.io Sprites: Pay as you go
Billing: Cua Fleets: Per second; Fly.io Sprites: Active CPU time only

Limits

Max session: Cua Fleets: Not listed; Fly.io Sprites: Not listed
Idle stop: Cua Fleets: Not listed; Fly.io Sprites: Not listed
Largest sandbox: Cua Fleets: 8 vCPU · 32 GiB; Fly.io Sprites: Not listed
Concurrent sandboxes: Cua Fleets: Not listed; Fly.io Sprites: Not listed

Platform

Isolation: Cua Fleets: gVisor; Fly.io Sprites: MicroVM
GPU: Cua Fleets: Not listed; Fly.io Sprites: Not listed
Snapshots: Cua Fleets: Not listed; Fly.io Sprites:
Pause and resume: Cua Fleets: No; Fly.io Sprites:

Developer

SDKs: Cua Fleets: Python, TypeScript, Rust; Fly.io Sprites: Python, JavaScript / TypeScript, Go
Integrations: Cua Fleets: OpenAI Agents SDK, MCP; Fly.io Sprites: MCP, OpenAI Agents SDK

Trust

License: Cua Fleets: Not listed; Fly.io Sprites: Not listed
BYOC: Cua Fleets: Your AWS, Google Cloud, or Modal account; Fly.io Sprites: Not listed

Hourly cost

One sandbox running for one hour

Size

Cua Fleets

Fly.io Sprites

1 vCPU · 2 GiB: Cua Fleets: $0.089; Fly.io Sprites: $0.082
2 vCPU · 4 GiB: Cua Fleets: $0.179; Fly.io Sprites: $0.165
4 vCPU · 8 GiB: Cua Fleets: $0.357; Fly.io Sprites: $0.329

Compute only, at list rates.

Open the calculator

Which one fits

Based on the fields above

Cua Fleets fits when

You need a desktop in the sandbox.
You need the sandboxes in your own cloud account.
You need SOC 2.

Fly.io Sprites fits when

You want each sandbox in its own microVM.
You want the lower list price: $0.165 against $0.179 an hour for 2 vCPU and 4 GiB.
You need snapshots.
You need pause and resume.

More comparisons

See all comparisons

Cua Fleets

Fly.io Sprites

What is different

Full comparison

Pricing

Limits

Platform

Developer

Trust

Hourly cost

Which one fits

Cua Fleets fits when

Fly.io Sprites fits when

More comparisons

Related

Compare

Pricing

Browse