> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tembo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Secure, isolated environments where coding agents execute sessions.

Every session runs in its own isolated sandbox. Sandboxes are ephemeral: spun up for the session, destroyed when it's done. No code or state persists after execution.

## Data handling

Your repository is cloned into the sandbox for the duration of a session and torn down when the session ends — no repository contents or working state persist afterward.

The one exception is [projects](https://docs.tembo.io/features/projects.md). When you use a project to speed up environment setup, its repositories and pre-installed dependencies are cached in reusable environments so future sessions start faster. Those cached copies persist until the project is rebuilt or removed.

Model providers handle prompt data according to their own retention policies — see the retention table in [Max](https://docs.tembo.io/features/max.md) for Tembo-hosted models. With [BYOK](https://docs.tembo.io/features/models.md), model requests run against your own provider account, so provider-side retention follows that account's terms.

## Sandbox sizes

Each session runs in a dedicated Linux VM, and no two sessions share the same VM.

Sandboxes size themselves automatically. Each sandbox starts with your project's minimum CPU and memory and grows as the work needs more, up to your project's maximum. By default, sandboxes start at 2 vCPU and 4 GiB and can grow to 16 vCPU and 32 GiB, with a 50 GB disk. You can change these limits in a project's resource settings and set its disk from 50 to 200 GB. Larger limits are available on request. Contact [support@tembo.io](mailto:support@tembo.io).

Named sizes describe common configurations, for example in [agent configuration](https://docs.tembo.io/features/agents.md) and self-hosted host sizing:

| Size | vCPU | Memory | Disk |
| - | - | - | - |
| Nano | 2 | 2 GiB | 50 GB |
| Micro | 2 | 4 GiB | 50 GB |
| Medium | 4 | 8 GiB | 50 GB |
| Large | 8 | 16 GiB | 100 GB |
| XL | 16 | 32 GiB | 200 GB |
| XXL | 16 | 64 GiB | 200 GB |
| Ultra | 32 | 128 GiB | 200 GB |

You pay for the vCPU, memory, and disk allocated while a sandbox runs. Rates and per-size prices are on the [pricing](https://docs.tembo.io/resources/pricing.md#cloud-vm-compute-rates) page.

VM sandboxes include full nested virtualization for Docker-in-Docker and provide a stronger isolation boundary.

If your org requires that untrusted code only runs with a VM boundary, we can enforce a VM-only posture. Contact [support@tembo.io](mailto:support@tembo.io).

## Pre-installed tools

All sandboxes come with:

| Category | Tools |
| - | - |
| **JavaScript** | Node.js 22, Bun, pnpm, Yarn |
| **Python** | Python 3.12, pipx, uv, ruff |
| **Ruby** | Ruby 3.3, Bundler, RuboCop |
| **.NET** | .NET SDK 10 |
| **Rust** | rustc, Cargo, Clippy, rustfmt |
| **Java** | JDK 21, Gradle, Maven |
| **Cloud** | Google Cloud SDK |
| **Containers** | Docker 28, Docker Compose 2.31 |
| **Other** | Git, curl, ShellCheck, httpie |

> [!NOTE]
>
> Go and Elixir are available through Nix dev shells. Add a `tembo.nix` to install language-specific tooling for your project.

## Add custom dependencies

Add a [`tembo.nix`](https://docs.tembo.io/features/sandbox/custom-dependencies) file to your repository when your project needs tools that are not pre-installed in the sandbox.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.