CI Runnerscirunners.org
Head-to-head

Namespace vs WarpBuild

Answer in brief

Namespace suits teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. WarpBuild suits teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account. Namespace is a managed service hosted by the vendor for GitHub Actions and Buildkite, priced at $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB); WarpBuild is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min.

By the CI Runners editors · Updated

Key differences between Namespace and WarpBuild

  • CI systems: Only Namespace documents Buildkite.
  • Isolation: Namespace: Virtual machine. WarpBuild: Ephemeral VM.
  • Published price: $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) (Namespace) versus $0.004/min (WarpBuild).
  • Largest runner: 64 vCPU / 512 GB (Namespace) versus 32 vCPU / 128 GB (WarpBuild).

What they have in common

  • Both are managed services hosted by the vendor.
  • Both run GitHub Actions jobs.
  • Both document Linux, macOS and Windows runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Both give every job a fresh environment.
  • Neither is open source.
  • Both document Docker layer caching.

Namespace vs WarpBuild at a glance

AttributeNamespaceWarpBuild
What it isManaged runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes.Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.
TypeManaged runner serviceManaged runner service
CI systemsGitHub Actions, BuildkiteGitHub Actions
Operating systemsLinux, macOS, WindowsLinux, macOS, Windows
Architecturesx64, arm64x64, arm64
IsolationEvery job runs in its own instance inside a virtual machine that is discarded when the job ends; the hypervisor is not namedEach runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build
Fresh environment per jobYesYes
HardwareNamespace says it deploys its own hardware in its own racks: AMD EPYC for Linux and Windows amd64, AmpereOne for Linux arm64 (Linux on Apple Silicon is in early access), and Apple M4 Pro and M5 Max for macOS.The cloud provider and CPU models behind the standard cloud runners are not documented; macOS runners and the “xfast” Linux arm64 runners use Apple M4 Pro and M5 Pro hardware.
Performance (vendor claim)Not documentedWarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims)
Runner sizesLinux up to 64 vCPU and 512 GB RAM, Windows up to 32 vCPU and 512 GB, macOS up to 16 vCPU and 56 GB; standard label shapes run from 2 vCPU / 4 GB to 32 vCPU / 64 GB, and instances over 64 GB RAM need special access2 to 32 vCPU with 8 to 128 GB RAM on Linux x64 and arm64; 4 to 32 vCPU with 16 to 128 GB on Windows; 6 or 12 vCPU with 14 or 28 GB on macOS
CachingCache Volumes persist data across runs; a runner profile can cache container images, toolchain downloads, action downloads and Git checkouts, and nscloud-cache-action replaces actions/cache. Docker builds go to Remote Builders with layer caching by default, and there are cache integrations for Bazel, Turborepo, Pants and Moonrepo.WarpBuild Cache (WarpBuilds/cache) is a drop-in replacement for actions/cache, enabled by default on Linux runners, with entries expiring 7 days after last use. Docker layer caching is offered through remote Docker Builders or a type=gha cache endpoint, and snapshot runners can save and boot from full VM disk snapshots on cloud Ubuntu runners.
Docker layer cachingYesYes
GPUNot documentedNot documented
ConcurrencyPer plan: Developer 32 Linux vCPU and 12 macOS vCPU; Team 64 Linux, 24 macOS and 32 Windows vCPU; Business 160 Linux, 48 macOS and 80 Windows vCPU; custom on EnterpriseUnlimited concurrency on Linux and Windows for generally available features; high-concurrency macOS requires contacting support
Static IPsYesYes
SSH into running jobsYesYes
PricingBilled in unit minutes (vCPU × minutes × platform multiplier: Linux 1, Windows 2, macOS 10), with a 1-minute minimum. Team is $100/month with 100,000 unit minutes and Business $250/month with 250,000; Developer is pay as you go. A 2 vCPU / 4 GB Linux runner is listed at $0.002/min prepaid and $0.003/min overage, 2 vCPU / 8 GB at $0.004 and $0.006, and macOS 6 vCPU / 14 GB at $0.06 and $0.09. Cache volume storage is $0.0048/GB-day on Developer, with free allowances on Team and Business.Cloud runners per minute: Linux x64 from $0.004 (2 vCPU) to $0.064 (32 vCPU); Linux arm64 from $0.003 to $0.048; Windows from $0.016 (4 vCPU) to $0.128; macOS $0.08 (6 vCPU) and $0.16 (12 vCPU). Cache storage is $0.20 per GB-month plus $0.0001 per operation, and snapshot restore is $0.04 per job. BYOC runners carry a $0.002/min fee, with infrastructure billed by your cloud provider and cache and snapshots free.
Free tier30-day free trial of Developer plan features, no credit card requiredNot documented
Open sourceNoNo
Self-host / your cloudNo / Not documentedNo / Yes
ComplianceSOC 2 Type IISOC 2 Type 2 (Security, Availability and Confidentiality criteria)
RegionsSpecific regions are not named; Namespace says it runs its own hardware at multiple sites, offers a regional preference on all plans and region-exclusive residency on enterprise plansNot listed for the standard cloud runners; region-specific infrastructure is offered on enterprise plans, and BYOC runners run in the region of your own stack
Company headquartersNot documentedNot documented
Good fit forTeams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapesTeams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Namespace

  • You want each job in its own virtual machine that is discarded when the job ends
  • You want cache volumes that persist container images, toolchains, action downloads and Git checkouts between runs
  • You need Linux, macOS and Windows runners, with Linux shapes up to 64 vCPU and 512 GB RAM
  • You run Buildkite as well as GitHub Actions and want one provider for both

