tensorlake

Build agents with sandboxes and serverless orchestration runtime

Tensorlake is a compute infrastructure platform for building agentic applications with sandboxes.

The Sandbox API creates MicroVM sandboxes which you can use to run agents, or use them as an isolated environment for running tools or LLM generated code.

In addition to stateful VMs, you can also add long running orchestration capabilities to Agents using a serverless function runtime with fan-out capabilities.

Sandboxes

Tensorlake Sandboxes are stateful Firecracker MicroVMs built for instant, stateful execution environments for AI agents — spin up millions of VMs with near-SSD filesystem performance.

Key capabilities

Fastest Filesystem I/O — Block-based storage achieving near-SSD speeds inside virtual machines. In SQLite benchmarks (2 vCPUs, 4 GB RAM), Tensorlake completes in 2.45s vs Vercel 3.00s (1.2×), E2B 3.92s (1.6×), Modal 4.66s (1.9×), and Daytona 5.51s (2.2×).
Fast startup — Sandboxes created in under a second via Lattice, a dynamic cluster scheduler.
Snapshots & cloning — Snapshot at any point to create durable memory and filesystem checkpoints; clone running sandboxes instantaneously across machines.
Auto suspend/resume — Sandboxes suspend when idle and resume in under a second without losing any memory or filesystem state.
Live migration — Sandboxes automatically move between machines during updates with only a brief pause of a few seconds.
Scale — Supports up to 5 million sandboxes in a single project.

Python SDK Installation

pip install tensorlake

CLI Installation

The tl CLI is distributed as a standalone binary, not through PyPI or npm. Install it with the install script:

curl -fsSL https://tensorlake.ai/install | sh

Setup

export TENSORLAKE_API_KEY="your-api-key"
tl login

Create Your First Sandbox (CLI)

Create a sandbox, run a command, and clean up:

# Create a sandbox
tl sbx create

# Run a command inside it
tl sbx exec <sandbox-id> -- sh -lc "printf 'Hello from the sandbox!\n'"

# Copy a file into the sandbox
tl sbx cp ./my_script.py <sandbox-id>:/tmp/my_script.py

# Open an interactive terminal
tl sbx ssh <sandbox-id>

# Block all outbound internet access on a running sandbox
tl sbx update <sandbox-id> --no-internet

# Allow outbound traffic only to selected destinations
tl sbx update <sandbox-id> --network-allow api.example.com

# Remove the network policy and restore unrestricted outbound access
tl sbx update <sandbox-id> --clear-network

# Terminate when done
tl sbx terminate <sandbox-id>

Omit --image to use Tensorlake's default managed environment. To select a custom environment, pass the name of a registered Sandbox Image; arbitrary Docker image references are not supported.

Create a Sandbox Programmatically

from tensorlake.sandbox import SandboxClient

client = SandboxClient.for_cloud(api_key="your-api-key")

# Create a sandbox and connect to it
with client.create_and_connect() as sandbox:
    # Run a command
    result = sandbox.run("sh", ["-lc", "printf 'Hello from the sandbox!\\n'"])
    print(result.stdout)  # "Hello from the sandbox!"

    # Write and read files
    sandbox.write_file("/tmp/data.txt", b"some data")
    content = sandbox.read_file("/tmp/data.txt")

    # Start a long-running process
    proc = sandbox.start_process("sleep", ["300"])
    print(proc.pid)

# Sandbox is automatically terminated when the context manager exits

Snapshots

Save the state of a sandbox and restore it later:

# Snapshot a running sandbox
snapshot = client.snapshot_and_wait(sandbox_id)

# Later, create a new sandbox from the snapshot
with client.create_and_connect(snapshot_id=snapshot.snapshot_id) as sandbox:
    # Picks up right where you left off
    result = sandbox.run("ls", ["/tmp"])
    print(result.stdout)

Sandbox Pools

Pre-warm containers for fast startup:

from tensorlake.sandbox import FileSystemMount, NetworkConfig

# Create a pool with warm containers and no internet access
pool = client.create_pool(
    image="tensorlake/ubuntu-minimal",
    warm_containers=3,
    network=NetworkConfig(allow_internet_access=False),
)

# Claim a sandbox instantly from the pool. Claim-specific file systems are
# mounted before the sandbox is reported as running.
resp = client.claim(
    pool.pool_id,
    file_systems=[
        FileSystemMount(
            file_system_id="file_system_abc",
            mount_path="/mnt/skills",
        )
    ],
)
sandbox = client.connect(resp.sandbox_id)

# Named sandboxes can be reconnected later by name
named = client.create(name="stable-name")
sandbox = client.connect("stable-name")

