# Groundbox > Groundbox is a hosted service with GitHub Actions runners and Linux sandbox VMs for coding agents, on one API key and one bill. ## Products - CI runners for GitHub Actions: change `runs-on` to a Groundbox label. `groundbox-2vcpu` (2 vCPU, 8 GB) $0.003/min; `groundbox-4vcpu` (4 vCPU, 16 GB) $0.006/min; `groundbox-8vcpu` (8 vCPU, 32 GB) $0.011/min; `groundbox-16vcpu` (16 vCPU, 64 GB) $0.021/min. Billed by the second. Each job runs in a new Firecracker VM. actions/cache, package mirrors (npm, PyPI, crates, apt, Docker Hub) and the Docker layer cache are on the same machine as the job. - Sandboxes: a Linux VM per agent at $0.04 per vCPU-hour on dedicated cores, memory up to 4 GB per vCPU included. Exec, files, fork, pause and resume (memory and disk kept), stop and start (disk kept, a cold boot on start; paused or stopped: $0.05 per GB-month), scheduled runs, egress allowlist. - Agent computers: a sandbox with a Linux desktop and Chrome for computer-use agents. Screenshot, click, type and the other actions computer-use models emit, through the API, the SDKs and MCP; a live view to embed in your own app; a handoff to a person for sign-ins and 2FA; fork a signed-in desktop. - CI tools: CI tune-up (an agent prepares one pull request that makes a repository's CI faster; free on every plan), insights (time, failures, cost, CPU and memory per job, with right-sizing tips), live job logs, a terminal on a running job (`groundbox ci ssh`), and test analytics with flaky-test detection from JUnit reports. - Builds: a remote build cache for Turborepo, Gradle, sccache, Bazel and Nx, set up on Groundbox runners already and reachable from outside at https://api.groundbox.dev/build-cache with an API key (included). Remote Docker builds on a 8 vCPU BuildKit builder with a layer cache per project, $0.011/min. A private container image registry (OCI) beside the runners, $0.05 per GB-month, pushes and pulls free. S3-compatible storage, $0.015 per GB-month. - Sandbox tools: scheduled runs (a cron expression, a sandbox spec and a command). Time machine: save points of memory, disk and processes, rewind, and fork one moment into many copies. Snapshots: keep a save point after its sandbox is deleted and start new sandboxes from it by id. A sandbox can start straight from a public Docker image (`image`), or from a template with warm start. Volumes cost $0.08 per GB-month. Previews: an HTTPS address for a port in a sandbox. - For agents: one API key with scopes and a monthly spend cap, a REST API, a CLI (every command takes --json), an MCP server, and TypeScript and Python SDKs. ## Set up for a person When a person asks you to set up Groundbox: `npm i -g @groundbox/cli`, then `groundbox login` (it opens a browser page where they sign up or sign in and approve this machine), then `groundbox run -- "uname -a"` to show a sandbox works. In Claude Code, also add the MCP server: `claude mcp add --transport http groundbox https://mcp.groundbox.dev/mcp` (OAuth sign-in, no key). For faster CI in a GitHub repo: `groundbox tuneup ` opens one pull request with the changes. The full prompt people paste: https://groundbox.dev/#agent ## Start with no human An agent can sign itself up and test sandboxes with no person and no card: `groundbox signup --name my-agent` (saves the key), the `signup` tool at the MCP endpoint that needs no key (https://mcp.groundbox.dev/mcp/signup; then connect to https://mcp.groundbox.dev/mcp with the key as a Bearer token), or `curl -s -X POST https://api.groundbox.dev/v1/signup -H 'content-type: application/json' -d '{"agent_name":"my-agent"}'`. - Free: $5.00 of usage, on the free plan with every feature. Until a card is on file: 2 sandboxes at a time (forks count), up to 2 vCPU and 4 GB, 60 minutes each from its start, paused or not, and up to 10 team secrets. - Everything else works, kept snapshots, volumes, templates, storage, schedules, previews and remote builds included. Only CI (a person installs the GitHub App) and adding a card need a person. - The answer has `api_key`, `claim_url` and `message_for_human`. When you want more, or a call answers `trial_limit` or `trial_credit_exhausted` (both carry the same two fields), send your human `message_for_human`: they open `claim_url`, take over the account and add a card. Your key and sandboxes stay. - Details: https://groundbox.dev/docs/api.md (Agent sign-up and the free credit). ## API spec - [OpenAPI spec](https://groundbox.dev/openapi.json): every public endpoint, generated from the API's own schemas (also as [YAML](https://groundbox.dev/openapi.yaml), and at https://api.groundbox.dev/openapi.json). - [API explorer](https://groundbox.dev/docs/api/explorer): send real requests with your own key, in the browser. ## Pricing - Free: everything, with $5 of usage and 3,000 CI minutes a month. $20 a month: $20 of usage included, then pay as you go. - Free plan: every feature and every runner size, no card. CI past the free minutes uses the free credit. Until a card is on file, sandboxes are held to 2 sandboxes at a time, 2 vCPU, 4 GB, 1 hour each. - $20 plan: $20 of usage included each month, then pay as you go at the same rates. Annual: 2 months free. - Auto size: runs-on: groundbox picks 2, 4, 6, 8, 10, 12, 14 and 16 vCPU for each job before it starts, from what its earlier runs used; billed at the size it ran at. runs-on: groundbox-auto-tests gives a job runners of its own, so it gets exactly its own size. `groundbox migrate ` moves each job to its own auto label (`--fixed` for fixed sizes); `groundbox migrate --to-auto` moves jobs on fixed Groundbox labels; `groundbox ci auto` shows each job's size and why, and `--max` sets the team's largest auto size (8 vCPU unless set). - Flex: the same runners at half price ($0.0015 / $0.003 / $0.0055 / $0.0105/min), started when a machine has spare room. - GitHub-hosted list price for comparison: $0.006 / $0.012 / $0.022 / $0.042/min at 2 / 4 / 8 / 16 vCPU. ## Measured - On 10 open-source projects, groundbox-2vcpu against GitHub's ubuntu-latest (2 vCPU each): median speed-up 2.4× with a warm cache, 2.1× with a cold cache. Method and raw timings: https://github.com/Ground-box/benchmarks ## Docs - [Docs](https://groundbox.dev/docs.md): Quickstarts for CI runners and sandboxes, and the reference for the REST API, the CLI, the MCP server and the SDKs. - [CI in one line](https://groundbox.dev/docs/ci.md): Move a GitHub Actions workflow to Groundbox: runner labels and sizes, caches, groundbox migrate and groundbox ci wait. - [First sandbox](https://groundbox.dev/docs/sandboxes.md): Start a sandbox, run a command and move files, then fork, pause and resume, schedule runs and set an egress allowlist. - [Agent computers](https://groundbox.dev/docs/agent-computers.md): Desktop sandboxes for computer-use agents: the computer-use API, a live view to embed, human handoff for sign-ins and 2FA, forking a signed-in desktop, and an agent loop with Claude. - [REST API](https://groundbox.dev/docs/api.md): Every Groundbox API endpoint with its scope, and how keys, scopes and spend caps work. - [API explorer](https://groundbox.dev/docs/api/explorer.md): Every Groundbox API endpoint from the OpenAPI spec. Fill in a request and send it with your own API key. - [OpenAPI reference](https://groundbox.dev/docs/api/reference.md): Every Groundbox API endpoint from the OpenAPI spec: its scope, parameters, body and answers. - [CLI](https://groundbox.dev/docs/cli.md): The groundbox command: sign in, sandboxes, ci wait and migrate. Every command takes --json. - [MCP server](https://groundbox.dev/docs/mcp.md): The groundbox MCP server for coding agents: how to add it and the tools it exposes. - [SDKs](https://groundbox.dev/docs/sdks.md): The TypeScript and Python SDKs for the Groundbox API, with one method per MCP tool. - [Templates and volumes](https://groundbox.dev/docs/templates.md): Build a sandbox's disk once from an image, a Dockerfile or packages, start sandboxes from it in well under a second, and keep data on volumes. - [CI tune-up](https://groundbox.dev/docs/tuneups.md): An agent reads a repo's workflows in a Groundbox sandbox and proposes one pull request that makes CI faster. Free on every plan. - [Build caches](https://groundbox.dev/docs/build-caches.md): A remote build cache for Turborepo, Gradle, sccache, Bazel and Nx, shared by CI jobs, laptops and agents. Set up on Groundbox runners already. - [Split tests by time](https://groundbox.dev/docs/test-splitting.md): groundbox tests split balances test files over CI shards by their recorded time, so every shard finishes together. Falls back to an even split. - [Image registry](https://groundbox.dev/docs/registry.md): registry.groundbox.dev: a private OCI container registry beside your CI runners. Log in with your API key, push and pull, retention, $0.05 per GB-month. - [Docker builds](https://groundbox.dev/docs/builds.md): groundbox build and the setup-build action: Docker builds on a remote BuildKit with a layer cache per project. docker/build-push-action works unchanged. - [Storage](https://groundbox.dev/docs/storage.md): S3-compatible buckets for agents and CI on Groundbox's own disks: access keys, the aws CLI, boto3, the AWS SDKs, rclone, limits and prices. - [Previews](https://groundbox.dev/docs/previews.md): An HTTPS URL for a port in a running sandbox: private with a share link, or public for webhooks and OAuth callbacks. Limits and what we change. - [Move from Runloop](https://groundbox.dev/docs/migrate/runloop.md): Move from Runloop devboxes to Groundbox sandboxes: every Runloop SDK call mapped to Groundbox in TypeScript and Python, what has no equivalent, and pricing. - [Omnara](https://groundbox.dev/docs/omnara.md): Use Groundbox as an Omnara machine provider: the API key, templates, sleep with memory kept, sizes, price and limits. ## Guides - [GitHub Actions runners](https://groundbox.dev/github-actions-runners.md): What a GitHub Actions runner is, the four kinds you can use, what each costs per minute, and measured job times on GitHub-hosted and Groundbox runners. - [GitHub Actions cache](https://groundbox.dev/github-actions-cache.md): How actions/cache keys, restore-keys and branch scope work, GitHub's 10 GB and 7-day limits, and how a cache on the runner's own machine changes restore time. - [GitHub Actions cost](https://groundbox.dev/github-actions-cost.md): How GitHub bills Actions minutes: per-minute prices by runner, included usage per plan, rounding to the minute, and worked monthly examples. - [AI agent sandbox](https://groundbox.dev/ai-agent-sandbox.md): What a sandbox for AI agents needs: isolation, commands and files, fork and pause, network limits and spend caps. Ours: a Linux VM at $0.04 per vCPU-hour. ## Compare - [Compare](https://groundbox.dev/compare.md): Groundbox next to GitHub-hosted runners, Blacksmith, Depot, WarpBuild and other CI runners, and E2B, Daytona, Modal and other sandboxes, from each one's own pages. - [GitHub-hosted runners](https://groundbox.dev/compare/github-hosted-runners.md): Median job times for ten open-source projects on GitHub's ubuntu-latest and groundbox-2vcpu, cold and warm cache, with per-minute prices for both. - [Blacksmith](https://groundbox.dev/compare/blacksmith.md): Groundbox and Blacksmith for GitHub Actions side by side: per-minute prices, free minutes, sizes, caches and isolation, from each one's public pages. - [Depot](https://groundbox.dev/compare/depot.md): Groundbox and Depot GitHub Actions runners side by side: plans, per-minute prices, sizes, billing and caches, from each one's public pages. - [Namespace](https://groundbox.dev/compare/namespace.md): Groundbox and Namespace GitHub Actions runners side by side: plans, unit prices, billing, caches and platforms, from each one's public pages. - [E2B](https://groundbox.dev/compare/e2b.md): Groundbox and E2B sandboxes for AI agents side by side: CPU and memory prices, sizes, session length, isolation, pause and SDKs. - [Daytona](https://groundbox.dev/compare/daytona.md): Groundbox and Daytona sandboxes for AI agents side by side: CPU, memory and storage prices, isolation model, idle handling and SDKs. - [WarpBuild](https://groundbox.dev/compare/warpbuild.md): Groundbox and WarpBuild GitHub Actions runners side by side: per-minute prices, platforms, caches, isolation and where they run, from each one's own pages. - [RunsOn](https://groundbox.dev/compare/runs-on.md): Groundbox's hosted GitHub Actions runners next to RunsOn's runners in your own AWS account: license, billing, platforms, caches and how to switch. - [Ubicloud](https://groundbox.dev/compare/ubicloud.md): Groundbox and Ubicloud GitHub Actions runners side by side: per-minute prices, free minutes, billing, caches and self-hosting, from each one's own pages. - [BuildJet](https://groundbox.dev/compare/buildjet.md): BuildJet has shut down its GitHub Actions runners. How to move BuildJet jobs and buildjet/cache to Groundbox runners, with prices and steps. - [Modal](https://groundbox.dev/compare/modal.md): Groundbox and Modal Sandboxes for AI agents side by side: CPU and memory prices, isolation, timeouts, snapshots, GPUs and SDKs. - [Runloop](https://groundbox.dev/compare/runloop.md): Groundbox sandboxes and Runloop Devboxes side by side: CPU and memory prices, sizes, session length, suspend, snapshots and network policies. - [Vercel Sandbox](https://groundbox.dev/compare/vercel-sandbox.md): Groundbox and Vercel Sandbox side by side: active-CPU and memory prices, sizes, session limits, persistence, egress firewall and SDKs. - [Cloudflare Sandboxes](https://groundbox.dev/compare/cloudflare-sandbox.md): Groundbox sandboxes and Cloudflare's Sandbox SDK on Containers side by side: prices, sizes, lifetime, snapshots, network rules and SDKs. - [CodeSandbox SDK](https://groundbox.dev/compare/codesandbox.md): Groundbox sandboxes and the CodeSandbox SDK, now Together Code Sandbox, side by side: prices, billing, sizes, hibernation and SDKs. - [Fly.io Machines](https://groundbox.dev/compare/fly-io.md): Groundbox sandboxes and Fly.io Machines for running agent code side by side: per-size prices, billing, suspend, regions, Sprites and SDKs. - [Blaxel](https://groundbox.dev/compare/blaxel.md): Groundbox and Blaxel sandboxes for AI agents side by side: price per hour, standby and pause, fork, session limits, regions and SDKs, from each one's own pages. - [Tensorlake](https://groundbox.dev/compare/tensorlake.md): Groundbox and Tensorlake sandboxes side by side: active-CPU and memory prices, suspend, memory snapshots, session limits, GPUs and GitHub Actions runners. - [Northflank](https://groundbox.dev/compare/northflank.md): Groundbox and Northflank sandboxes side by side: CPU and memory prices, microVM isolation, pause, session length, BYOC and GPUs, from each one's own pages. - [Blacksmith vs Depot](https://groundbox.dev/compare/blacksmith-vs-depot.md): Blacksmith and Depot compared: $0.008 / min against $0.012 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Blacksmith vs GitHub-hosted runners](https://groundbox.dev/compare/blacksmith-vs-github-hosted-runners.md): Blacksmith and GitHub-hosted runners compared: $0.008 / min against $0.012 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Blacksmith vs Namespace](https://groundbox.dev/compare/blacksmith-vs-namespace.md): Blacksmith and Namespace compared: $0.008 / min against $0.012 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Blacksmith vs RunsOn](https://groundbox.dev/compare/blacksmith-vs-runs-on.md): Blacksmith and RunsOn compared: prices at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Blacksmith vs Ubicloud](https://groundbox.dev/compare/blacksmith-vs-ubicloud.md): Blacksmith and Ubicloud compared: $0.008 / min against $0.0025 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Blacksmith vs WarpBuild](https://groundbox.dev/compare/blacksmith-vs-warpbuild.md): Blacksmith and WarpBuild compared: $0.008 / min against $0.008 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Blaxel vs Cloudflare Sandboxes](https://groundbox.dev/compare/blaxel-vs-cloudflare-sandbox.md): Blaxel and Cloudflare Sandboxes compared: $0.17 / hour against $0.036 to $0.18 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs CodeSandbox SDK](https://groundbox.dev/compare/blaxel-vs-codesandbox.md): Blaxel and CodeSandbox SDK compared: $0.17 / hour against $0.15 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs Daytona](https://groundbox.dev/compare/blaxel-vs-daytona.md): Blaxel and Daytona compared: $0.17 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs E2B](https://groundbox.dev/compare/blaxel-vs-e2b.md): Blaxel and E2B compared: $0.17 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs Fly.io Machines](https://groundbox.dev/compare/blaxel-vs-fly-io.md): Blaxel and Fly.io Machines compared: $0.17 / hour against $0.092 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs Modal](https://groundbox.dev/compare/blaxel-vs-modal.md): Blaxel and Modal compared: $0.17 / hour against $0.24 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs Northflank](https://groundbox.dev/compare/blaxel-vs-northflank.md): Blaxel and Northflank compared: $0.17 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs Tensorlake](https://groundbox.dev/compare/blaxel-vs-tensorlake.md): Blaxel and Tensorlake compared: $0.17 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Blaxel vs Vercel Sandbox](https://groundbox.dev/compare/blaxel-vs-vercel-sandbox.md): Blaxel and Vercel Sandbox compared: $0.17 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs CodeSandbox SDK](https://groundbox.dev/compare/cloudflare-sandbox-vs-codesandbox.md): Cloudflare Sandboxes and CodeSandbox SDK compared: $0.036 to $0.18 / hour against $0.15 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs Daytona](https://groundbox.dev/compare/cloudflare-sandbox-vs-daytona.md): Cloudflare Sandboxes and Daytona compared: $0.036 to $0.18 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs E2B](https://groundbox.dev/compare/cloudflare-sandbox-vs-e2b.md): Cloudflare Sandboxes and E2B compared: $0.036 to $0.18 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs Fly.io Machines](https://groundbox.dev/compare/cloudflare-sandbox-vs-fly-io.md): Cloudflare Sandboxes and Fly.io Machines compared: $0.036 to $0.18 / hour against $0.092 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs Modal](https://groundbox.dev/compare/cloudflare-sandbox-vs-modal.md): Cloudflare Sandboxes and Modal compared: $0.036 to $0.18 / hour against $0.24 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs Northflank](https://groundbox.dev/compare/cloudflare-sandbox-vs-northflank.md): Cloudflare Sandboxes and Northflank compared: $0.036 to $0.18 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs Tensorlake](https://groundbox.dev/compare/cloudflare-sandbox-vs-tensorlake.md): Cloudflare Sandboxes and Tensorlake compared: $0.036 to $0.18 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Cloudflare Sandboxes vs Vercel Sandbox](https://groundbox.dev/compare/cloudflare-sandbox-vs-vercel-sandbox.md): Cloudflare Sandboxes and Vercel Sandbox compared: $0.036 to $0.18 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs Daytona](https://groundbox.dev/compare/codesandbox-vs-daytona.md): CodeSandbox SDK and Daytona compared: $0.15 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs E2B](https://groundbox.dev/compare/codesandbox-vs-e2b.md): CodeSandbox SDK and E2B compared: $0.15 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs Fly.io Machines](https://groundbox.dev/compare/codesandbox-vs-fly-io.md): CodeSandbox SDK and Fly.io Machines compared: $0.15 / hour against $0.092 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs Modal](https://groundbox.dev/compare/codesandbox-vs-modal.md): CodeSandbox SDK and Modal compared: $0.15 / hour against $0.24 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs Northflank](https://groundbox.dev/compare/codesandbox-vs-northflank.md): CodeSandbox SDK and Northflank compared: $0.15 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs Tensorlake](https://groundbox.dev/compare/codesandbox-vs-tensorlake.md): CodeSandbox SDK and Tensorlake compared: $0.15 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [CodeSandbox SDK vs Vercel Sandbox](https://groundbox.dev/compare/codesandbox-vs-vercel-sandbox.md): CodeSandbox SDK and Vercel Sandbox compared: $0.15 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Daytona vs E2B](https://groundbox.dev/compare/daytona-vs-e2b.md): Daytona and E2B compared: $0.17 / hour against $0.17 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Daytona vs Fly.io Machines](https://groundbox.dev/compare/daytona-vs-fly-io.md): Daytona and Fly.io Machines compared: $0.17 / hour against $0.092 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Daytona vs Modal](https://groundbox.dev/compare/daytona-vs-modal.md): Daytona and Modal compared: $0.17 / hour against $0.24 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Daytona vs Northflank](https://groundbox.dev/compare/daytona-vs-northflank.md): Daytona and Northflank compared: $0.17 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Daytona vs Tensorlake](https://groundbox.dev/compare/daytona-vs-tensorlake.md): Daytona and Tensorlake compared: $0.17 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Daytona vs Vercel Sandbox](https://groundbox.dev/compare/daytona-vs-vercel-sandbox.md): Daytona and Vercel Sandbox compared: $0.17 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Depot vs GitHub-hosted runners](https://groundbox.dev/compare/depot-vs-github-hosted-runners.md): Depot and GitHub-hosted runners compared: $0.012 / min against $0.012 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Depot vs Namespace](https://groundbox.dev/compare/depot-vs-namespace.md): Depot and Namespace compared: $0.012 / min against $0.012 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Depot vs RunsOn](https://groundbox.dev/compare/depot-vs-runs-on.md): Depot and RunsOn compared: prices at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Depot vs Ubicloud](https://groundbox.dev/compare/depot-vs-ubicloud.md): Depot and Ubicloud compared: $0.012 / min against $0.0025 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Depot vs WarpBuild](https://groundbox.dev/compare/depot-vs-warpbuild.md): Depot and WarpBuild compared: $0.012 / min against $0.008 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [E2B vs Fly.io Machines](https://groundbox.dev/compare/e2b-vs-fly-io.md): E2B and Fly.io Machines compared: $0.17 / hour against $0.092 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [E2B vs Modal](https://groundbox.dev/compare/e2b-vs-modal.md): E2B and Modal compared: $0.17 / hour against $0.24 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [E2B vs Northflank](https://groundbox.dev/compare/e2b-vs-northflank.md): E2B and Northflank compared: $0.17 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [E2B vs Tensorlake](https://groundbox.dev/compare/e2b-vs-tensorlake.md): E2B and Tensorlake compared: $0.17 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [E2B vs Vercel Sandbox](https://groundbox.dev/compare/e2b-vs-vercel-sandbox.md): E2B and Vercel Sandbox compared: $0.17 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Fly.io Machines vs Modal](https://groundbox.dev/compare/fly-io-vs-modal.md): Fly.io Machines and Modal compared: $0.092 / hour against $0.24 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Fly.io Machines vs Northflank](https://groundbox.dev/compare/fly-io-vs-northflank.md): Fly.io Machines and Northflank compared: $0.092 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Fly.io Machines vs Tensorlake](https://groundbox.dev/compare/fly-io-vs-tensorlake.md): Fly.io Machines and Tensorlake compared: $0.092 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Fly.io Machines vs Vercel Sandbox](https://groundbox.dev/compare/fly-io-vs-vercel-sandbox.md): Fly.io Machines and Vercel Sandbox compared: $0.092 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [GitHub-hosted runners vs Namespace](https://groundbox.dev/compare/github-hosted-runners-vs-namespace.md): GitHub-hosted runners and Namespace compared: $0.012 / min against $0.012 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [GitHub-hosted runners vs RunsOn](https://groundbox.dev/compare/github-hosted-runners-vs-runs-on.md): GitHub-hosted runners and RunsOn compared: prices at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [GitHub-hosted runners vs Ubicloud](https://groundbox.dev/compare/github-hosted-runners-vs-ubicloud.md): GitHub-hosted runners and Ubicloud compared: $0.012 / min against $0.0025 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [GitHub-hosted runners vs WarpBuild](https://groundbox.dev/compare/github-hosted-runners-vs-warpbuild.md): GitHub-hosted runners and WarpBuild compared: $0.012 / min against $0.008 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Modal vs Northflank](https://groundbox.dev/compare/modal-vs-northflank.md): Modal and Northflank compared: $0.24 / hour against $0.067 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Modal vs Tensorlake](https://groundbox.dev/compare/modal-vs-tensorlake.md): Modal and Tensorlake compared: $0.24 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Modal vs Vercel Sandbox](https://groundbox.dev/compare/modal-vs-vercel-sandbox.md): Modal and Vercel Sandbox compared: $0.24 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Namespace vs RunsOn](https://groundbox.dev/compare/namespace-vs-runs-on.md): Namespace and RunsOn compared: prices at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Namespace vs Ubicloud](https://groundbox.dev/compare/namespace-vs-ubicloud.md): Namespace and Ubicloud compared: $0.012 / min against $0.0025 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Namespace vs WarpBuild](https://groundbox.dev/compare/namespace-vs-warpbuild.md): Namespace and WarpBuild compared: $0.012 / min against $0.008 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Northflank vs Tensorlake](https://groundbox.dev/compare/northflank-vs-tensorlake.md): Northflank and Tensorlake compared: $0.067 / hour against $0.088 to $0.20 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Northflank vs Vercel Sandbox](https://groundbox.dev/compare/northflank-vs-vercel-sandbox.md): Northflank and Vercel Sandbox compared: $0.067 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [RunsOn vs Ubicloud](https://groundbox.dev/compare/runs-on-vs-ubicloud.md): RunsOn and Ubicloud compared: prices at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [RunsOn vs WarpBuild](https://groundbox.dev/compare/runs-on-vs-warpbuild.md): RunsOn and WarpBuild compared: prices at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. - [Tensorlake vs Vercel Sandbox](https://groundbox.dev/compare/tensorlake-vs-vercel-sandbox.md): Tensorlake and Vercel Sandbox compared: $0.088 to $0.20 / hour against $0.085 to $0.34 / hour at 2 vCPU and 4 GB, plus isolation, pause, sessions and self-host, from their own pages. - [Ubicloud vs WarpBuild](https://groundbox.dev/compare/ubicloud-vs-warpbuild.md): Ubicloud and WarpBuild compared: $0.0025 / min against $0.008 / min at a 4 vCPU Linux job, plus billing, platforms, sizes and free minutes, from their own pages. ## Optional - [CI runners](https://groundbox.dev/ci-runners): Change runs-on to switch. 2 / 4 / 8 / 16 vCPU at $0.003 / $0.006 / $0.011 / $0.021 a minute, billed by the second, with caches and mirrors next to the job. - [Flex](https://groundbox.dev/flex): The same runners at half price ($0.0015 / $0.003 / $0.0055 / $0.0105 a minute) for work that can wait. A flex job starts when a box has spare room and is never stopped once running. - [CI tune-up](https://groundbox.dev/ci-tune-up): An agent reads a repository's workflows in a sandbox and prepares one pull request: runner sizes, caches, parallel jobs. You review and merge. Free on every plan. - [Insights](https://groundbox.dev/ci-insights): For every GitHub Actions job on Groundbox runners: how long it takes, how often it fails, what it costs, the CPU and memory it uses, and the runner size it should be on. - [Test analytics](https://groundbox.dev/test-analytics): Each test across your CI runs, read from JUnit reports: which tests flake, which are slow and which fail most, with no workflow changes on Groundbox runners. - [Logs and terminals](https://groundbox.dev/ci-logs): Watch a GitHub Actions job's log while it runs, open a shell in its VM with groundbox ci ssh, keep a failed job's VM to debug it, and search a week of logs. - [Build cache](https://groundbox.dev/build-cache): A remote build cache for five build tools, shared by CI jobs, sandboxes, laptops and agents. Set up on Groundbox runners already, one store per team, included. - [Docker builds](https://groundbox.dev/docker-builds): Docker builds on a remote BuildKit builder with a layer cache kept per project. docker/build-push-action works unchanged. $0.011 a minute of builder time. - [Image registry](https://groundbox.dev/image-registry): A private OCI registry on the same machines as your CI runners and sandboxes. Log in with your API key; $0.05 per GB-month, pushes and pulls free. - [Storage](https://groundbox.dev/storage): S3-compatible buckets on the same API key and bill as CI and sandboxes. $0.015 per GB-month stored; any S3 client works. - [Sandboxes](https://groundbox.dev/sandboxes): A Linux VM for each agent. Fork, pause and resume, scheduled runs, an egress allowlist. $0.04 per vCPU-hour on dedicated cores. - [Time machine](https://groundbox.dev/time-machine): Save points of a running sandbox: its memory, its disk and every process. Rewind to any of them, or fork one moment into many copies. - [Templates and volumes](https://groundbox.dev/templates): Build a sandbox's disk once from an image, a Dockerfile or packages and start sandboxes from it. Volumes keep data at $0.08 per GB-month. - [Previews](https://groundbox.dev/previews): An app listening on a port in a sandbox at an HTTPS address: private to your team by default, shared by link, or public for webhooks. - [Scheduled runs](https://groundbox.dev/scheduled-runs): A cron expression, a sandbox spec and a command. Each run gets a fresh sandbox that is destroyed when the command exits. $0.04 per vCPU-hour while it runs. - [For coding agents](https://groundbox.dev/agents): One API key and one MCP server for CI and sandboxes. Scopes and a monthly spend cap on every key, and a prompt to hand to your agent. - [Agent computers](https://groundbox.dev/agent-computers): A Linux desktop with Chrome for each computer-use agent: screenshot, click and type by API or MCP, a live view for your app, and a handoff to a person. $0.04 per vCPU-hour. - [Pricing](https://groundbox.dev/pricing): Free: 3,000 CI minutes a month, no card. Paid: $20 a month with $20 of usage included. CI from $0.003 a minute, sandboxes $0.04 per vCPU-hour. - [Benchmark](https://groundbox.dev/benchmark): Groundbox CI runners against GitHub-hosted runners: the same ten open-source projects and workflows, 2 vCPU on both sides, cold and warm cache, medians with ranges. - [CI cost checker](https://groundbox.dev/ci-cost): Point it at a GitHub organization: a month of Actions minutes priced on GitHub, Blacksmith and Groundbox, the fixes ranked by minutes, and flaky tests. - [Status](https://groundbox.dev/status): Groundbox status: whether work is waiting, and job start times over the last 24 hours. - [Full text of the docs and guides](https://groundbox.dev/llms-full.txt): every page above as one Markdown file.