CI Runnerscirunners.org
Runner profile · Managed runner service

WarpBuild

Answer in brief

Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account. A managed GitHub Actions runner service with a bring-your-own-cloud option, suited to teams that want hosted runners with a path to running them in their own cloud account.

By the CI Runners editors · Updated

Overview

WarpBuild provides runners for GitHub Actions in two forms. Its cloud runners are hosted by WarpBuild: after installing the GitHub App on an organization, a team changes runs-on to a label such as warp-ubuntu-latest-x64-4x. Each runner is a virtual machine created on demand and destroyed after the build. Linux x64 and arm64, Windows x64 and Apple Silicon macOS runners are offered, and concurrency on Linux and Windows is documented as unlimited.

The second form is Bring Your Own Cloud: WarpBuild provisions and manages runners inside your AWS, Google Cloud or Azure account for a per-minute fee, with support for custom images, spot instances and static IPs. Around the runners it offers a cache action, remote Docker builders, snapshot runners that boot from a saved disk image, and observability with OTLP export. Static IPs are a BYOC-only feature, and the GitHub App cannot be installed on personal accounts.

Notable

  • Cloud spot runners and Windows 2 vCPU runners were removed on 8 June 2026, according to the cloud runner docs.
  • macOS 13 runners were removed on 8 June 2026.
  • From 1 October 2026 the 6 vCPU macOS runners have 14 GB RAM and the 12 vCPU runners 28 GB, with prices unchanged.

WarpBuild specifications

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux, macOS, Windows
Architecturesx64, arm64
DeploymentManaged runner service · BYOC available
Where it can runAWS, Google Cloud, Azure
IsolationEach runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build
Fresh environment per jobYes
HardwareThe 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)WarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims)
Runner sizes2 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
CachingWarpBuild 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 cachingYes
GPUNot documented
ConcurrencyUnlimited concurrency on Linux and Windows for generally available features; high-concurrency macOS requires contacting support
Job limitsNot documented
Static IPsYes
SSH into running jobsYes
ObservabilityCPU, memory, filesystem and network metrics, system and GitHub Actions logs, right-sizing recommendations, and export to your own OTLP backend.
SetupSign up, install the WarpBuild GitHub App on a GitHub organization, then change runs-on to a WarpBuild label; an MCP-based flow can open the pull request for you. For BYOC, connect a cloud account and create a stack first. Personal accounts are not supported.
Example labelwarp-ubuntu-latest-x64-4x
PricingCloud 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 tierNot documented
ComplianceSOC 2 Type 2 (Security, Availability and Confidentiality criteria)
RegionsNot 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
Open sourceNo
Company headquartersNot documented

Facts from WarpBuild’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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
  • You need to export runner metrics and logs to your own OTLP backend

Trade-offs

  • Static IPs are available only with BYOC deployments
  • WarpBuild Cache is not supported on Windows runners
  • Snapshot runners work only on cloud Ubuntu runners, not on BYOC, Windows or macOS
  • macOS runners do not support nested virtualization or Docker

Good fit for: 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.

Use cases WarpBuild fits

  • Faster builds: WarpBuild advertises 2x faster builds and offers a cache action, snapshot runners and remote Docker builders (vendor claim).
  • Lower CI cost: Linux x64 cloud runners start at $0.004/min and BYOC runners carry a $0.002/min fee on top of your own cloud bill.
  • Docker builds: Remote Docker Builders build and push images with layer caching, and a type=gha cache endpoint is available on runners.
  • ARM64 builds: Linux arm64 runners from 2 to 32 vCPU start at $0.003/min, with Apple Silicon “xfast” variants.
  • macOS and iOS builds: macOS runners on Apple M4 Pro and M5 Pro hardware are offered with 6 or 12 vCPU.
  • Windows builds: Windows Server 2022 and 2025 x64 runners from 4 to 32 vCPU are offered.
  • Your own cloud: WarpBuild provisions and manages runners inside your own AWS, Google Cloud or Azure account.

How WarpBuild compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
NamespaceGitHub Actions, BuildkiteLinux, macOS, Windows, x64, arm64Vendor-hostedVirtual machine$0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)64 vCPU / 512 GBYesNot documentedNoNot documented
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States

Head-to-head: Blacksmith vs WarpBuild · Cirun vs WarpBuild · Depot GitHub Actions Runners vs WarpBuild · GitHub-hosted runners vs WarpBuild · Namespace vs WarpBuild · RunsOn vs WarpBuild · Ubicloud Runners vs WarpBuild

See all WarpBuild alternatives →

Frequently asked questions

What is WarpBuild?
Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account. A managed GitHub Actions runner service with a bring-your-own-cloud option, suited to teams that want hosted runners with a path to running them in their own cloud account.
Which CI systems does WarpBuild work with?
WarpBuild runs jobs for GitHub Actions, on Linux, macOS, Windows, x64 and arm64.
How does WarpBuild isolate jobs?
WarpBuild documents its isolation as: Each runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build. Each job gets a fresh environment that is discarded afterwards.
Is WarpBuild open source?
No, WarpBuild is not open source. It does run in your own cloud account or on your own hardware.
How much does WarpBuild cost?
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. Check the official pricing page for current rates.
How do I switch from GitHub-hosted runners to WarpBuild?
Sign up, install the WarpBuild GitHub App on a GitHub organization, then change runs-on to a WarpBuild label; an MCP-based flow can open the pull request for you. For BYOC, connect a cloud account and create a stack first. Personal accounts are not supported. An example label is warp-ubuntu-latest-x64-4x.
How fast is WarpBuild?
WarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims). Speed figures are the provider’s own and depend on the workload.
Does WarpBuild support ARM64 runners?
Yes, WarpBuild documents arm64 runners (Linux, macOS and Windows).
Does WarpBuild offer macOS runners?
Yes, WarpBuild documents macOS runners alongside Linux and Windows.
Does WarpBuild cache Docker layers?
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.
Can WarpBuild run in my own cloud account?
Yes, WarpBuild documents a bring-your-own-cloud option on AWS, Google Cloud and Azure.
How many jobs can run at once on WarpBuild?
Unlimited concurrency on Linux and Windows for generally available features; high-concurrency macOS requires contacting support.
Where do WarpBuild runners run?
Not 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.
What compliance certifications does WarpBuild have?
SOC 2 Type 2 (Security, Availability and Confidentiality criteria).
What are the alternatives to WarpBuild?

Sources

  1. warpbuild.com/
  2. warpbuild.com/pricing
  3. warpbuild.com/docs/ci
  4. warpbuild.com/docs/ci/cloud-runners
  5. warpbuild.com/docs/ci/byoc
  6. warpbuild.com/docs/ci/byoc/aws
  7. warpbuild.com/docs/ci/security
  8. warpbuild.com/docs/ci/quick-start
  9. warpbuild.com/docs/ci/features/caching
  10. warpbuild.com/docs/ci/features/observability
  11. warpbuild.com/docs/ci/features/snapshot-runners
  12. warpbuild.com/legal/terms

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). WarpBuild. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/warpbuild/