# Tenki Sandbox — Disposable Linux VMs for AI Agents (https://tenki.cloud/products/sandbox)

> For the complete documentation index, see [llms.txt](https://tenki.cloud/llms.txt)

# Full Linux computers for your AI agents.

Isolated VMs that start in under a second. Drive them from the SDK or CLI.

[Create a Sandbox](https://app.tenki.cloud/auth/registration) · Onboard via Agent (copies a prompt that points your coding agent at [https://tenki.cloud/skill.md](https://tenki.cloud/skill.md))

Companies deploy faster with Tenki.

## Built for real work — Prepare, run, pause, branch, share.

- **Start with your tools installed** — Define the environment once. Launch from it every time. [Build a template](https://tenki.cloud/docs/sandbox/templates.md).
- **A real VM, not a container** — Root, Docker, systemd, any package. [Explore the environment](https://tenki.cloud/docs/sandbox/base-image.md).
- **Pause and continue later** — Stop paying. Resume with memory and files intact. [Explore the lifecycle](https://tenki.cloud/docs/sandbox/sessions.md#manage-a-session).
- **Branch from a checkpoint** — Snapshot disk and memory. Fork sessions from it. [Work with snapshots](https://tenki.cloud/docs/sandbox/snapshots.md).
- **Share a working preview** — Expose a port, get a URL. [Create a preview URL](https://tenki.cloud/docs/sandbox/sessions.md#port-exposure-and-networking).
- **Keep data across sessions** — Persistent volumes for caches, repos, and datasets. [Attach a volume](https://tenki.cloud/docs/sandbox/volumes.md).

## Our infrastructure — Your custom image, running in under a second.

We own the compute, storage, and network, so the whole startup path is built around your image.

Your image is already on disk in the Ceph storage cluster (tools, dependencies, project files). The compute node mounts it in under a second and reserves cores for your session. Owned end-to-end. [Create a custom image](https://tenki.cloud/docs/sandbox/templates.md).

### Owned end-to-end.

Compute, Ceph storage, switches, power, and uplink are ours.

### Mount the disk. Skip the copy.

Your disk mounts straight from Ceph. Nothing is copied before boot.

## Sandbox SDKs and CLI — Drive sandboxes from your terminal or code.

Create a VM, run a command, read the result.

[Quickstart](https://tenki.cloud/docs/sandbox/quickstart.md) · [Full walkthrough](https://tenki.cloud/docs/sandbox/recipes.md)

```typescript
// npm install @tenkicloud/sandbox
import { TenkiSandbox } from "@tenkicloud/sandbox";

const sandbox = new TenkiSandbox();

await using session = await sandbox.createAndWait({
  cpuCores: 2,
  memoryMb: 4096,
});

const result = await session.exec("bash", {
  args: ["-lc", "uname -a && whoami"],
});

console.log(result.stdout);
```

The same sample is available for Go, Python, and the CLI.

## Pricing and Limits — Pay for what runs. Upgrade your workspace to raise limits.

| Compute      | Per Hour  | Per Second  |
| ------------ | --------- | ----------- |
| CPU · Core   | $0.0504   | $0.000014   |
| Memory · GiB | $0.0162   | $0.0000045  |
| Disk · GiB   | $0.000108 | $0.00000003 |

| Resources       | Starter Workspace | Team Workspace |
| --------------- | ----------------- | -------------- |
| CPU per VM      | Up to 4 cores     | Up to 16 cores |
| RAM per VM      | Up to 8 GB        | Up to 64 GB    |
| Storage         | 100 GB            | 1,000 GB       |
| Active Sessions | 5                 | 100            |
| Preview URLs    | 20                | 20             |

Billed per second. Hourly rate shown for reference. First 5 GiB of disk free. [View pricing](https://tenki.cloud/pricing)

## Sandbox Security — Enterprise-grade security.

Each sandbox is a disposable, hardware-isolated VM.

- **Hardware-isolated VMs** — Its own kernel, not a shared-kernel container.
- **Wiped on teardown** — Disk and memory are gone when the session ends.
- **Secrets never cross boundaries** — Credentials are scoped to one session.
- **Encrypted in transit** — Tunneled, authenticated connections. No public IPs.

Backed by the compliance program of our parent company, Luxor Technology. [How Tenki protects customers](https://tenki.cloud/company/security)

## Testimonials — Don't believe us. Believe them.

Customer quotes from founders, CTOs, and engineering managers on Tenki's speed, cost savings, and support.

## FAQs

Have a question we haven't answered? Reach out to hello@tenki.cloud.

### What is a sandbox?

A sandbox is an isolated, fully managed compute environment where developers and AI coding agents can write, run, and test code without affecting production systems. Think of it as a disposable virtual machine spun up on demand.

### How fast do sandboxes start?

Tenki provisions sandboxes from custom images in under a second, including your tools and dependencies. Sandbox disks are mounted directly from our dedicated Ceph storage cluster instead of provisioned from the compute node’s local drive. This keeps provisioning fast for your own environment as well as our base images.

### Is this a good fit for AI coding agents?

Full VM sandboxes are a great fit for agents that need to run tests, compile code, or interact with Docker. Every agent task gets its own isolated workspace, so agents can work with root access without ever touching your host machine.

### Can I run Docker inside a sandbox?

Yes. Full VM-based sandboxes support Docker, system packages, and background services. This makes them ideal for integration tests and workflows that mirror a CI/CD environment exactly.

### Can I customize the environment with my own dependencies?

Yes. Define a typed template with your repository, dependencies, and build steps, then build it into a reusable image. You can also snapshot a running sandbox and start new sessions from that saved state. Templates do not currently accept Dockerfiles.

### What happens when I pause or terminate a sandbox?

Pausing stops compute charges and preserves memory and durable files so you can resume later. Active connections close and /tmp is cleared; keep durable files under /home/tenki or on a volume. A non-sticky session is paused automatically when it reaches its maximum duration. Terminating ends the session permanently; saved snapshots and persistent volumes are managed separately.

### How does pricing work?

Usage is metered per second across CPU, memory, and disk. Pausing a sandbox stops compute charges. Sandboxes are not paused for inactivity: a running sandbox accrues compute charges until you pause or terminate it, or until a non-sticky session reaches its maximum duration and is paused. The first 5 GiB of disk is included, and resource limits scale with your workspace plan.

### How do I get started?

Spin up your first environment in seconds with the TypeScript, Go, or Python SDK, or the CLI.