Firecracker microVMs billed on measured CPU, with the strongest secret handling in this set.
Short answer: One always-on personal agent (2 vCPU / 4 GiB / 20 GiB) costs about $24.95 a month here, the 5th cheapest of the 11 providers that run it as described. The AI model adds about $14.70 a month on top (GLM 5.3, 30 requests a day at 40k tokens each, median zero-retention price; from $6.84 at the cheapest host). Fits well: An agent that mostly waits: measured CPU with a 50-millicore floor makes an idle hour about $0.03.
withruntime.com16 providersSources linked
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.
At a glance
Who it is for
Teams building agent products that execute model-written code, and teams migrating off a rival sandbox SDK: drop-in shims exist for E2B, Daytona, Vercel and Blaxel.
Isolation
Firecracker microVM on servers Runtime operates, with its own kernel; not a container and not gVisor. New sandboxes expose /dev/kvm, so nested virtualisation works. No GPU and no ARM: x86-64 only.
Sizes
No fixed size menu: any vCPU / memory / disk combination inside the bounds, which are 16 vCPU, 64 GiB of memory and 400 GiB of disk on a paid account. CPU is shared by default; reserved guarantees every vCPU at full price.
A personal agent here
About $24.95 a month for one always-on 2 vCPU / 4 GiB machine (2 vCPU / 4 GiB / 20 GiB), before the AI model. Change the numbers
Our reading of the sourced material on this page, not a provider claim.
Fits well
An agent that mostly waits: measured CPU with a 50-millicore floor makes an idle hour about $0.03.
A small team that needs SSO, SCIM, a 400-day audit log and per-key spend limits without an enterprise plan.
Secrets that must not enter the machine, plus OIDC tokens for AWS or GCP.
Fits badly
A buyer who needs a named founder, a funding history or a company older than a few months.
Multi-region or EU data residency: there is one region, in Virginia.
A workload that needs a Runtime-owned SOC 2 report.
How it bills
Model
Prepaid credit, no plan fee, no seats and no commitment.
Meter
Per second: $0.025 per active vCPU-hour measured, with a 50-millicore floor per sandbox, plus $0.0075 per reserved GiB-hour of memory. Storage while paused or stopped is $0.08 per decimal GB per 30-day month.
While stopped
Disk and saved memory blocks keep billing at the storage rate. Only delete ends the charge.
Plan fee
None publicly. Plans exist in a private beta with no published prices.
Minimum
No minimum billing period. Top-ups are $10 to $10,000, and an automatic top-up earns 5% extra credit.
Secrets the machine never holds: placeholders swapped into HTTPS headers for named hosts only.
OIDC workload identity that AWS and GCP can trust.
Pause with memory, and snapshots that keep memory by default.
SSO, SCIM, audit logs and roles free on every account.
Billed on measured CPU, so a box waiting on a model costs the floor, about $0.03 an hour.
Using it without writing code
Dashboard
Yes, a detailed console: a Home report with a Needs you section, sandboxes with Overview, Terminal, Files, Activity and Settings tabs, a limits page, and usage and billing with daily spend by product.
Without code
Partly, and only for the first step: one click starts a sandbox with a shell in the page on free hours. There are no app templates and no hosted agent, and the documented no-code path is pasting its llms.txt link into Claude Code, Codex or Cursor.
Signup
A Google sign-in, no card and no waitlist. Free usage needs a verified sign-in and is withheld from data-centre or VPN addresses until credit is added.
Docs and support
Extensive, every page dated, with llms.txt bundles. Support is an AI agent in the same call, with humans for billing, security and data loss. The status page is public and specific.
Capability checklist
Every capability the guide checks, with the catch where Runtime's version falls short. Compare all providers
The certificates on its trust page belong to suppliers, including its Virginia data centre. No Runtime-owned SOC 2 is claimed.
“Sandboxes, their disks and memory — Data center, Virginia — SOC 1, SOC 2 and SOC 3 Type 2; ISO 27001”withruntime.comdocs-confirmed
Caveats and contradictions
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.
“New accounts get 100 free hours of a 1 GB machine every month, no card”
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.