CI Runnerscirunners.org
Head-to-head

Blacksmith vs BuildPulse Runners

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. BuildPulse Runners suits teams on GitHub Actions, CircleCI or Semaphore that want Linux runners bundled with cache storage and flaky-test analytics. Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; BuildPulse Runners is a managed service hosted by the vendor for GitHub Actions, CircleCI and Semaphore, priced at $0.004/min.

By the CI Runners editors · Updated

Key differences between Blacksmith and BuildPulse Runners

  • CI systems: Only BuildPulse Runners documents CircleCI and Semaphore.
  • Operating systems: Only Blacksmith documents macOS and Windows.
  • Isolation: Blacksmith: Firecracker microVM. BuildPulse Runners: Fresh per-job runner.
  • Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 64 vCPU / 256 GB (BuildPulse Runners).

What they have in common

  • Both are managed services hosted by the vendor.
  • Both run GitHub Actions jobs.
  • Both document Linux runners.
  • Both document arm64 runners.
  • Both give every job a fresh environment.
  • Neither is open source.
  • Both document Docker layer caching.

Blacksmith vs BuildPulse Runners at a glance

AttributeBlacksmithBuildPulse Runners
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 Linux runners for GitHub Actions, CircleCI and Semaphore with included cache storage and flaky-test detection on every run.
TypeManaged runner serviceManaged runner service
CI systemsGitHub ActionsGitHub Actions, CircleCI, Semaphore
Operating systemsLinux, macOS, WindowsLinux
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 job runs on a fresh runner that is discarded when the job ends; the isolation boundary is not documented
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.x64 runners on AMD EPYC 9R45 (Zen 5) according to an October 2026 benchmark post; arm64 runners on Graviton; NVMe-backed Docker builder runners from 4x to 32x.
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)BuildPulse says its 4-vCPU runners were 1.3x to 2.1x faster than GitHub’s ubuntu-latest in its own October 2026 benchmark (vendor claim)
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 vCPU / 8 GB to 64 vCPU / 256 GB on x64; the same vCPU counts on arm64
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.250 GB of cache storage is included for Docker layer, dependency and build caches that persist across runs; storage beyond that is $0.20 per GB per month. Docker builder runners keep each customer’s layer cache between builds.
Docker layer cachingYesYes
GPUNot documentedNot documented
ConcurrencyBlacksmith documents no limit on concurrent jobs or vCPUsGoverned by a per-organization CPU quota that can be raised on request; there is no per-plan limit on parallel jobs
Static IPsYesYes
SSH into running jobsYesNot documented
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.Linux x64 per minute (list prices dated September 2026): $0.004 (2 vCPU / 8 GB), $0.008 (4 vCPU), $0.016 (8 vCPU), $0.032 (16 vCPU), $0.064 (32 vCPU), $0.128 (64 vCPU). arm64 is $0.0025 per minute at 2 vCPU. Billed per minute, rounded up per job; cache storage beyond the included 250 GB is $0.20 per GB per month.
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 rates3,000 free minutes every month, with no credit card required
Open sourceNoNo
Self-host / your cloudNo / Not documentedNo / Not documented
ComplianceSOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progressNot documented
Regionsus-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting supportBuildPulse says its services run entirely on AWS in the United States; runner regions are not listed separately
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, CircleCI or Semaphore that want Linux runners bundled with cache storage and flaky-test analytics

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 BuildPulse Runners

  • You want one runner vendor across GitHub Actions, CircleCI and Semaphore
  • You want 3,000 free minutes each month and 250 GB of cache storage included
  • You want flaky-test detection and per-test timing on every run without extra setup
  • You need runners that egress from fixed IP addresses for allowlisting

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
  • BuildPulse Runners: Not yet SOC 2 attested; the security page says a Type I attestation is being pursued
  • BuildPulse Runners: Runners register with GitHub organizations, not personal accounts

Run your slowest workflow on both before deciding. See the full Blacksmith profile and BuildPulse Runners profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Blacksmith or BuildPulse Runners 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. BuildPulse Runners suits teams on GitHub Actions, CircleCI or Semaphore that want Linux runners bundled with cache storage and flaky-test analytics.
What is the difference between Blacksmith and BuildPulse Runners?
Only BuildPulse Runners documents CircleCI and Semaphore. Only Blacksmith documents macOS and Windows. Isolation is Firecracker microVM on Blacksmith and Fresh per-job runner on BuildPulse Runners. Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 64 vCPU / 256 GB (BuildPulse Runners).
Which is open source, Blacksmith or BuildPulse Runners?
Neither is open source.
How do Blacksmith and BuildPulse Runners 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. BuildPulse Runners: Each job runs on a fresh runner that is discarded when the job ends; the isolation boundary is not documented.
How does Blacksmith pricing compare with BuildPulse Runners?
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. BuildPulse Runners: Linux x64 per minute (list prices dated September 2026): $0.004 (2 vCPU / 8 GB), $0.008 (4 vCPU), $0.016 (8 vCPU), $0.032 (16 vCPU), $0.064 (32 vCPU), $0.128 (64 vCPU). arm64 is $0.0025 per minute at 2 vCPU. Billed per minute, rounded up per job; cache storage beyond the included 250 GB is $0.20 per GB per month. Rates change, so check the Blacksmith and BuildPulse Runners pricing pages before deciding.
Is Blacksmith or BuildPulse Runners 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). BuildPulse Runners: BuildPulse says its 4-vCPU runners were 1.3x to 2.1x faster than GitHub’s ubuntu-latest in its own October 2026 benchmark (vendor claim).
Do Blacksmith and BuildPulse Runners 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. BuildPulse Runners: 250 GB of cache storage is included for Docker layer, dependency and build caches that persist across runs; storage beyond that is $0.20 per GB per month. Docker builder runners keep each customer’s layer cache between builds.
Where do Blacksmith and BuildPulse Runners runners run?
Blacksmith is a managed service hosted by the vendor. BuildPulse Runners is a managed service hosted by the vendor.

Sources

  1. blacksmith.sh/
  2. blacksmith.sh/pricing
  3. blacksmith.sh/security
  4. docs.blacksmith.sh/blacksmith-runners/overview
  5. buildpulse.io/products/runners
  6. buildpulse.io/runners/github-actions
  7. buildpulse.io/pricing
  8. buildpulse.io/security

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 BuildPulse Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/blacksmith-vs-buildpulse-runners/