CI Runnerscirunners.org
Head-to-head

Blacksmith vs WarpBuild

Answer in brief

Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. 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. Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; 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 Blacksmith and WarpBuild

  • Isolation: Blacksmith: Firecracker microVM. WarpBuild: Ephemeral VM.

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 give every job a fresh environment.
  • Neither is open source.
  • Both document Docker layer caching.

Blacksmith vs WarpBuild at a glance

AttributeBlacksmithWarpBuild
What it isManaged GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners.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 ActionsGitHub Actions
Operating systemsLinux, macOS, WindowsLinux, macOS, Windows
Architecturesx64, arm64x64, arm64
IsolationEach Linux and Windows job runs in an ephemeral Firecracker microVM on Blacksmith’s bare-metal hosts and is destroyed afterwards; the isolation used for macOS runners is not documentedEach runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build
Fresh environment per jobYesYes
HardwareBlacksmith describes its hosts as bare-metal machines with gaming CPUs chosen for single-core performance and NVMe drives, in ISO 27001 data centers; CPU models are not named, and macOS runners use Apple M4.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)Blacksmith says most CI jobs run about 2x faster than on GitHub-hosted runners and cache downloads about 4x faster, and that customers report 2x to 40x faster Docker builds (vendor claims)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; 2 to 32 vCPU with 6 to 96 GB on Linux arm64; 2 to 32 vCPU with 7 to 112 GB on Windows x64 (public beta); 6 or 12 vCPU with 24 or 48 GB on macOS2 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
CachingStandard cache actions (actions/cache and the setup-* actions) are served from a cache in the same data center as the runners, with 25 GB of free storage per repository per week and eviction of entries unused for 7 days. Docker layers persist on NVMe-backed sticky disks through useblacksmith/setup-docker-builder, billed at $0.50/GB/month; the docs also cover Git checkout, container image and Bazel, Go, Turborepo and Nx build caching.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
ConcurrencyBlacksmith documents no limit on concurrent jobs or vCPUsUnlimited concurrency on Linux and Windows for generally available features; high-concurrency macOS requires contacting support
Static IPsYesYes
SSH into running jobsYesYes
PricingThe pricing page lists Ubuntu x64 at $0.004/min, Ubuntu ARM at $0.0025/min, Windows x64 at $0.008/min and macOS M4 at $0.08/min; the docs say runners cost half of GitHub’s per-minute rate. Add-ons: Docker layer caching and sticky disks at $0.50/GB/month and static IPs at $100/IP/month. Flex scheduling costs 40% less for jobs that can wait up to 24 hours to start.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 tier3,000 free minutes per organization per month, counted as x64 2-vCPU minutes; larger, ARM, Windows and macOS runners consume them at weighted ratesNot documented
Open sourceNoNo
Self-host / your cloudNo / Not documentedNo / Yes
ComplianceSOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progressSOC 2 Type 2 (Security, Availability and Confidentiality criteria)
Regionsus-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting supportNot 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 headquartersSan Francisco, California, United StatesNot documented
Good fit forTeams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observabilityTeams 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 Blacksmith

  • You want each Linux or Windows job in its own Firecracker microVM that is destroyed after the job
  • You want Docker layers kept on persistent NVMe-backed disks between runs
  • You need to run many jobs at once: Blacksmith documents no concurrency limit
  • You want to SSH into running jobs and search CI logs from one console

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

  • Blacksmith: Available to GitHub organizations only, not personal repositories
  • Blacksmith: Windows runners are in public beta and do not support Docker Linux containers
  • 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 Blacksmith profile and WarpBuild profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Blacksmith or WarpBuild better?
Neither is better for every pipeline. Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. 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 Blacksmith and WarpBuild?
Isolation is Firecracker microVM on Blacksmith and Ephemeral VM on WarpBuild.
Which is open source, Blacksmith or WarpBuild?
Neither is open source.
How do Blacksmith and WarpBuild isolate jobs?
Blacksmith: Each Linux and Windows job runs in an ephemeral Firecracker microVM on Blacksmith’s bare-metal hosts and is destroyed afterwards; the isolation used for macOS runners is not documented. WarpBuild: Each runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build.
How does Blacksmith pricing compare with WarpBuild?
Blacksmith: The pricing page lists Ubuntu x64 at $0.004/min, Ubuntu ARM at $0.0025/min, Windows x64 at $0.008/min and macOS M4 at $0.08/min; the docs say runners cost half of GitHub’s per-minute rate. Add-ons: Docker layer caching and sticky disks at $0.50/GB/month and static IPs at $100/IP/month. Flex scheduling costs 40% less for jobs that can wait up to 24 hours to start. 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 Blacksmith and WarpBuild pricing pages before deciding.
Is Blacksmith or WarpBuild faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Blacksmith: Blacksmith says most CI jobs run about 2x faster than on GitHub-hosted runners and cache downloads about 4x faster, and that customers report 2x to 40x faster Docker builds (vendor claims). WarpBuild: WarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims).
Do Blacksmith and WarpBuild cache Docker layers?
Blacksmith: Standard cache actions (actions/cache and the setup-* actions) are served from a cache in the same data center as the runners, with 25 GB of free storage per repository per week and eviction of entries unused for 7 days. Docker layers persist on NVMe-backed sticky disks through useblacksmith/setup-docker-builder, billed at $0.50/GB/month; the docs also cover Git checkout, container image and Bazel, Go, Turborepo and Nx build caching. 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 Blacksmith and WarpBuild runners run?
Blacksmith is a managed service hosted by the vendor. WarpBuild is a managed service hosted by the vendor (AWS, Google Cloud and Azure).

Sources

  1. blacksmith.sh/
  2. blacksmith.sh/pricing
  3. blacksmith.sh/security
  4. docs.blacksmith.sh/blacksmith-runners/overview
  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). Blacksmith vs WarpBuild. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/blacksmith-vs-warpbuild/