Skip to content
GroundboxGroundmail
Groundbox
PricingDocs
Sign inStart free, no card

CI

CI runnersGitHub Actions runnersGitLab runnersGitLab CI, a third of the priceFlexHalf price, when there is roomCI tune-upOne pull request, faster CIInsightsTime, cost and size per jobTest analyticsFlaky and slow testsLogs and terminalsLive logs, a shell on a job

Builds

Build cacheTurborepo, Gradle, sccache, Bazel, NxDocker buildsA remote builderImage registryBeside your runnersStorageS3-compatible buckets

Sandboxes

SandboxesA VM for each agentTime machineSave points, rewind, forkTemplates and volumesBuild the disk oncePreviewsA URL for a portScheduled runsCron for a command

Agents

For agentsKeys, scopes, spend capsAgent computersA desktop for computer use
CI and sandboxes, one bill$20a month, $20 of usage included →
All prices →Benchmark →

Build

DocsQuickstarts and guidesAPI referenceREST endpointsCLIEvery command takes --json

Connect

MCP serverFor coding agentsSDKsTypeScript and PythonAPI explorerSend requests with your key
All docs →contact@groundbox.dev →

Compare

All comparisonsEvery sandbox and CI runner, side by sidevs GitHub-hostedMeasured on 10 open-source projectsvs E2BHalf the hourly price, memory includedMove from RunloopEvery call mapped, step by step

Guides

GitHub Actions runnersSizes, labels and what they costGitHub Actions cacheMake cached steps fastGitHub Actions costHow minutes are billed, with examplesGitLab runnersExecutors, setup, hosted vs your ownGitLab compute minutesCalculator: GitLab.com vs GroundboxAI agent sandboxesWhat to look for when you pick one

Proof and help

BenchmarkMethod, scripts and raw timingsCI cost checkerPoint it at your GitHub org, see what you'd payStatusUptime and start timesTalk to usBook a call with the team
All comparisons →Benchmark →
Products

CI

CI runnersGitHub Actions runnersGitLab runnersGitLab CI, a third of the priceFlexHalf price, when there is roomCI tune-upOne pull request, faster CIInsightsTime, cost and size per jobTest analyticsFlaky and slow testsLogs and terminalsLive logs, a shell on a job

Builds

Build cacheTurborepo, Gradle, sccache, Bazel, NxDocker buildsA remote builderImage registryBeside your runnersStorageS3-compatible buckets

Sandboxes

SandboxesA VM for each agentTime machineSave points, rewind, forkTemplates and volumesBuild the disk oncePreviewsA URL for a portScheduled runsCron for a command

Agents

For agentsKeys, scopes, spend capsAgent computersA desktop for computer use
Developers

Build

DocsQuickstarts and guidesAPI referenceREST endpointsCLIEvery command takes --json

Connect

MCP serverFor coding agentsSDKsTypeScript and PythonAPI explorerSend requests with your key
Resources

Compare

All comparisonsEvery sandbox and CI runner, side by sidevs GitHub-hostedMeasured on 10 open-source projectsvs E2BHalf the hourly price, memory includedMove from RunloopEvery call mapped, step by step

Guides

GitHub Actions runnersSizes, labels and what they costGitHub Actions cacheMake cached steps fastGitHub Actions costHow minutes are billed, with examplesGitLab runnersExecutors, setup, hosted vs your ownGitLab compute minutesCalculator: GitLab.com vs GroundboxAI agent sandboxesWhat to look for when you pick one

Proof and help

BenchmarkMethod, scripts and raw timingsCI cost checkerPoint it at your GitHub org, see what you'd payStatusUptime and start timesTalk to usBook a call with the team
PricingDocs
Start free, no cardSign in
GroundboxGitHub Actions runners and Linux sandboxes for AI agents. One key, one bill.System status

Product

CI runnersSandboxesBuilds and cacheAgent computersPricing

Developers

DocsAPI referenceAPI explorerCLIMCP serverBenchmark

Compare

vs GitHub-hostedvs Blacksmithvs E2Bvs DaytonaAll comparisons

Company

Talk to usSupportcontact@groundbox.devGroundmail ↗
© 2026 Groundbox
TermsPrivacyllms.txt
  1. Home
  2. Compare
  3. CodeSandbox SDK vs Vercel Sandbox

CodeSandbox SDK vs Vercel Sandbox: prices, limits and features.

Their prices for 2 vCPU and 4 GB overlap: $0.15 / hour and $0.085 to $0.34 / hour, since CPU is billed only while busy. Here is where they differ, from each one's own pages, plus a third option if neither fits.

The short answer

