Quickstart
Install the SDK, authenticate, and run your first sandbox in under five minutes. Head to the Quickstart for setup steps and runnable examples in the CLI, Python, and TypeScript.How it works
Each sandbox is a microVM backed by a block-based filesystem and lazily mapped memory snapshots. That’s what keeps cold starts in the hundreds of milliseconds and lets suspend preserve the running process — filesystem, memory, and in-flight work — rather than doing a clean shutdown. During cluster updates and security patches, Tensorlake live-migrates running sandboxes to healthy hosts with only a brief pause — no restarts, no reconnection logic, no dropped process state.State and persistence
Sandboxes aren’t just for one-off execution. An agent can install dependencies, inspect outputs, write intermediate results to disk, and continue from where the previous step left off.- Suspend and resume — pause a named sandbox when it goes idle and bring it back on the next request, preserving state without keeping it running.
- Snapshots — capture the filesystem and memory of a sandbox as a reusable artifact, and restore it into a new sandbox later when you want to return to a known-good state.
- Clone — fork a running sandbox to start a second copy from the same filesystem and memory state. Useful for debugging, testing an alternative path, or continuing in parallel without touching the original.
- Sandbox Images — package a prepared environment as a reusable starting point and launch new sandboxes from that named image on demand.