BuildPulse Runners
Managed Linux runners for GitHub Actions, CircleCI and Semaphore with included cache storage and flaky-test detection on every run. A managed Linux runner service for GitHub Actions, CircleCI and Semaphore that suits teams wanting runners, caching and test analytics from one vendor.
Overview
BuildPulse Runners is a managed runner service from BuildPulse, a company also known for flaky-test detection. On GitHub Actions a team installs the BuildPulse GitHub App on its organization and changes runs-on to a label such as bp-ubuntu-latest-x64-4x. Linux runners come in six sizes from 2 to 64 vCPU on x64 and arm64, and each job runs on a fresh runner that is discarded when the job ends.
The same runners can serve CircleCI through a namespaced resource class and Semaphore through an agent machine type. Billing is per minute with no minimums or commitment. Every account gets 3,000 free minutes a month and 250 GB of cache storage for Docker layers, dependencies and build outputs. Each run is parsed for flaky tests and per-test timing, and runners egress from four fixed addresses, with a dedicated egress IP available on request.
Notable
- October 23, 2026: BuildPulse published a benchmark of its runners against GitHub-hosted runners, with a public benchmark repository.
- September 2026: the date given for the current runner list prices on the product and pricing pages.
- As of November 22, 2026 the security page says BuildPulse is pursuing a SOC 2 Type I attestation.
BuildPulse Runners specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions, CircleCI, Semaphore |
| Operating systems | Linux |
| Architectures | x64, arm64 |
| Deployment | Managed runner service |
| Isolation | Each job runs on a fresh runner that is discarded when the job ends; the isolation boundary is not documented |
| Fresh environment per job | Yes |
| Hardware | 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) | 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 sizes | 2 vCPU / 8 GB to 64 vCPU / 256 GB on x64; the same vCPU counts on arm64 |
| 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 caching | Yes |
| GPU | Not documented |
| Concurrency | Governed by a per-organization CPU quota that can be raised on request; there is no per-plan limit on parallel jobs |
| Job limits | Not documented |
| Static IPs | Yes |
| SSH into running jobs | Not documented |
| Observability | Flaky-test detection and per-test timing on every run, plus per-organization usage analytics across GitHub Actions, CircleCI and Semaphore |
| Setup | Install the BuildPulse GitHub App on an organization and change runs-on to a bp-* label. For CircleCI, set a namespaced resource_class; for Semaphore, set the agent machine type. |
| Example label | bp-ubuntu-latest-x64-4x |
| Pricing | 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 tier | 3,000 free minutes every month, with no credit card required |
| Compliance | Not documented |
| Regions | BuildPulse says its services run entirely on AWS in the United States; runner regions are not listed separately |
| Open source | No |
| Company headquarters | Not documented |
Facts from BuildPulse Runners’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- 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
- Not yet SOC 2 attested; the security page says a Type I attestation is being pursued
- Runners register with GitHub organizations, not personal accounts
- The isolation boundary between jobs is not documented
- Windows and macOS runners are not documented
Good fit for: Teams on GitHub Actions, CircleCI or Semaphore that want Linux runners bundled with cache storage and flaky-test analytics.
Use cases BuildPulse Runners fits
- Faster builds: BuildPulse reports 1.3x to 2.1x faster runs than GitHub’s ubuntu-latest at 4 vCPU in its own benchmark (vendor claim).
- Lower CI cost: Linux x64 runners are listed at $0.004 per minute for 2 vCPU, with 3,000 free minutes a month.
- Docker builds: Docker layer caches persist across runs, and NVMe-backed Docker builder runners are offered.
- ARM64 builds: arm64 runners on Graviton are offered in the same vCPU sizes as x64, from $0.0025 per minute at 2 vCPU.
How BuildPulse Runners compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| BuildPulse Runners | GitHub Actions, CircleCI, Semaphore | Linux, x64, arm64 | Vendor-hosted | Fresh per-job runner | $0.004/min | 64 vCPU / 256 GB | Yes | Not documented | No | Not documented |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
| Depot GitHub Actions Runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Single-tenant EC2 instance | $0.006/min | 64 vCPU / 256 GB | Yes | Yes | No | Not documented |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
Head-to-head: Blacksmith vs BuildPulse Runners
Frequently asked questions
What is BuildPulse Runners?
Which CI systems does BuildPulse Runners work with?
How does BuildPulse Runners isolate jobs?
Is BuildPulse Runners open source?
How much does BuildPulse Runners cost?
How do I switch from GitHub-hosted runners to BuildPulse Runners?
bp-ubuntu-latest-x64-4x.How fast is BuildPulse Runners?
Does BuildPulse Runners have a free tier?
Does BuildPulse Runners support ARM64 runners?
Does BuildPulse Runners cache Docker layers?
How many jobs can run at once on BuildPulse Runners?
Where do BuildPulse Runners runners run?
What are the alternatives to BuildPulse Runners?
Sources
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). BuildPulse Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/buildpulse-runners/