The CodeSandbox SDK runs microVM sandboxes. Together AI now offers it as Together Code Sandbox and calls the old SDK legacy. Vercel Sandbox runs untrusted code in Firecracker microVMs, billed on active CPU and provisioned memory.

Pick CodeSandbox SDK if you want

  • a lower price while the CPU is busy: $0.15 against $0.34 an hour
  • longest session: Runs until stopped, unless a ttl is set (Vercel Sandbox: 24 hours on Pro, 45 minutes on Hobby)

Pick Vercel Sandbox if you want

  • a lower price while the CPU is idle: $0.085 against $0.15 an hour
  • CPU billed only while busy; CodeSandbox SDK bills CPU the whole time a sandbox runs
  • fork and snapshots: Snapshots, which CodeSandbox SDK's pages do not state
  • largest size: 32 vCPU; 8 on Pro (CodeSandbox SDK: 16 cores)
  • security report: SOC 2 Type II, which CodeSandbox SDK's pages do not state

Or Groundbox if you want

  • a lower list price than both: $0.08 / hour
  • CI runners too: yes, on the same key and bill

Where CodeSandbox SDK or Vercel Sandbox is ahead of Groundbox: longest session, largest size, security report.

Side by side

CodeSandbox SDK, Vercel Sandbox and Groundbox
FeatureCodeSandbox SDKVercel SandboxGroundbox
Price, 2 vCPU · 4 GB$0.15 / hour$0.085 to $0.34 / hour$0.08 / hour
Pause keeps memoryNot publishedNo: the filesystem is saved, not memoryYes, memory and disk
CI runners tooNo: the pricing page lists Code Sandbox and Code Interpreter onlyNo: the pricing page lists sandboxes onlyYes, on the same key and bill
IsolationmicroVMFirecracker microVMFirecracker VM
Fork and snapshotsNot publishedSnapshotsFork a running sandbox; save points
Longest sessionRuns until stopped, unless a ttl is set24 hours on Pro, 45 minutes on Hobby720 hours, renewable
Self-hostNot publishedNot publishedNo
GPUsNot publishedNot publishedNot offered
Largest size16 cores32 vCPU; 8 on Pro16 vCPU
SDK languagesPython and TypeScriptJavaScript / TypeScript and PythonTypeScript and Python
Security reportNot publishedSOC 2 Type IINo SOC 2 report
Free to startLegacy SDK: a free Build planHobby, within monthly quotas$5 of usage, no card
PlansLegacy SDK: Build (free) and Scale plans; the new SDK is sold through Together's sales teamHobby free within monthly quotas; Pro usage comes out of the plan's $20 monthly credit, then rates applyFree: everything, with $5 of usage. $20 / month: $20 of usage included, then pay as you go
CPU$0.0446 per vCPU-hour (Together)$0.128 per active CPU-hour (iad1); time waiting on I/O is not billed$0.04 per vCPU-hour, a dedicated core
Memory$0.0149 per GiB-hour (Together)$0.0212 per GB-hour of provisioned memory (iad1)Included, up to 4 GB per vCPU
BillingLegacy SDK: VM credits at $0.01486 each, rounded up to the minuteMemory in 1-minute minimum increments; $0.60 per million sandbox creationsPer second, no minimum
SizesNew SDK: 0.1 to 16 cores, 1 to 8 GB per CPU1 to 32 vCPU, 2 GB per vCPU; 8 vCPU at most on Pro1 to 16 vCPU, up to 4 GB per vCPU
Sandboxes at onceLegacy SDK: 10 on Build, 250 on Scale10 on Hobby, 10,000 on Pro20 once a card is on file
Egress controlsNot publishedAllow all, deny all, or a domain and CIDR allowlistAn allowlist of hosts per sandbox

a rust mark means that side is ahead · each value links to its source · checked 2026-11-20

Each against Groundbox: Groundbox vs CodeSandbox SDK and Groundbox vs Vercel Sandbox. Every other comparison is on /compare.

Sources

CodeSandbox SDK

  • Together: Code Sandbox (legacy CodeSandbox SDK), checked 2026-11-19
  • Together: Code Sandbox, checked 2026-11-19
  • Together pricing, checked 2026-11-20

Vercel Sandbox

  • Vercel Sandbox pricing, checked 2026-11-20
  • Vercel Sandbox docs, checked 2026-11-19
  • Vercel Sandbox: security, checked 2026-11-19
  • Vercel Sandbox: persistent sandboxes, checked 2026-11-20
  • Vercel Sandbox: firewall, checked 2026-11-19

Try the third option free.

Start free, no cardGroundbox vs CodeSandbox SDK