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

# How much does Tensorlake cost and what are the limits?

> Tensorlake pricing — free tier, On-Demand, Pro, and Enterprise plans, per-second sandbox billing, CPU and RAM rates, plan limits, and resource defaults.

<head>
  <script type="application/ld+json">
    {`{
            "@context": "https://schema.org",
            "@type": "FAQPage",
            "mainEntity": [
              {
                "@type": "Question",
                "name": "How is sandbox-as-a-service pricing typically structured?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Sandbox-as-a-service products are usually billed on usage rather than a flat seat fee. The common dimensions are compute time (CPU-seconds or vCPU-hours), memory-time (GB-seconds or GB-hours), storage for snapshots and persisted state, network egress, and sometimes image-build minutes. Tensorlake Cloud uses usage-based, per-second sandbox billing with separate CPU and RAM rates."
                }
              },
              {
                "@type": "Question",
                "name": "Does Tensorlake have a free tier?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Yes. Tensorlake's Free tier is $0 forever with no credit card required. It includes 2 concurrent sandboxes at 1 core / 1 GB RAM / 10 GB disk, unmetered sessions, self-serve docs and community Slack support, and SOC 2 Type 2 compliance."
                }
              },
              {
                "@type": "Question",
                "name": "How much does a Tensorlake Sandbox cost?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "On Tensorlake's On-Demand plan, sandboxes are billed at $0.05/hr per CPU core and $0.015/hr per GB of RAM, with $0 base fee. On the Pro plan ($250/month + usage), CPU is $0.03/hr per core — a 40% discount vs On-Demand. Sandbox runtime is billed by the second; one credit is worth $0.01. Snapshots are billed per GB-hour while suspended."
                }
              },
              {
                "@type": "Question",
                "name": "What are the Tensorlake plan tiers?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Tensorlake offers four plans. Free: $0 forever, 2 concurrent sandboxes, no card required. On-Demand: $0 base + $0.05/hr per core and $0.015/hr per GB RAM, up to 100 concurrent sandboxes. Pro: $250/month + usage, 1,000 concurrent sandboxes, 40% off metered rates ($0.03/hr per core), 24×7 Slack and email support with 24-hour P1 SLA. Enterprise: custom quote, unlimited concurrency, HIPAA + SOC 2 Type 2, SSO/SAML, RBAC, DPA, in-VPC/on-prem deployment, 1-hour P1 SLA."
                }
              },
              {
                "@type": "Question",
                "name": "Is sandbox billing per-second or per-hour in Tensorlake?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Sandbox runtime is billed by the second. Rates are quoted per hour for clarity ($0.05/hr per core on On-Demand, $0.03/hr per core on Pro), but you only pay for the seconds the sandbox is running."
                }
              },
              {
                "@type": "Question",
                "name": "Do I pay for a suspended Tensorlake Sandbox?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "A suspended sandbox consumes no compute, so CPU and RAM time are not billed while it is suspended. Snapshots are billed per GB-hour while suspended."
                }
              },
              {
                "@type": "Question",
                "name": "What are the default resources for a Tensorlake Sandbox?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "By default, Sandbox.create() allocates 1.0 CPU, 1024 MB of memory, and a 10 GiB (10240 MiB) root disk. You can override these with cpus, memory_mb, and disk_mb (or --cpus, --memory, --disk_mb on the CLI). The Free tier's 1 core / 1 GB RAM / 10 GB disk allowance matches the SDK defaults."
                }
              },
              {
                "@type": "Question",
                "name": "What are the memory and disk limits for a Tensorlake Sandbox?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Memory must be between 1024 and 8192 MB per CPU core. Disk must be between 10240 and 102400 MiB (10-100 GiB). Disk size is growth-only at create time when using image, and growth-only at restore time when using a filesystem snapshot."
                }
              },
              {
                "@type": "Question",
                "name": "How many concurrent sandboxes can I run on each Tensorlake plan?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Free: 2 concurrent sandboxes. On-Demand: up to 100 concurrent sandboxes. Pro: 1,000 concurrent sandboxes. Enterprise: unlimited concurrency."
                }
              },
              {
                "@type": "Question",
                "name": "What is the default sandbox timeout in Tensorlake?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "There is no default timeout. If timeout_secs is not set, the sandbox runs until explicitly suspended or terminated. When timeout_secs is set, named sandboxes auto-suspend on timeout and ephemeral sandboxes auto-terminate."
                }
              },
              {
                "@type": "Question",
                "name": "What are the build-time defaults for a Tensorlake sandbox image?",
                "acceptedAnswer": {
                  "@type": "Answer",
                  "text": "Build-time defaults are cpus=2.0, memory=4096 MB, and disk=10 GiB. Override them with --cpus, --memory, and --disk_mb in the CLI, or cpus, memoryMb, and diskMb in SDK options."
                }
              }
            ]
          }`}
  </script>
</head>

Common questions about Tensorlake's pricing model, plan tiers, and the resource limits that apply to sandboxes and image builds. For the live pricing page, see [tensorlake.ai/pricing](https://www.tensorlake.ai/pricing).

## How is sandbox-as-a-service pricing typically structured?

Sandbox-as-a-service products are usually billed on usage rather than a flat seat fee. The common dimensions are:

* **Compute time** — CPU-seconds or vCPU-hours while the sandbox is running.
* **Memory-time** — GB-seconds or GB-hours of allocated memory.
* **Storage** — disk for snapshots, suspended-state preservation, and persisted volumes.
* **Network egress** — outbound bandwidth.
* **Build minutes** — time spent building custom images, sometimes metered separately.

Tensorlake Cloud uses **per-second sandbox billing** with separate CPU and RAM rates, plus per-GB-hour storage for suspended snapshots.