Set the pool network policy when you create the pool, replace it later with a pool update, or pass CLEAR_NETWORK_POLICY (Python) / null (TypeScript) to remove it. On a change the service recycles the pool's unclaimed warm containers onto the new policy, while containers already claimed by sandboxes keep the policy they booted with.

Sandbox startup errors include the server's reason and actionable diagnostic. The Python and TypeScript RemoteAPIError exposes structured failure fields; the CLI shows the same details in create/copy errors and tl sbx describe. See sandbox failure diagnostics for error handling examples.

Cloud Volumes

FilesystemClient manages durable, versioned file trees without mounting them. SDK writes hash files locally, upload missing 64 MiB parts directly to checksum-bound object-store URLs, and then atomically publish metadata. Reads resolve an authenticated immutable plan and fetch the selected records directly from signed object-store URLs. File payloads normally do not pass through the Tensorlake API service.

import { FilesystemClient } from "tensorlake";

const client = new FilesystemClient({
  apiKey: "your-api-key",
});
const fs = await client.create("agent-artifacts");

// In-memory data; all changes become visible atomically.
await fs.writeFiles({
  "run/config.json": JSON.stringify({ model: "gpt-5" }),
  "run/input.txt": "hello",
});

// Multi-GiB files use bounded memory and stream directly to object storage.
await fs.writeFileFromPath("models/weights.bin", "./weights.bin");

// These reuse immutable content references and transfer no payload bytes.
await fs.copyFile("run/input.txt", "run/input-copy.txt");
await fs.moveFile("run/config.json", "archive/config.json");

// One request returns only the selected bytes plus full-file identity/size.
const read = await fs.readFileWithMetadata("models/weights.bin", {
  range: { offset: 0, length: 1024 * 1024 },
});

// Snapshot retention and forks are metadata-only operations.
const snapshot = await fs.snapshot("ready for evaluation");
const fork = await client.fork("agent-artifacts-eval", fs.name, snapshot.id);
await fork.writeFile("results/score.txt", "0.98");

await fs.deleteSnapshot(snapshot.id);

writeFile() and writeFiles() accept bytes already in memory. Prefer writeFileFromPath() or writeFilesFromPaths() for large local files so neither JavaScript nor Rust retains the complete payload. A successful write is durable before it returns, but only the live head is retained automatically; snapshot() pins the current head permanently in one client/server round trip. readFileWithMetadata() returns immutable content identity and total size with the bytes; its optional range downloads only overlapping immutable records. The SDK bounds every response, verifies stored and logical content checksums, and falls back to the authenticated service only when the object store cannot honor the signed range. Deleting a snapshot releases that retention root, while bytes still reachable from a live head, another snapshot, a fork, or a mount remain durable.

Orchestrate

Create orchestration APIs on a distributed runtime with automatic scaling, fan-out capabilities and built-in tracking. The orchestration APIs can be invoked using HTTP requests or using the Python SDK.

Quickstart

Decorate your entrypoint with @application() and functions with @function(). Each function runs in its own isolated sandbox.

Example: City guide using OpenAI Agents with web search and code execution:

from agents import Agent, Runner
from agents.tool import WebSearchTool, function_tool
from tensorlake.applications import application, function, Image

# Define the image with necessary dependencies
FUNCTION_CONTAINER_IMAGE = Image(base_image="python:3.11-slim", name="city_guide_image").run(
    "pip install openai openai-agents"
)

@function_tool
@function(
    description="Gets the weather for a city using an OpenAI Agent with web search",
    secrets=["OPENAI_API_KEY"],
    image=FUNCTION_CONTAINER_IMAGE,
)
def get_weather_tool(city: str) -> str:
    """Uses an OpenAI Agent with WebSearchTool to find current weather."""
    agent = Agent(
        name="Weather Reporter",
        instructions="Use web search to find current weather in Fahrenheit for the city.",
        tools=[WebSearchTool()],  # Agent can search the web
    )
    result = Runner.run_sync(agent, f"City: {city}")
    return result.final_output.strip()

@application(tags={"type": "example", "use_case": "city_guide"})
@function(
    description="Creates a guide with temperature conversion using function_tool",
    secrets=["OPENAI_API_KEY"],
    image=FUNCTION_CONTAINER_IMAGE,
)
def city_guide_app(city: str) -> str:
    """Uses an OpenAI Agent with function_tool to run Python code for conversion."""

    @function_tool
    def convert_to_celsius_tool(python_code: str) -> float:
        """Converts Fahrenheit to Celsius - runs as Python code via Agent."""
        return float(eval(python_code))

    agent = Agent(
        name="Guide Creator",
        instructions="Using the appropriate tools, get the weather for the purposes of the guide. If the city uses Celsius, call convert_to_celsius_tool to convert the temperature, passing in the code needed to convert the temperature to Celsius. Create a friendly guide that references the temperature of the city in Celsius if the city typically uses Celsius, otherwise reference the temperature in Fahrenheit. Only reference Celsius or Fahrenheit, not both.",
        tools=[get_weather_tool, convert_to_celsius_tool],  # Agent can execute this Python function
    )
    result = Runner.run_sync(agent, f"City: {city}")
    return result.final_output.strip()

