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

# Pricing

> Four plans, each with vCPU-hours and egress included every month, and one rate card for the rest.

> [!NOTE]
>
> These plans and rates apply from the hour after they went live; usage before that was billed under the previous plans. Paid plans are paid on the secure Stripe checkout page; see [Plans and codes](/docs/plans-and-codes.md#choosing-a-plan).

## Plans

| | Free | Starter | Pro | Scale |
| - | - | - | - | - |
| Price a month | **\$0** | **\$19** | **\$99** | **\$399** |
| vCPU-hours included a month (each with 2 GiB of memory) | 100 | 330 | 1,800 | 7,500 |
| Egress included a month | 5 GB | 25 GB | 100 GB | 250 GB |
| When the included usage is used up | New sandboxes stop, running ones are paused | Keeps running, billed at the rates below | Keeps running, billed at the rates below | Keeps running, billed at the rates below |
| Sandboxes at once | 5 | 20 | 100 | 500 |
| Largest size | Medium | Medium | Large | XL |

| Meter | Price |
| - | - |
| Allocated vCPU, per vCPU-hour | **\$0.04** |
| Allocated memory, per GiB-hour | **\$0.01** |
| Storage (paused sandboxes and snapshots), per GiB-hour | \$0.0000685 |
| Egress, per GB | \$0.12 |
| A unit of 1 vCPU and 2 GiB, per hour | **\$0.06** |

Every plan uses the same rates. The other limits of each plan are on [Regions and limits](/docs/concepts/limits.md).

## How usage is billed

**Allocated, not active.** A sandbox is billed for the vCPU and memory it is given, for every second it runs, whatever it does with them: billed per second, with a 1-minute minimum. A sandbox that runs less than a minute is billed one minute; after the first minute every second is billed, so one that runs 90 seconds is billed 90 seconds. A Medium sandbox (2 vCPU, 4 GiB) costs 2 × $0.04 + 4 × $0.01 = **\$0.12 an hour** whether it is busy or waiting for an LLM. See [Sandbox sizes](/docs/concepts/sizes.md) for what each size is given.

**Included usage is counted in vCPU-hours.** Each included vCPU-hour also includes 2 GiB-hours of memory, so one included hour is one hour of a 1 vCPU, 2 GiB sandbox: a Small sandbox for an hour uses 1, a Medium 2, a Large 4 and an XL 8. Included usage and egress reset on the first of each calendar month (UTC), and the first month gets the full amount however late in it you start. What you do not use does not carry over.

**Warnings.** The team's owners and admins get an email at **80%** and **100%** of the month's included vCPU-hours and of its included egress: on Free, saying it will stop; on a paid plan, saying usage over it is billed at the rates above.

**When it is used up.**

* **Free** stops: new sandboxes are refused, and running ones are paused (or deleted, when your paused sandboxes are already at the limit) until the month ends. Upgrade to carry on straight away.
* **Paid plans** keep running. What you use beyond the included vCPU-hours, memory and egress is billed at the rates above and added to your next invoice.

**Credit you already have keeps paying.** A credit balance from before these plans pays for usage over the included amount first, on any plan; only what it does not cover is billed (paid plans), and Free stops only once it is spent. New credit codes and sign-up credit are no longer given.

**Paused costs only storage.** A paused sandbox pays no vCPU or memory charge. Its snapshot is billed as storage until you resume or delete it, at $0.0000685 per GiB-hour (about $0.05 per GiB a month). Storage is not part of the included usage. Free is never billed: its storage costs nothing.

**Egress** is data your sandboxes send to the internet, per GB (10<sup>9</sup> bytes). Paid plans have public internet egress on by default. On Free it is off for now: its 5 GB a month needs a cap that acts in real time, which is coming soon, and the stop at the included egress applies once it is on.

Usage is counted from the hourly rollup, so what you see, and the moment Free stops, can trail what ran by up to about an hour.

The credential vault is included at no charge on every plan.

## Examples

| Pattern | Per hour | A month of included usage lasts |
| - | - | - |
| One Small sandbox (1 vCPU, 2 GiB) | \$0.06 | Free: 100 hours. Starter: 330 hours |
| One Medium sandbox (2 vCPU, 4 GiB) | \$0.12 | Free: 50 hours. Pro: 900 hours |
| One Large sandbox (4 vCPU, 8 GiB) | \$0.24 | Pro: 450 hours |
| A paused Medium sandbox with a 4 GiB snapshot | about \$0.0003 | Storage, billed on paid plans |

On Pro, a team that runs 2,000 vCPU-hours in a month (with 4,000 GiB-hours of memory) and sends 80 GB pays the $99 fee plus 200 × $0.04 + 400 × $0.01 = **$12\*\* of overage.

See [Usage and billing](/docs/usage-and-billing.md) for where to see what you used against what is included: the dashboard, `anona-compute usage`, or `GET /v1/usage`.


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