Groundbox vs CodeSandbox SDK for agent sandboxes.
The CodeSandbox SDK is now Together Code Sandbox, and Together calls the old SDK legacy. Pick it for memory snapshots and hibernation on Together's platform, or Docker Compose environments. Pick Groundbox for self-serve sign-up, per-second billing, memory included in the CPU price, and CI runners on the same key.
sources: groundbox.dev/pricing · together.ai · checked 2026-11-20
Side by side
| Feature | Groundbox | CodeSandbox SDK |
|---|---|---|
| Price, 2 vCPU · 4 GB | $0.08 / hour | $0.15 / hour |
| Pause keeps memory | Yes, memory and disk | Not published |
| CI runners too | Yes, on the same key and bill | No: the pricing page lists Code Sandbox and Code Interpreter only |
| Isolation | Firecracker VM | microVM |
| Fork and snapshots | Fork a running sandbox; save points | Not published |
| Longest session | 720 hours, renewable | Runs until stopped, unless a ttl is set |
| Self-host | No | Not published |
| GPUs | Not offered | Not published |
| Largest size | 16 vCPU | 16 cores |
| SDK languages | TypeScript and Python | Python and TypeScript |
| Security report | No SOC 2 report | Not published |
| Free to start | $5 of usage, no card | Legacy SDK: a free Build plan |
The CodeSandbox SDK runs microVM sandboxes. Together AI now offers it as Together Code Sandbox and calls the old SDK legacy. A rust mark means that side is ahead. Where they are ahead, we say so. Every value of theirs links to the page it is from; “Not published” means their pages do not say. More comparisons: all comparisons.
Who each is for
Pick CodeSandbox SDK for
- memory snapshots and hibernation
- environments from Docker, Docker Compose or Dev Containers
- sandboxes on the same platform as Together's models
Pick Groundbox for
- self-serve sign-up; the new Together SDK is sold through sales
- per-second billing; the legacy SDK rounds up to the minute
- pause, fork and save points of a running sandbox, and an egress allowlist
- a spend cap and scopes on every API key
- GitHub Actions runners on the same key and bill
Every detail
| Feature | Groundbox | CodeSandbox SDK |
|---|---|---|
| Plans | Free: everything, with $5 of usage. $20 / month: $20 of usage included, then pay as you go | Legacy SDK: Build (free) and Scale plans; the new SDK is sold through Together's sales team |
| CPU | $0.04 per vCPU-hour, a dedicated core | $0.0446 per vCPU-hour (Together) |
| Memory | Included, up to 4 GB per vCPU | $0.0149 per GiB-hour (Together) |
| Billing | Per second, no minimum | Legacy SDK: VM credits at $0.01486 each, rounded up to the minute |
| Sizes | 1 to 16 vCPU, up to 4 GB per vCPU | New SDK: 0.1 to 16 cores, 1 to 8 GB per CPU |
| Default size | 2 vCPU, 4 GB RAM, 20 GB disk | New SDK: 1 vCPU, 2 GiB |
| Longest session | 720 hours, renewable; 60 minutes by default | Runs until stopped, unless you set a ttl |
| Sandboxes at once | 20 once a card is on file | Legacy SDK: 10 on Build, 250 on Scale |
| Isolation | A Firecracker VM, a new one per job or sandbox | microVM |
| Idle | Auto-stop after 60 minutes by default | Legacy SDK: hibernates after a timeout |
| SDKs | TypeScript and Python, plus a REST API, CLI and MCP server | New SDK: Python and TypeScript, plus a CLI |
A month at list price
One sandbox with 2 vCPU and 4 GiB of memory, running 100 hours in a month:
| Groundbox | $8.00 ($0.04 per vCPU-hour, memory included). On the $20 plan it fits in the $20 of usage included. |
|---|---|
| CodeSandbox SDK | $14.88 |
At Together's per-vCPU and per-GiB rates. Plan fees are not counted. All our prices are on the pricing page.
Speed
We have not measured this service's sandboxes, and we publish no start or fork times for ours, so this page makes no speed claim. The speed figures we do publish are for CI runners, on the benchmark page. Method, scripts and every project's times: the benchmark page.
Switch in four steps
- Create an API key in the dashboard. An agent can also sign itself up with groundbox signup and send its person a claim link.
- Install an SDK: npm i @groundbox/sdk or pip install groundbox.
- Where your code creates a sandbox and runs a command in it, call create_sandbox and run_command. Files, fork, pause and stop have one method each, with the same names as the MCP tools.
- Or give the agent the MCP server instead of SDK code: it has the same tools.
Details in the docs: First sandbox, the SDKs and the MCP server.
import { Groundbox } from "@groundbox/sdk";
const groundbox = new Groundbox(); // reads GROUNDBOX_API_KEY
const sandbox = await groundbox.create_sandbox({ cpus: 2 });
const result = await groundbox.run_command(sandbox.id, "uname -a");Questions
| Is Groundbox cheaper than the CodeSandbox SDK? | At list price, one 2 vCPU, 4 GiB sandbox for 100 hours costs $8.00 on Groundbox and $14.88 on Together, before plan fees and credits. |
| How do I move an agent from the CodeSandbox SDK to Groundbox? | Create an API key, install the TypeScript or Python SDK, and call create_sandbox and run_command where your code makes a sandbox and runs a command. The MCP server has the same tools. |
| How are sandboxes isolated on Groundbox and on the CodeSandbox SDK? | Each Groundbox sandbox is its own Firecracker VM on dedicated cores. CodeSandbox sandboxes run in microVMs. |
| Can a Groundbox sandbox pause and fork? | Yes. Pause keeps memory and disk and costs $0.05 per GB-month. Fork copies a running sandbox's files and processes. |
| How long can a Groundbox sandbox run? | It stops after 60 minutes by default. The longest timeout is 720 hours, and it can be renewed. A Together sandbox runs until it is stopped, unless you set a ttl. |
| Does Groundbox also run CI? | Yes. GitHub Actions runners from $0.003 a minute are on the same API key and bill as sandboxes. |
Sources
CodeSandbox SDK's facts come from its own pages, read on the day shown. Prices change; their pages are the final word.
- Together: Code Sandbox (legacy CodeSandbox SDK), checked 2026-11-19
- Together: Code Sandbox, checked 2026-11-19
- Together pricing, checked 2026-11-20