Deploy to Tensorlake

Set your API keys:

export TENSORLAKE_API_KEY="your-api-key"
tl secrets set OPENAI_API_KEY "your-openai-key"

Deploy:

tl deploy examples/readme_example/city_guide.py

tl deploy builds a version-scoped runtime image for every function and stores its registered sandbox-template name in the application manifest. The image contains the dependencies declared by Image, the language runner, and the native function-agent core. Application source remains a separate ZIP that is uploaded with the manifest; it is not copied into the runtime image. Reusing an application version with different code or configuration is rejected; an identical redeploy is idempotent. Image and application requests normally route through TENSORLAKE_API_URL so ingress can authenticate them and attach trusted project identity. Application deployment, invocation, output, listing, and inspection all use that same origin. Trusted split local installations can set TENSORLAKE_IMAGE_SERVICE_URL and TENSORLAKE_FUNCTION_SERVICE_URL independently.

Call via HTTP

# Invoke the application
curl https://api.tensorlake.ai/applications/city_guide_app \
  -H "Authorization: Bearer $TENSORLAKE_API_KEY" \
  --json '"San Francisco"'
# Returns: {"request_id": "beae8736ece31ef9"}

# Get the result
curl https://api.tensorlake.ai/applications/city_guide_app/requests/{request_id}/output \
  -H "Authorization: Bearer $TENSORLAKE_API_KEY"

# Stream results with SSE
curl https://api.tensorlake.ai/applications/city_guide_app \
  -H "Authorization: Bearer $TENSORLAKE_API_KEY" \
  -H "Accept: text/event-stream" \
  --json '"San Francisco"'

FAQ

What is Tensorlake? Tensorlake is the sandbox-native cloud for AI agents — a compute platform for securely running untrusted, LLM-generated code in isolated sandboxes and orchestrating agentic applications at scale.

How do I run untrusted or LLM-generated code safely? Each Tensorlake sandbox is an isolated Firecracker MicroVM, so untrusted or LLM-generated code runs in a hardware-virtualized environment separate from your infrastructure and other sandboxes. Create one with the Python or TypeScript SDK, or the CLI, in a few lines.

How is Tensorlake different from E2B, Modal, or Daytona? Tensorlake is built for heavy filesystem I/O, fast startup, and large-scale fan-out. In SQLite benchmarks (2 vCPUs, 4 GB RAM) it completes in 2.45s versus E2B (3.92s), Modal (4.66s), and Daytona (5.51s), and it supports snapshots, auto suspend/resume, live migration, and up to 5 million sandboxes per project.

Can I checkpoint and resume an AI agent? Yes. Snapshot a running sandbox at any point to capture both memory and filesystem state, then create a new sandbox from that snapshot to pick up exactly where you left off. Sandboxes also auto-suspend when idle and resume in under a second without losing state.

How fast do sandboxes start? Sandboxes are created in under a second via Lattice, a dynamic cluster scheduler. For even faster starts, use sandbox pools to keep warm containers ready to claim instantly.

How do I run code interpreter / tool execution for an LLM agent? Spin up a sandbox as an isolated execution environment for an agent's tools or generated code, run commands or processes inside it, read and write files, and terminate it when done — all from the Python or TypeScript SDK, or the CLI.

What languages and interfaces are supported? Tensorlake provides a Python SDK, a TypeScript SDK, and a standalone CLI (tl), plus an HTTP API for invoking orchestration applications.

How do I get started? Sign up at cloud.tensorlake.ai, run pip install tensorlake for the Python SDK, install the CLI with curl -fsSL https://tensorlake.ai/install | sh, set your TENSORLAKE_API_KEY, and create your first sandbox. See the documentation for full guides.

Learn More

Metadata

Release files for tensorlake 0.5.128

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for tensorlake 0.5.128
File	Interpreter	ABI	Platform	Reset
tensorlake-0.5.128-cp310-abi3-win_amd64.whl 9.4 MB Sep 9, 2026	CPython 3.10	abi3	Windows x86-64	Details
tensorlake-0.5.128-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl 8.8 MB Sep 9, 2026	CPython 3.10	abi3	Linux glibc 2.17+ x86-64	Details
tensorlake-0.5.128-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl 8.5 MB Sep 9, 2026	CPython 3.10	abi3	Linux glibc 2.17+ ARM64	Details
tensorlake-0.5.128-cp310-abi3-macosx_11_0_arm64.whl 8.2 MB Sep 9, 2026	CPython 3.10	abi3	macOS 11.0+ ARM64	Details

