# Pricing — caas.sh

**Usage-based pricing.** Sandboxes bill per resource. The MCP Gateway bills per request. Workflows bill per step. A typical coding agent runs about $0.17 an hour.

## Sandboxes

vCPU bills only while computing. Memory and disk bill while the sandbox runs.

| Meter | Price | When |
| --- | --- | --- |
| Active vCPU | $0.15 / hour | Only while computing |
| Memory | $0.018 / GiB-hour | While the sandbox is running |
| Disk | $0.001 / GB-hour | While the sandbox is running |
| Egress | $0.06 / GB | Outbound data from the sandbox |
| Snapshot storage | $0.025 / GB-month | For each snapshot you keep |
| Snapshot create / restore | Included | No charge per operation |

## MCP Gateway

| Meter | Price |
| --- | --- |
| Requests | $0.005 / 1,000 requests |

Includes the hosted endpoint, authentication, routing, persistence, and observability.

## Workflows

Each step runs in its own sandbox and bills at the sandbox rates above, plus the step.

| Meter | Price | When |
| --- | --- | --- |
| Steps | $1.00 / 1,000 steps | A four-step run adds $0.004 |
| Carried files | $0.10 / GiB-month | Files handed between steps, stored by content hash |
| Checkpoints and resumes | Included | Restart from the failed step at no charge |

## Container registry

Your images at registry.caas.sh. Pulls by your sandboxes count too.

| Meter | Price | When |
| --- | --- | --- |
| Storage | $0.025 / GB-month | For the images you keep |
| Pulls | $0.01 / 1,000 pulls | Each image manifest fetched |
| Lists | $0.005 / 1,000 lists | Each repository or tag listing |

## Example: a typical coding agent, for one hour

2 vCPU and 4 GiB of memory, busy 30% of the time, with a 10 GB disk. You pay for the CPU it uses, not the CPU it holds.

| Line | Calculation | Cost |
| --- | --- | --- |
| Active CPU | 2 × 0.30 × $0.15 | $0.09 |
| Memory | 4 × $0.018 | $0.072 |
| Disk | 10 × $0.001 | $0.01 |
| **Total** | | **~$0.17 / hour** |

Egress billed separately at $0.06 / GB.

## Workflow example: one run of fix-failing-tests

Four steps, each in a fresh 2 vCPU, 4 GiB sandbox with a 10 GB disk: 12 minutes of sandbox time in all, busy 30% of the time. About 200 MB of files move between steps and are kept for a week.

| Line | Calculation | Cost |
| --- | --- | --- |
| Active CPU | 2 × 0.30 × 0.2 h × $0.15 | $0.018 |
| Memory | 4 × 0.2 h × $0.018 | $0.014 |
| Disk | 10 × 0.2 h × $0.001 | $0.002 |
| Steps | 4 × $0.001 | $0.004 |
| Carried files | 0.2 GiB × 7 days at $0.10 | $0.005 |
| **Total** | | **~$0.04 / run** |

Checkpoints and resumes are included. A run that resumes pays only for the steps it reruns.

## Included: operate the workload from one place

- **MCP endpoint.** Connect clients to a hosted server through an authenticated URL.
- **Outbound policy.** Set the hosts your sandbox may reach.
- **Workspace recovery.** Take snapshots and keep a durable backup of workspace files.

## Run an agent or an MCP server

Watch the meters from your first workspace. Get started in the [console](https://console.caas.sh/).

[Features](https://caas.sh/features.html) · [Agents](https://caas.sh/agents.html)