Runtime Cloud is a hosted fleet of Firecracker microVMs that an agent, or the program driving it, creates, runs commands in, pauses, forks and deletes over an API.
It is sold as compute for AI-agent workloads rather than websites or long-lived servers. The commercial pitch is that CPU is billed on measured use with a very low idle floor, so a sandbox waiting on a language model costs almost nothing.
Twenty products sit behind one API, CLI, MCP server and SDK set: sandboxes, secrets, images, volumes, snapshots, previews, desktop, metrics, webhooks, OpenTelemetry, TCP ports, private networks and more.
Shown as the research found them. A contradiction means the provider's own pages disagree; an open question means the answer is not published.
- 01
A stopped sandbox keeps billing Open question
Only delete ends the storage charge. A stopped box is a bill, not a cleanup, and persistent: true bills memory around the clock.
- 02
Uptime was below the published promise Open question
The status page showed 96.37% over 7 days and 98.87% over 30 days against a 99% monthly promise at the time of research.
- 03
Free hours: every month or once? Contradiction
The start page says 100 free hours every month; the pricing and included-usage pages say an account that has never paid gets them once, across its first 30 days.
- 04
The canonical state list is not published Open question
The docs name transitions and mention starting, running, pausing, paused, resuming, stopping and stopped, but there is no quotable list of state strings.
- 05
One region, in Virginia Open question
Everything runs in us-east. There is no EU option, and no per-tenant residency control.
- 06
Very young Open question
A one-month-old repository, near-zero community discussion, and daily changelog entries including breaking changes. No preinstalled coding agents, and the vendor says no bridge harness has run on Runtime yet.