Runtime vs Tenki Sandbox
Choose Runtime for cost-sensitive agent workloads with many short runs, where active-CPU billing and a free monthly allowance matter; choose Tenki Sandbox for coding agents that need a full Linux VM with Docker and systemd, pausable between tasks, at per-second rates. Runtime uses Firecracker microVM isolation; Tenki Sandbox uses Single-tenant VM isolation.
Key differences between Runtime and Tenki Sandbox
- Isolation: Runtime uses Firecracker microVM; Tenki Sandbox uses Single-tenant VM.
- Session length: No limit documented (Runtime) versus Configurable; sticky = unlimited (Tenki Sandbox).
- SDKs and interfaces: Only Runtime lists Ruby, Java, REST API and MCP server.
What they have in common
- Both companies are based in the United States.
- Both are hosted platforms.
- Neither is open source.
- Both support snapshots.
- Both can pause and resume a sandbox.
- Both list TypeScript, Python, Go and CLI.
Runtime vs Tenki Sandbox at a glance
| Attribute | Runtime | Tenki Sandbox |
|---|---|---|
| What it is | Firecracker microVM sandboxes billed on active CPU at $0.025 per vCPU-hour, with pause that keeps memory, forks, SDKs in five languages and no plan fee. | Full Linux VMs for agents from the Tenki CI-runner company, booting from Ceph-backed disks in under a second (claimed), with pause, memory snapshots, forks and volumes at per-second rates. |
| Type | Hosted platform | Hosted platform |
| Isolation | Firecracker microVM with its own Linux kernel, disk and memory per sandbox, on dedicated servers Runtime operates | Hardware-isolated single-tenant VM with its own kernel; hypervisor not named; disks mount from a Ceph cluster |
| Open source | No | No |
| Self-host / BYOC | Not documented / Not documented | Not documented / Not documented |
| SDKs | JavaScript/TypeScript, Python, Go, Ruby, Java, CLI, REST API, MCP server | JavaScript/TypeScript, Python, Go, CLI |
| Cold start (vendor claim) | Runtime measures create and exec from outside every one to five minutes and publishes p50/p95/p99 on its speed page; the September 2026 figures were taken down on 27 October 2026, so no current figure is published | Website: "Isolated VMs that start in under a second" and "Your custom image, running in under a second" (vendor claims) |
| Max session | No maximum documented; a sandbox pauses itself after 300 seconds of inactivity by default (idlePauseSeconds 60–86,400, or 0 for never) | Maximum duration is set per session (default not stated); non-sticky sessions pause automatically at their maximum; sticky sessions run until terminated |
| Persistence | Pause keeps memory and processes; paused sandboxes are kept while the account has credit or for 1–365 days as set (30 days after credit runs out with a card or prior top-up, 7 days otherwise); snapshots of running or paused sandboxes; forks of 1–10 running copies with memory and processes; volumes backed up daily; S3, R2 and GCS bucket mounts | Pause preserves memory and durable files (/home/tenki and volumes; /tmp survives a pause but is cleared on snapshot) and stops compute charges; snapshots capture disk and memory and can be forked; persistent volumes keep data across sessions |
| Snapshots / pause | Yes / Yes | Yes / Yes |
| GPU | Not documented | Not documented |
| Networking | Per-sandbox allow and deny lists, or internet off; sandboxes reach only the public internet, private addresses refused; HTTPS previews on runtimehost.com (private by default with rotatable tokens), custom domains, public TCP ports, WireGuard private networks and a dedicated outbound IPv4 ($5 per 30 days); secrets substituted by the host on outbound requests | Inbound and outbound networking on by default and fixed at create time; outbound allowlists up to 256 domains and 64 IPv4 CIDRs; expose_port creates authenticated, tunnelled preview URLs with optional TTL; no public IPs |
| Pricing | $0.025 per active vCPU-hour and $0.0075 per reserved GiB-hour, billed per second; a waiting sandbox bills memory plus a 0.05 vCPU floor; paused sandboxes, snapshots and images $0.08 per GB per 30-day month; volumes about $0.11 per GiB per 30 days; outbound traffic free to 100 GiB a month then $0.02 per GB; no plan, seat or minimum fee | Per second: vCPU $0.000014 ($0.0504/hour), memory $0.0000045 per GiB ($0.0162/GiB-hour), disk $0.00000003 per GiB ($0.000108/GiB-hour, first 5 GiB free), kept storage $0.000000076 per GiB-second. Starter $0; Team $250/month ($200/month billed yearly) with $100 monthly credits, up to 100 concurrent sessions and 16 cores/64 GB; Enterprise custom |
| Free tier | 100 free hours of a 1 GB machine (100 GiB-hours of memory, 25 vCPU-hours of active CPU) in the first 30 days with no card, renewing monthly once the account has paid; without credit up to 4 sandboxes at once of 2 vCPU and 4 GiB | Starter: $100 one-time credit (granted when a payment method is added), up to 5 concurrent sessions, 4 cores/8 GB, 100 GiB storage |
| Compliance | No certification of Runtime itself is named; the trust page lists subprocessor attestations (Virginia data centre SOC 1/2/3 Type 2 and ISO 27001; Neon and Vercel SOC 2 Type 2); DPA included in every account; SAML/OIDC SSO and SCIM free; 99% monthly API uptime promise on paid accounts | SOC 2 Type II through parent Luxor Technology's programme (report under NDA); compute in SOC 2-attested and ISO 27001-certified data centres; GDPR alignment with certification on the roadmap |
| Regions | All processing in one region in Virginia, United States (trust page); limits are counted per region | Multi-region availability mentioned; regions not listed (preview URL example uses a "us" subdomain) |
| Company headquarters | Denver, Colorado, United States | Seattle, Washington, United States |
| Good fit for | Cost-sensitive agent workloads with many short runs, where active-CPU billing and a free monthly allowance matter | Coding agents that need a full Linux VM with Docker and systemd, pausable between tasks, at per-second rates |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Runtime
- You want the lowest published per-vCPU rate with billing only for active CPU.
- You need SDKs in Go, Ruby or Java as well as Python and TypeScript.
- You want SSO, SCIM, audit logging and a DPA without an enterprise contract.
- You run many short agent jobs and want a renewing free monthly allowance.
Reasons to choose Tenki Sandbox
- You want a full VM with Docker and systemd rather than a container-shaped sandbox.
- You need pause-and-resume with memory kept and no charge while paused.
- You want Go support alongside TypeScript and Python SDKs.
- You are already using Tenki runners and want one credit balance.
Trade-offs to check first
- Runtime: Single region: everything runs in one region in Virginia, United States.
- Runtime: No startup latency figures are currently published, and no certification of Runtime itself is named.
- Tenki Sandbox: Hypervisor, region list and default session duration are not documented.
- Tenki Sandbox: SOC 2 Type II is through parent company Luxor Technology's programme, with reports under NDA.
Both are worth piloting with your own image and region. See the full Runtime profile and Tenki Sandbox profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Runtime or Tenki Sandbox better for AI agents?
What is the difference between Runtime and Tenki Sandbox?
Which is open source, Runtime or Tenki Sandbox?
How do Runtime and Tenki Sandbox isolate code?
How does Runtime pricing compare with Tenki Sandbox?
How long can sessions run on Runtime and Tenki Sandbox?
idlePauseSeconds 60–86,400, or 0 for never). Tenki Sandbox: Maximum duration is set per session (default not stated); non-sticky sessions pause automatically at their maximum; sticky sessions run until terminated.Do Runtime and Tenki Sandbox support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Runtime vs Tenki Sandbox. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/withruntime-vs-tenki-sandbox/