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. Fly.io Machines

Groundbox vs Fly.io Machines for agent sandboxes.

Fly.io Machines are general microVMs you can place in many regions, run through a REST API and the flyctl CLI. Pick Fly.io for many regions, volumes, Machines that start on an incoming request, or its Sprites sandboxes. Pick Groundbox for TypeScript and Python SDKs and an MCP server, a spend cap on every key, and CI runners on the same key.

Start free, no cardHow to switch
2 vCPU · 4 GB, one hourlist prices
Groundbox$0.08 / hour
Fly.io Machines$0.092 / hour

sources: groundbox.dev/pricing · fly.io · checked 2026-11-20

Side by side

Groundbox and Fly.io Machines
FeatureGroundboxFly.io Machines
Price, 2 vCPU · 4 GB$0.08 / hour$0.092 / hour
Pause keeps memoryYes, memory and diskYes, for Machines with 2 GB or less
CI runners tooYes, on the same key and billNo: the pricing page lists no CI runners
IsolationFirecracker VMFirecracker microVM
Fork and snapshotsFork a running sandbox; save pointsClone copies the config; volume snapshots
Longest session720 hours, renewableNot published
Self-hostNoNot published
GPUsNot offeredNot published
Largest size16 vCPU16 CPUs
SDK languagesTypeScript and PythonNone: a REST API and the flyctl CLI
Security reportNo SOC 2 reportSOC 2 Type 2
Free to start$5 of usage, no cardNo plan fee; pay as you go

Fly.io Machines are Firecracker microVMs you start through a REST API, in many regions. Fly also sells Sprites, a sandbox for agents. 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 Fly.io Machines for

  • many regions, priced per region
  • a proxy that stops idle Machines and starts them on the next request
  • persistent volumes and volume snapshots
  • Sprites: sandboxes billed on the CPU and memory they use

Pick Groundbox for

  • SDKs for TypeScript and Python and an MCP server
  • memory included in the CPU price ($0.04 per vCPU-hour), on dedicated cores
  • 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

Every row: Groundbox and Fly.io Machines
FeatureGroundboxFly.io Machines
PlansFree: everything, with $5 of usage. $20 / month: $20 of usage included, then pay as you goNo plan fee; pay as you go
CPU$0.04 per vCPU-hour, a dedicated coreperformance-2x with 4 GB: $0.0917 an hour in iad; other regions cost more or less
MemoryIncluded, up to 4 GB per vCPU$6 per GB-month past what the size includes
Storage20 GB disk by default, up to 100 GBVolumes and stopped root disks $0.15 per GB-month
BillingPer second, no minimumPer second while running
Sizes1 to 16 vCPU, up to 4 GB per vCPU1 to 16 CPUs, shared or performance
Default size2 vCPU, 4 GB RAM, 20 GB disk1 shared CPU, 256 MB (API default)
IsolationA Firecracker VM, a new one per job or sandboxFirecracker microVM
Pause and resumeYes, memory and disk; $0.05 per GB-month while pausedSuspend keeps memory, for Machines with 2 GB or less
Fork and snapshotsFork a running sandbox with its files and processes; save points to rewind tofly machine clone copies a Machine's config; volume snapshots
SDKsTypeScript and Python, plus a REST API, CLI and MCP serverA REST API and the flyctl CLI
Agent sandboxes$0.04 per vCPU-hour with memory included, 1 to 16 vCPUSprites: $0.0385 per CPU-hour and $0.021875 per GB-hour of actual use; 8 vCPU, 100 GB disk
Security reportsNo SOC 2 reportSOC 2 Type 2

A month at list price

One sandbox with 2 vCPU and 4 GiB of memory, running 100 hours in a month:

One sandbox with 2 vCPU and 4 GiB of memory, running 100 hours in a month: Groundbox and Fly.io Machines
Groundbox$8.00 ($0.04 per vCPU-hour, memory included). On the $20 plan it fits in the $20 of usage included.
Fly.io Machines$9.17 for a performance-2x Machine with 4 GB, in iad

Fly prices sizes, not vCPU and memory apart, and other regions cost more or less. Shared-CPU Machines cost less than performance ones. 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

  1. Create an API key in the dashboard. An agent can also sign itself up with groundbox signup and send its person a claim link.
  2. Install an SDK: npm i @groundbox/sdk or pip install groundbox.
  3. 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.
  4. 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 Fly.io?At list price, one 2 vCPU, 4 GiB sandbox for 100 hours costs $8.00 on Groundbox and $9.17 (a performance-2x Machine with 4 GB, in iad) on Fly.io, before plan fees and credits.
How do I move an agent from Fly.io 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 Fly.io?Each Groundbox sandbox is its own Firecracker VM on dedicated cores. Fly.io Machines are Firecracker microVMs too.
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. Fly.io states no time limit for a running Machine.
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

Fly.io Machines's facts come from its own pages, read on the day shown. Prices change; their pages are the final word.

  • Fly.io pricing, checked 2026-11-20
  • Fly.io docs: pricing, checked 2026-11-19
  • Fly.io docs: Machine sizing, checked 2026-11-19
  • Fly.io docs: Machines API, checked 2026-11-19
  • Fly.io docs: suspend and resume, checked 2026-11-19
  • Fly.io docs: Machines overview, checked 2026-11-19
  • Fly.io docs: Machines, checked 2026-11-19
  • Fly.io security questionnaire, checked 2026-11-19
  • Fly.io Sprites
  • Fly.io Sprites pricing, checked 2026-11-19

Also compared

Blaxel vs Fly.io MachinesCloudflare Sandboxes vs Fly.io MachinesCodeSandbox SDK vs Fly.io MachinesDaytona vs Fly.io MachinesE2B vs Fly.io MachinesFly.io Machines vs ModalFly.io Machines vs NorthflankFly.io Machines vs TensorlakeFly.io Machines vs Vercel SandboxGroundbox vs Cloudflare SandboxesGroundbox vs E2BGroundbox vs NorthflankSandboxes for agentsPricingFirst sandboxAll comparisons

Try it on your own repo.

Start free, no cardBook a call