← Providers
Tensorlake
provider: "tensorlake"
Bills active CPU (floor 20% of allocation); this is the full-use price; Pro plan is lower.
List price per hour
| 1 vCPU · 2 GB | $0.100 |
| 2 vCPU · 4 GB | $0.200 |
| 4 vCPU · 8 GB | $0.400 |
| 8 vCPU · 16 GB | max 4 vCPU |
| 16 vCPU · 32 GB | max 4 vCPU |
| 32 vCPU · 128 GB | max 4 vCPU |
- Source
- www.tensorlake.ai, 2026-11-04 (an estimate, not a bill)
- Billing
- CPU only while busy; shown with every core busy
- Plan
- none needed
Adapter
- Supports
- Exec + streaming · Files · Pause · Custom image
- Max size
- 4 vCPU · 16 GB
- Routing
- Chosen when it's the cheapest fit, or as a fallback
Measured on real accounts
- Real-account check
- not run yet
- tested against a mock of its API only
- Cold start
- not measured
- no benchmark run yet
- Succeeded
- not measured
- no benchmark run yet
- Size you get
- not measured
- no cost run yet
- Billed vs list price
- not measured
- no cost run yet
Help verify Tensorlake
Have a Tensorlake account? These run real sandboxes on it, for a few cents at most, and write result files that fill in the blanks above. Results never include your keys. Run them in a clone of the repo and open a pull request with the files: CI checks every file for keys and impossible numbers, and a maintainer reviews each one before it shows here.
terminal
npx @sandboxrouter/sdk check --provider tensorlake --save --by YOUR_GITHUB_USERNAME
npx @sandboxrouter/sdk bench --provider tensorlake --runs 5 --share --label "your city or cloud region" --by YOUR_GITHUB_USERNAME
npx @sandboxrouter/sdk cost run --provider tensorlake --minutes 10 --by YOUR_GITHUB_USERNAMEReal-account check, step by step
Not run on a real account yet; the adapter is tested against a mock of Tensorlake's API.
setup
npm i @sandboxrouter/sdk @tensorlakeai/tensorlake
export TENSORLAKE_API_KEY=...use Tensorlake
import { Router } from "@sandboxrouter/sdk";
const router = new Router();
const sbx = await router.create({}, { provider: "tensorlake" });
await sbx.exec("uname -a", { onStdout: (c) => process.stdout.write(c) });
await sbx.kill();