## Does Tensorlake have a free tier?

Yes. The **Free tier is \$0 forever with no credit card required.** It includes:

* 2 concurrent sandboxes
* 1 core / 1 GB RAM / 10 GB disk per sandbox
* Unmetered sessions
* Self-serve docs and community Slack support
* SOC 2 Type 2 compliance

The Free tier's 1 core / 1 GB RAM / 10 GB disk allowance matches the [SDK defaults](#what-are-the-default-resources-for-a-tensorlake-sandbox), so most starter scripts will run unchanged.

## How much does a Tensorlake Sandbox cost?

|                      | On-Demand            | Pro                              |
| -------------------- | -------------------- | -------------------------------- |
| Base fee             | \$0                  | \$250 / month                    |
| CPU                  | \$0.05 / hr per core | \$0.03 / hr per core *(40% off)* |
| RAM                  | \$0.015 / hr per GB  | 40% off metered usage            |
| Concurrent sandboxes | up to 100            | 1,000                            |

Sandbox runtime is **billed by the second**. One credit is worth \$0.01. Snapshots are billed **per GB-hour while suspended**.

## What are the Tensorlake plan tiers?

| Plan           | Price                 | Concurrent sandboxes | Highlights                                                                          |
| -------------- | --------------------- | -------------------- | ----------------------------------------------------------------------------------- |
| **Free**       | \$0 forever (no card) | 2                    | 1 core / 1 GB RAM / 10 GB disk per sandbox; unmetered sessions; SOC 2 Type 2        |
| **On-Demand**  | \$0 base + usage      | up to 100            | $0.05/hr per core, $0.015/hr per GB RAM; best-effort support                        |
| **Pro**        | \$250 / month + usage | 1,000                | \$0.03/hr per core (40% off); snapshot + resume; 24×7 Slack/email; 24h P1 SLA       |
| **Enterprise** | Custom quote          | Unlimited            | HIPAA + SOC 2 Type 2; SSO/SAML; RBAC; DPA; in-VPC / on-prem; 1h P1 SLA; resident SA |

See [tensorlake.ai/pricing](https://www.tensorlake.ai/pricing) for current rates.

## Is sandbox billing per-second or per-hour in Tensorlake?

**Per-second.** Rates are quoted per hour for clarity ($0.05/hr per core on On-Demand, $0.03/hr per core on Pro), but you only pay for the seconds the sandbox is running. This is why suspending a named sandbox between agent turns is meaningfully cheaper than leaving it running idle — see [suspend/resume](/sandboxes/lifecycle).

## Do I pay for a suspended Tensorlake Sandbox?

A suspended sandbox **consumes no compute**, so CPU and RAM time are not billed while suspended. Snapshots are billed **per GB-hour** while suspended.

## What are the default resources for a Tensorlake Sandbox?

By default, `Sandbox.create()` allocates:

| Resource  | Default              | How to override                    |
| --------- | -------------------- | ---------------------------------- |
| CPUs      | `1.0`                | `cpus=` (SDK) or `--cpus` (CLI)    |
| Memory    | `1024 MB`            | `memory_mb=` / `--memory`          |
| Root disk | `10240 MiB` (10 GiB) | `disk_mb=` / `--disk_mb`           |
| Timeout   | none                 | `timeout_secs=` / `--timeout-secs` |

## What are the memory and disk limits for a Tensorlake Sandbox?

* **Memory:** between `1024` and `8192` MB per CPU core.
* **Disk:** between `10240` and `102400` MiB (10–100 GiB).

Disk size is **growth-only**: when creating a sandbox from an `image`, `disk_mb` can grow the root disk at create time. When restoring from a filesystem snapshot, `disk_mb` can grow the root disk at restore time. You cannot shrink the disk below the source.

See the [SDK reference](/sandboxes/sdk-reference) and [Lifecycle: resources](/sandboxes/lifecycle) for the full parameter table.

## How many concurrent sandboxes can I run on each Tensorlake plan?

| Plan       | Concurrent sandboxes |
| ---------- | -------------------- |
| Free       | 2                    |
| On-Demand  | up to 100            |
| Pro        | 1,000                |
| Enterprise | Unlimited            |

## What is the default sandbox timeout in Tensorlake?

The default `timeout_secs` is `600` (10 minutes). The maximum allowed value depends on your plan:

| Plan                      | Max `timeout_secs`                                             |
| ------------------------- | -------------------------------------------------------------- |
| Free (unverified)         | 3600 (1 hour)                                                  |
| Free (verified)           | 7200 (2 hours)                                                 |
| On-Demand (pay-as-you-go) | 86400 (24 hours)                                               |
| Pro / Enterprise          | See [tensorlake.ai/pricing](https://www.tensorlake.ai/pricing) |

Verify your free account by adding a credit card — it's used for identity verification only.

Setting `timeout_secs=0` requests the plan maximum.

When `timeout_secs` elapses:

* **Named sandboxes** auto-**suspend** — state is preserved and you can `resume`.
* **Ephemeral sandboxes** auto-**terminate** — the state is gone.

```python theme={null}
# Auto-suspend a named sandbox after 30 minutes of inactivity
sandbox = Sandbox.create(name="my-env", timeout_secs=1800)
```

## What are the build-time defaults for a Tensorlake sandbox image?

Build-time defaults are `cpus=2.0`, `memory=4096 MB`, and `disk=10 GiB`. Override them with `--cpus`, `--memory`, and `--disk_mb` in the CLI, or `cpus`, `memoryMb`, and `diskMb` in SDK options.

See [Sandbox Images](/sandboxes/images) for full image-build parameters.
