Sandbox pricing
Sandboxes run in the customer's cloud account, so the customer pays the cloud provider for them. Alien bills separately for deployment management. See Pricing for Alien's rates.
Prices on this page are AWS list prices as of October 2026 in us-east-1. The customer pays them on their own cloud bill. Official pricing: AWS Lambda, Google Cloud Agent Platform, Azure Container Apps.
Provider charges
| Platform | What you pay for |
|---|---|
| AWS | Lambda MicroVMs: compute per second, snapshot writes and reads on pause and resume, snapshot and image storage, and data transfer. |
| Google Cloud | Agent Platform: Agent Compute and Agent Memory. |
| Azure | Container Apps: sandbox compute. |
| Kubernetes | Cluster nodes, disks, load balancers, and network traffic. The two idle warm-pool pods per Sandbox reserve their declared CPU and memory. |
| Local | Your machine's resources. |
AWS rates
| Item | Price |
|---|---|
| Compute, vCPU | $0.0000276944 per vCPU-second |
| Compute, memory | $0.0000036667 per GB-second |
| Snapshot write (on pause) | $0.0038 per GB |
| Snapshot read (on start or resume) | $0.00155 per GB |
| Snapshot and image storage | $0.000111 per GB-hour, about $0.08 per GB-month |
These are Arm (Graviton) rates.
- You pay for the MicroVM's baseline while it runs, and for usage above baseline while it bursts. A MicroVM can burst to four times its baseline.
- Image storage has a 1-week minimum retention.
- The Lambda pricing page lists no free tier for MicroVMs.
Alien picks the MicroVM size from your .limits(). Without limits, it uses the 2 GiB baseline size (1 vCPU baseline, up to 4 vCPU and 8 GiB at peak). See AWS sizes.
Egress gateway
.egress("internet") on AWS and Kubernetes runs two gateway replicas with 0.25 vCPU and 512 MiB each. AWS places them behind an internal Network Load Balancer, and Kubernetes uses a cluster Service. The gateway runs even when no sandbox does.
Budget for:
- Gateway compute, and any new cluster instances or disks it needs.
- The internal load balancer, including capacity-unit charges.
- NAT, public IPs, logs, and data transfer.
Spare cluster capacity may cover the gateway. On AWS, a stack without containers gets the default compute cluster for it, so include that in the plan review. Policies are kept in memory, so there's no database charge.
.egress("none") and the older egress values add no gateway.
See EC2 pricing and Elastic Load Balancing pricing.
NAT
Reuse existing NAT where you can. Count it once, then add the extra traffic.
See AWS VPC pricing, Google Cloud NAT pricing, and Azure NAT Gateway pricing.
Example
10,000 sandboxes a month, each running for 5 minutes on AWS at the default size (2 GB, 1 vCPU baseline), with no bursting and no pause:
Running time: 10,000 × 300 s = 3,000,000 s
vCPU: 3,000,000 vCPU-s × $0.0000276944 = $83.08
Memory: 3,000,000 s × 2 GB = 6,000,000 GB-s × $0.0000036667 = $22.00
Compute total = $105.08Bursting above baseline adds charges for the time spent above it. Pausing adds snapshot charges for each pause and resume.
For other platforms, convert the same usage to hours and multiply by the provider's rates:
vCPU: 10,000 × 300 s / 3,600 = 833.33 vCPU-hours
Memory: 833.33 h × 2 GiB = 1,666.67 GiB-hoursThis covers sandbox compute only. Add gateway compute, the load balancer, NAT and data transfer, logs, image storage, builds, and Alien's fee.