# Brimble Sandboxes

Official pricing: https://brimble.io/pricing  
Category: agent-sandbox · Isolation: gvisor

## Pricing regimes (raw)

- **On-demand** (resource)

## Features

Yes: snapshots, fork/clone, pause/resume, persistent disk, volumes, custom image (Docker or snapshot), start from your own snapshot, Docker inside, code interpreter, preinstalled agents, egress allowlist, Python, Node.js, live fork (no pause), EU data residency, spend limits, MCP server, snapshots on demand, gVisor or VM (no shared kernel), extra volumes

No: memory snapshots, idle auto-stop, ≥24 h sessions, your own Docker/OCI image, full VM (own kernel), nested virtualization, browser, desktop GUI, computer-use API, browser + desktop control, anti-bot stealth, CAPTCHA solving, residential IPs, SSH, public IPv4, HTTPS preview URLs, static egress IP, self-hosting, BYOC, open source, SSO, GPU, Windows, macOS, HTTP method/path egress rules, wake on request, live resize, memory fork, automatic snapshots, agent harness API, hosted agent API (their own agent), inbound access rules, firewall inside (nftables), secret proxy, secret proxy for any API, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/brimble.json → feature_evidence

## Caveats

- Public paid-plan sandbox quotas. PaaS bandwidth/object storage rates are not automatically sandbox snapshot/egress rates; no sandbox overage CPU/RAM unit price established.
- ENGINE_CARD cannot apply all independent free CPU/RAM/storage/request allowances exactly. Raw regimes/worked example retain them; any engine subtotal may overstate charges or miss eligibility. Do not subtract them twice.
- Not fully priceable in ENGINE_CARD: unknown USD resource rates or machine shape. Null is not zero; do not rank as a free provider.
- Features set to null were not verified. No sandbox was purchased or tested; feature/performance statements are documentation claims. Null maximums are unknown unless a cited note explicitly states unlimited.
- A complete monthly bill requires known snapshot/egress/plan limits; do not silently treat missing ancillary charges as free.
- Re-checked 2026-09-28: pricing page publishes plan fees, concurrency, max runtime and included CPU-/GB-hours only; no per-resource or overage rate, so the card stays unpriced.
- Brimble app/project compute is $1/vCPU-month and $1/GB-month (~$0.0014/h, region multipliers e.g. 1.45x) but the docs explicitly exclude sandboxes from that page; do NOT use these as sandbox overage rates.
- Snapshots expire: each has expires_at set by plan-dependent retention; an hourly reaper deletes expired snapshots. Snapshot storage bills while held ('Metered above plan-included snapshot allowance').
- Auto-destroy timers only 30m/1h/3h/6h/12h/18h plus a platform max-lifetime ceiling; spending limit with action 'pause' rejects every new sandbox create until raised or the cycle rolls.
- Sandbox size conflict: docs (paper.brimble.io/sandboxes/overview) cap sandbox memory at 2 GB and scratch disk at 1-5 GB, but the pricing page advertises up to 2 vCPU / 4 GB (Hacker) and 4 vCPU / 8 GB (Developer). A 4 vCPU / 8 GiB sandbox may not be creatable.
- Free plan: the pricing page says "Sandboxes available on paid plans", but the docs say free accounts get "a small sandbox quota" in free-marked regions only. Contradictory, so not modelled as a plan.
- One-time 14-day Developer trial for eligible personal accounts; a payment method is required before it starts (paper.brimble.io/billing/plans).

## How this provider charges


As of 2026-09-28. Prices are USD unless explicitly labelled otherwise. Source type: official published list/promo or unknown, never a fabricated quote.

Public paid-plan sandbox quotas. PaaS bandwidth/object storage rates are not automatically sandbox snapshot/egress rates; no sandbox overage CPU/RAM unit price established.

| Regime | When it applies | How billed / numbers | Source |
|---|---|---|---|
| Hacker | $3/month | 3concurrent,max2vCPU/4GB,2h;5CPU-h+10GB-h included. | https://brimble.io/pricing |
| Developer | $11/month | 15concurrent,max4vCPU/8GB,6h;20CPU-h+40GB-h included. | https://brimble.io/pricing |
| Enterprise | C50/8h requirement | Custom quote; published self-serve plans fail both limits. | https://brimble.io/pricing |

## Gotchas

- Public paid-plan sandbox quotas. PaaS bandwidth/object storage rates are not automatically sandbox snapshot/egress rates; no sandbox overage CPU/RAM unit price established.
- ENGINE_CARD cannot apply all independent free CPU/RAM/storage/request allowances exactly. Raw regimes/worked example retain them; any engine subtotal may overstate charges or miss eligibility. Do not subtract them twice.
- Not fully priceable in ENGINE_CARD: unknown USD resource rates or machine shape. Null is not zero; do not rank as a free provider.
- Features set to null were not verified. No sandbox was purchased or tested; feature/performance statements are documentation claims. Null maximums are unknown unless a cited note explicitly states unlimited.
- A complete monthly bill requires known snapshot/egress/plan limits; do not silently treat missing ancillary charges as free.

## Worked workload

4 vCPU / 8 GiB; 50 simultaneous instances × 8 h/day × 22 days = **8,800 instance-hours**, **35,200 vCPU-hours**, **70,400 GiB-hours**. At 30% observed CPU:10,560 active-vCPU-hours only where the meter actually uses utilization. Assume one start/instance/day:1,100starts. Retain50GiB snapshots for a month;100GiB outbound. Active disk capacity was not specified.

8,800h needs35,200CPU-h/70,400GB-h. Developer included20CPU-h/40GB-h does not cover this, andC15/max6h fail theworkload. Need Enterprise quote, overage tariff andsnapshot/network rates.

## Sources

- https://brimble.io/pricing
- https://pypi.org/project/brimble-sandbox/