Skip to main content
Tensorlake Sandboxes are isolated MicroVM environments that start quickly and keep memory and filesystem state across suspend and resume. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to tensorlake and these variables:
  • TENSORLAKE_API_KEY
For CI runners, CostGraph sets CPU and memory and boots providerTemplate as the Tensorlake image.

​
Key and permissions

TENSORLAKE_API_KEY is a Tensorlake project API key (tl_apiKey_…) created in the Tensorlake Dashboard: select the project, then create an API key. keys are not scoped: each key lives in one project with the same permissions as a project member, and cannot be restricted to specific endpoints or given org-level permissions. Source: https://docs.tensorlake.ai/platform/authentication Sources: docs.tensorlake.ai: authentication, docs.tensorlake.ai: billing, docs.tensorlake.ai: create, docs.tensorlake.ai: introduction.

​
Limits

  • Max session duration: Free 2 h, Usage Credits 24 h, Pro and Enterprise unlimited; default timeout 600 s; unnamed sandboxes are discarded at timeout, named ones suspend. (source)
  • Per sandbox: Free 1 vCPU/1 GB; Usage Credits 4 vCPU/16 GB; Pro 16 vCPU/64 GB; root disk 10-100 GB; RAM 1-8 GB per vCPU on paid plans. (source)
  • Concurrent sandboxes: Free 1, Usage Credits up to 100, Pro 1,000, Enterprise unlimited. (source)
  • API timeout_secs maxima: Free unverified 1 h, Free verified 2 h, On-Demand 24 h (0 = plan max). (source)
  • Regions and CPU architecture not documented; GPU sandboxes use gVisor, CPU-only run in VMs. (source)