Plans and limits
Resource limits apply to each sandbox. Concurrency is the maximum number of sandboxes you can run at the same time.
The paid-plan memory limits are also subject to the sandbox resource ratio: allocate between 1 GB and 8 GB of RAM per vCPU. For example, a 16-vCPU Pro sandbox can allocate up to 64 GB of RAM, while a 2-vCPU sandbox can allocate up to 16 GB.
If you need a larger sandbox or an account-specific limit, contact support@tensorlake.ai.
Metered resource rates
Usage Credits and Pro deduct usage for sandbox CPU, RAM, root disk, and snapshot storage at these rates:
Rates are quoted per hour for readability, but runtime usage is measured by the second. CPU tracks active runtime execution, not allocated vCPU time is used. RAM and root disk are allocation-based while the sandbox is running. Snapshot storage is billed per GB-month while the sandbox is suspended.
Usage Credits
One compute unit (CU) is $0.01 of prepaid balance.
You can buy up to 10 packs at once, top up at any time, or enable threshold-based auto-refill. When the balance reaches zero, Tensorlake blocks new sandbox activity and stops running sandboxes instead of creating a postpaid overage. Add another pack to resume, or enable auto-refill to reduce interruptions.
Configure sandbox resources
The SDK and CLI default to 1 vCPU, 1 GB RAM, and a 10 GB root disk. Override those values when you create a sandbox, within your plan limits:- CLI
- Python
- TypeScript
disk_mb is expressed in MiB by the API even though plan limits and billing rates are displayed in GB. See Sandbox lifecycle: resources for all resource parameters and constraints.
View usage and invoices
Organization settings in the Tensorlake dashboard has two tabs for spend. The Usage tab shows metered charges for the selected billing cycle, the CPU-hours and GiB-hours behind those charges, and usage per day.