Total release size: 34.9 MB

Release files / tensorlake-0.5.128-cp310-abi3-win_amd64.whl

Download URL	tensorlake-0.5.128-cp310-abi3-win_amd64.whl
Size	9.4 MB
Tags	CPython 3.10 Windows x86-64 abi3
SHA-256 checksum How to use checksums	`2874728987b0e78ff3259178c1278da8311fe12289689a31da658a9c79a427f1`
BLAKE2b-256 checksum How to use checksums	`b3581aa5ba696d55abfaa56c6fc39e1fb9552338f43916efdca29199702ebf9e`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/tensorlakeai/tensorlake
Publishing commit: github.com/tensorlakeai/tensorlake/tree/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae

Workflow

Publishing configuration: github.com/tensorlakeai/tensorlake/blob/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae/.github/workflows/publish_pypi.yaml
Publishing logs: github.com/tensorlakeai/tensorlake/actions/runs/34301892050/attempts/1

Artifact

Subject: tensorlake-0.5.128-cp310-abi3-win_amd64.whl
SHA-256 checksum: 2874728987b0e78ff3259178c1278da8311fe12289689a31da658a9c79a427f1 Verifying attestations

Release files / tensorlake-0.5.128-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL	tensorlake-0.5.128-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size	8.8 MB
Tags	CPython 3.10 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum How to use checksums	`1edf20aca687da313cfa27bef58ced92f42749f9ec6e1bb143b23df9f9f7ea1e`
BLAKE2b-256 checksum How to use checksums	`1c660942a1ef4716387092f80551a80c6e4f549954bc952d28c5318b9188a65c`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/tensorlakeai/tensorlake
Publishing commit: github.com/tensorlakeai/tensorlake/tree/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae

Workflow

Publishing configuration: github.com/tensorlakeai/tensorlake/blob/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae/.github/workflows/publish_pypi.yaml
Publishing logs: github.com/tensorlakeai/tensorlake/actions/runs/34301892050/attempts/1

Artifact

Subject: tensorlake-0.5.128-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
SHA-256 checksum: 1edf20aca687da313cfa27bef58ced92f42749f9ec6e1bb143b23df9f9f7ea1e Verifying attestations

Release files / tensorlake-0.5.128-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL	tensorlake-0.5.128-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size	8.5 MB
Tags	CPython 3.10 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum How to use checksums	`b7a58c10f6312dd2f6dbebcc05b84dd1c434f9558d4dd495bfd2f340b22f0aab`
BLAKE2b-256 checksum How to use checksums	`91fbcefb17a7c99a2a2256c3ced76660f88c339bd0de4eb249c1f110a90f3118`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/tensorlakeai/tensorlake
Publishing commit: github.com/tensorlakeai/tensorlake/tree/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae

Workflow

Publishing configuration: github.com/tensorlakeai/tensorlake/blob/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae/.github/workflows/publish_pypi.yaml
Publishing logs: github.com/tensorlakeai/tensorlake/actions/runs/34301892050/attempts/1

Artifact

Subject: tensorlake-0.5.128-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
SHA-256 checksum: b7a58c10f6312dd2f6dbebcc05b84dd1c434f9558d4dd495bfd2f340b22f0aab Verifying attestations

Release files / tensorlake-0.5.128-cp310-abi3-macosx_11_0_arm64.whl

Download URL	tensorlake-0.5.128-cp310-abi3-macosx_11_0_arm64.whl
Size	8.2 MB
Tags	CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum How to use checksums	`939d50b8001c37cb700c11d4440648934685159158e106eda962b0102564147d`
BLAKE2b-256 checksum How to use checksums	`397147d2db46a53a9e89a87f52a26419b91cff8962c8aeb70185e3fef8491556`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/tensorlakeai/tensorlake
Publishing commit: github.com/tensorlakeai/tensorlake/tree/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae

Workflow

Publishing configuration: github.com/tensorlakeai/tensorlake/blob/faea1f5bdbba35a6d8a9c7fa77f15ed7e7da6fae/.github/workflows/publish_pypi.yaml
Publishing logs: github.com/tensorlakeai/tensorlake/actions/runs/34301892050/attempts/1

Artifact

Subject: tensorlake-0.5.128-cp310-abi3-macosx_11_0_arm64.whl
SHA-256 checksum: 939d50b8001c37cb700c11d4440648934685159158e106eda962b0102564147d Verifying attestations