Home / Compare / Lizard Sandboxes vs Tensorlake Sandboxes
Lizard Sandboxes vs Tensorlake Sandboxes
Verdict (2026-11-15): They tie at 76/100. Choose Lizard Sandboxes for large fleets of small sandboxes where a low flat hourly price matters more than idle-time billing. Choose Tensorlake Sandboxes for agent tool calls and harnesses that wait on model calls, since only active CPU time is billed.
Lizard Sandboxes
Highest scoreFirecracker microVM sandboxes at flat per-size hourly prices from $0.0081 for 1 vCPU / 2 GB, billed per second.
$19.00 a month
Tensorlake Sandboxes
Highest scoreFirecracker microVM sandboxes billed on active CPU time (20% floor), with suspend/resume, snapshots and SSH.
$17.95 a month
Score by part
Cost at four workloads
| Workload | Lizard Sandboxes | Tensorlake Sandboxes |
|---|---|---|
| Short tasks: 1 vCPU, 1 GiB, 50 h/month | $19.00 | $1.80 |
| Dev agent: 2 vCPU, 4 GiB, 176 h/month | $19.00 | $17.95 |
| Fleet: 2 vCPU, 4 GiB, 1,760 h/month | $28.51 | $179.52 |
| Always on: 4 vCPU, 8 GiB, 730 h/month | $23.65 | $189.80 |
Per month, cheapest plan for each, without storage, network or GPU. Lowest cost in bold.
Choose Lizard Sandboxes if
- Large fleets of small sandboxes where a low flat hourly price matters more than idle-time billing
- Agents that fork a running sandbox with memory and processes included
- Teams that also want to host apps and databases on the same plan
Choose Tensorlake Sandboxes if
- Agent tool calls and harnesses that wait on model calls, since only active CPU time is billed
- Named sandboxes used as SSH or IDE dev environments that suspend when idle and resume with processes intact
- Evals and RL rollouts that fork a warmed sandbox into many copies
Side by side
| Lizard Sandboxes | Tensorlake Sandboxes | |
|---|---|---|
| Category | agent sandbox | agent sandbox, dev box, GPU sandbox |
| Our score | 76/100 | 76/100 |
| Isolation | Firecracker microVM per sandbox with its own kernel | Firecracker microVM per sandbox (GPU sandboxes use gVisor) |
| vCPU per hour | — | $0.07 (active CPU only) |
| Memory per GiB-hour | — | $0.015 |
| Fixed size per hour | $0.0081 (Mini: 1 vCPU / 2 GB RAM / 10 GB disk) | — |
| Storage per GiB-month | $0.14 | $0.07 |
| Billing | per second | per second, billed in whole compute units ($0.01 each), pooled per organization |
| Free tier | 7-day Pro trial with $5 of usage; a card is required but nothing is charged during the 7 days. The trial runs at most 1 Small, 2 Mini and 2 Nano sandboxes at a time, in US regions only, and deletes each after at most 1 hour. | Free plan at $0 with no credit card: 1 sandbox at a time with 1 vCPU, 1 GB RAM and 10 GB disk, sessions up to 2 hours, unmetered. |
| Pause and resume | Yes | Yes |
| Snapshots | Yes | Yes |
| GPU | No | Yes |
| Custom images | No | Yes |
| Network controls | Not stated | Yes |
| Max session | 596 hours | Not stated |
| Max vCPU | 16 vCPU | 16 vCPU |
| Max memory | 32 GiB | 64 GiB |
| Open source | No | No |
| Self-host | No | Yes |
| SDKs and interfaces | JavaScript/TypeScript, Python, CLI, REST API | Python, TypeScript, CLI, REST API |
| Regions | US East (Virginia, us-east-1) and EU West (Limburg), chosen per sandbox. The trial runs only in US regions. | Region list not published; the docs state EU data residency is supported. Enterprise can run in your own AWS, GCP or Azure account. |
| Facts checked | 2026-11-15 | 2026-11-14 |
Lizard Sandboxes alternatives · Tensorlake Sandboxes alternatives
Sources
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Mini (1 vCPU, 2 GB RAM) at $0.0081/hour
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
1 vCPU · 2 GB RAM · 10 GB disk
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Large 8 vCPU · 16 GB RAM · 80 GB disk |$0.0648 per hour
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Pro costs $19 a month and includes $19 of usage for the whole platform: apps, databases, Sandboxes, storage and egress.
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Pro 5x ($99) and Pro 20x ($499) work the same way, include $99 and $499 of usage, and raise the sandbox limits.
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Pro starts with a 7-day trial that includes $5 of usage. You need a card to start it, but we charge nothing during the 7 days
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Persistent Volumes |$0.14 per GB/month
- Lizard Sandboxes: https://lizard.build/docs/platform/limits/, checked 2026-11-15:
Pro runs up to 40 vCPU of sandboxes at once, Pro 5x 220 and Pro 20x 1,200.
- Lizard Sandboxes: https://lizard.build/docs/platform/limits/, checked 2026-11-15:
Pro, Pro 5x and Pro 20x have no limit on sandbox starts.
- Lizard Sandboxes: https://lizard.build/docs/platform/limits/, checked 2026-11-15:
The trial runs 1 Small, 2 Mini and 2 Nano sandboxes at a time, only in US regions, and deletes each sandbox 1 hour after it starts at the latest.
- Lizard Sandboxes: https://lizard.build/docs/sandboxes/, checked 2026-11-15:
Sandboxes run as Firecracker microVMs, each with its own kernel.
- Lizard Sandboxes: https://lizard.build/docs/sandboxes/, checked 2026-11-15:
The public CLI does not provide a custom-template upload flow.
- Lizard Sandboxes: https://lizard.build, checked 2026-11-15:
For longer tasks you can remove the deadline; the VM then stops after 596 hours (about 24 days).
- Lizard Sandboxes: https://lizard.build, checked 2026-11-15:
Sandboxes run on CPUs only.
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
Big (16 vCPU, 32 GB RAM; paid plans only) at $0.1296/hour
- Lizard Sandboxes: https://lizard.build/pricing, checked 2026-11-15:
A paused sandbox costs $0.14 per GB-month of used disk space until you resume or delete it, and so does each snapshot until you delete it.
- Lizard Sandboxes: https://lizard.build/docs/sandboxes/, checked 2026-11-15:
Running processes and memory end, and a resume boots the sandbox fresh with its files.
- Lizard Sandboxes: https://lizard.build/docs/sandboxes/, checked 2026-11-15:
fork copies a running sandbox, memory and processes included
- Lizard Sandboxes: https://lizard.build/docs/platform/limits/, checked 2026-11-15:
During the trial, you can start 50 Small, 100 Mini and 100 Nano sandboxes in total across all your workspaces.
- Tensorlake Sandboxes: https://tensorlake.ai/pricing, checked 2026-11-14:
An idle 8-vCPU sandbox bills 1.6 vCPU; a busy one bills what it uses.
- Tensorlake Sandboxes: https://tensorlake.ai/pricing, checked 2026-11-14:
Includes 25,000 CU ($250 of usage) per billing cycle. Additional usage is billed at $0.01 per CU at the Pro rates below.
- Tensorlake Sandboxes: https://tensorlake.ai/pricing, checked 2026-11-14:
We block new sandbox activity and stop running sandboxes instead of turning the shortfall into an unexpected bill.
- Tensorlake Sandboxes: https://tensorlake.ai/pricing, checked 2026-11-14:
The NVIDIA H100 is $3.95 per GPU-hour.
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
Active CPU per core-hour | $0.07 | $0.042 | Custom
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
RAM per GB-hour | $0.015 | $0.009 | Custom
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
Root disk per GB-hour | $0.0002 | $0.0001 | Custom
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
Snapshot storage per GB-month | $0.07 | $0.07 | Custom
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
Rates are quoted per hour for readability, but runtime usage is measured by the second.
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
Pro | $250 / month + usage | 1,000 | 16 vCPU, 64 GB RAM, 100 GB root disk | Unlimited
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
Free | $0 forever | 1 | 1 vCPU, 1 GB RAM, 10 GB root disk | 2 hours
- Tensorlake Sandboxes: https://docs.tensorlake.ai/platform/billing, checked 2026-11-14:
allocate between 1 GB and 8 GB of RAM per vCPU
- Tensorlake Sandboxes: https://docs.tensorlake.ai/sandboxes/introduction, checked 2026-11-14:
GPU sandboxes use gVisor while CPU-only sandboxes run in VMs.
- Tensorlake Sandboxes: https://docs.tensorlake.ai/sandboxes/introduction, checked 2026-11-14:
Tensorlake is HIPAA and SOC 2 Type II compliant, supports EU data residency, and offers zero data retention.
- Tensorlake Sandboxes: https://docs.tensorlake.ai/sandboxes/lifecycle, checked 2026-11-14:
Named sandbox is paused. Consumes no compute; state is preserved for resume under the same sandbox ID.
- Tensorlake Sandboxes: https://docs.tensorlake.ai/sandboxes/gpu, checked 2026-11-14:
GPU sandboxes are available by request.
- Tensorlake Sandboxes: https://docs.tensorlake.ai/sandboxes/networking, checked 2026-11-14:
Restricting the sandbox's own outbound internet access
- Tensorlake Sandboxes: https://tensorlake.ai, checked 2026-11-14:
Each tool call and harness runs in its own microVM. No shared kernel, no cross-tenant state.
Questions
Is Lizard Sandboxes or Tensorlake Sandboxes better?
They tie at 76/100 on our published method. Choose Lizard Sandboxes for large fleets of small sandboxes where a low flat hourly price matters more than idle-time billing. Choose Tensorlake Sandboxes for agent tool calls and harnesses that wait on model calls, since only active CPU time is billed. Checked 2026-11-14.
Is Lizard Sandboxes or Tensorlake Sandboxes cheaper?
Tensorlake Sandboxes is cheaper: Lizard Sandboxes $19.00, Tensorlake Sandboxes $17.95 a month for 2 vCPU, 4 GiB, 176 hours a month (8 h × 22 days), CPU busy 30%.
How do Lizard Sandboxes and Tensorlake Sandboxes isolate code?
Lizard Sandboxes: Firecracker microVM per sandbox with its own kernel. Tensorlake Sandboxes: Firecracker microVM per sandbox (GPU sandboxes use gVisor).