Reasons to choose WarpBuild

  • You want the choice between vendor-hosted runners and runners inside your own AWS, Google Cloud or Azure account
  • You want each runner in its own VM that is destroyed after the build
  • You need Linux x64 and arm64, Windows and macOS runners under one account
  • You want to boot jobs from a saved VM disk snapshot for incremental builds

Trade-offs to check first

  • Namespace: Concurrency is capped per plan, for example 32 Linux vCPU on Developer and 64 on Team
  • Namespace: Maximum instance duration is 3 hours on Developer and 5 hours on Team
  • WarpBuild: Static IPs are available only with BYOC deployments
  • WarpBuild: WarpBuild Cache is not supported on Windows runners

Run your slowest workflow on both before deciding. See the full Namespace profile and WarpBuild profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Namespace or WarpBuild better?
Neither is better for every pipeline. Namespace suits teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. WarpBuild suits teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account.
What is the difference between Namespace and WarpBuild?
Only Namespace documents Buildkite. Isolation is Virtual machine on Namespace and Ephemeral VM on WarpBuild. Published price: $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) (Namespace) versus $0.004/min (WarpBuild). Largest runner: 64 vCPU / 512 GB (Namespace) versus 32 vCPU / 128 GB (WarpBuild).
Which is open source, Namespace or WarpBuild?
Neither is open source.
How do Namespace and WarpBuild isolate jobs?
Namespace: Every job runs in its own instance inside a virtual machine that is discarded when the job ends; the hypervisor is not named. WarpBuild: Each runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build.
How does Namespace pricing compare with WarpBuild?
Namespace: Billed in unit minutes (vCPU × minutes × platform multiplier: Linux 1, Windows 2, macOS 10), with a 1-minute minimum. Team is $100/month with 100,000 unit minutes and Business $250/month with 250,000; Developer is pay as you go. A 2 vCPU / 4 GB Linux runner is listed at $0.002/min prepaid and $0.003/min overage, 2 vCPU / 8 GB at $0.004 and $0.006, and macOS 6 vCPU / 14 GB at $0.06 and $0.09. Cache volume storage is $0.0048/GB-day on Developer, with free allowances on Team and Business. WarpBuild: Cloud runners per minute: Linux x64 from $0.004 (2 vCPU) to $0.064 (32 vCPU); Linux arm64 from $0.003 to $0.048; Windows from $0.016 (4 vCPU) to $0.128; macOS $0.08 (6 vCPU) and $0.16 (12 vCPU). Cache storage is $0.20 per GB-month plus $0.0001 per operation, and snapshot restore is $0.04 per job. BYOC runners carry a $0.002/min fee, with infrastructure billed by your cloud provider and cache and snapshots free. Rates change, so check the Namespace and WarpBuild pricing pages before deciding.
Is Namespace or WarpBuild faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Namespace: Not documented. WarpBuild: WarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims).
Do Namespace and WarpBuild cache Docker layers?
Namespace: Cache Volumes persist data across runs; a runner profile can cache container images, toolchain downloads, action downloads and Git checkouts, and nscloud-cache-action replaces actions/cache. Docker builds go to Remote Builders with layer caching by default, and there are cache integrations for Bazel, Turborepo, Pants and Moonrepo. WarpBuild: WarpBuild Cache (WarpBuilds/cache) is a drop-in replacement for actions/cache, enabled by default on Linux runners, with entries expiring 7 days after last use. Docker layer caching is offered through remote Docker Builders or a type=gha cache endpoint, and snapshot runners can save and boot from full VM disk snapshots on cloud Ubuntu runners.
Where do Namespace and WarpBuild runners run?
Namespace is a managed service hosted by the vendor. WarpBuild is a managed service hosted by the vendor (AWS, Google Cloud and Azure).

Sources

  1. namespace.so/
  2. namespace.so/pricing
  3. namespace.so/docs/solutions/github-actions
  4. namespace.so/docs/reference/github-actions/runner-configuration
  5. warpbuild.com/
  6. warpbuild.com/pricing
  7. warpbuild.com/docs/ci
  8. warpbuild.com/docs/ci/cloud-runners

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). Namespace vs WarpBuild. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/namespace-vs-warpbuild/