BuildPulse vs Blacksmith
A Blacksmith alternative for GitHub Actions runners, at the same $0.004 a minute. BuildPulse includes 250 GB of cache storage and fixed egress IPs in that price, finds flaky tests on every run, and runs CircleCI and Semaphore jobs on the same machines.
250 GB
of cache storage included every month. Blacksmith lists $0.50 per GB a month
$0
for fixed egress IPs: 4 addresses included. Blacksmith lists $100 per IP a month
64 vCPU
largest runner, twice Blacksmith’s 32
3 CIs
GitHub Actions, CircleCI and Semaphore on the same machines
At a glance
| Blacksmith runners | BuildPulse runners | |
|---|---|---|
| Price per minute, x64 2 vCPU | $0.004 | $0.004, the same |
| Price per minute, arm64 2 vCPU | $0.0025 | $0.0025, the same |
| Cache storage | $0.50 per GB a month for Docker layer caching and sticky disks | 250 GB included every month, then $0.20 per GB a month |
| Fixed egress IPs | $100 per IP a month | 4 fixed addresses included, ready to allowlist |
| Flaky test detection | Not on Blacksmith’s pricing page | Included with every run: detection, quarantine and per-test timing |
| CI providers | GitHub Actions | GitHub Actions, CircleCI and Semaphore, on the same machines and prices |
| Largest Linux runner | 32 vCPU | 64 vCPU, x64 and arm64, plus Docker builder runners |
| Config change | The runs-on label | The runs-on label |
What the extras cost in a month
Take a team that keeps 150 GB of Docker layer cache and allowlists one static IP for a database or a private registry. The minutes cost the same on both sides, so only the extras differ:
Blacksmith
$175 a month
150 GB × $0.50 = $75 for cache, plus $100 for the IP.
BuildPulse
$0 a month
150 GB is inside the 250 GB included, and the 4 fixed IPs come with every runner.
What BuildPulse adds
Flaky test detection included
Every run is parsed for flaky tests and per-test timing, with quarantine and Jira-linked triage. No second tool, no separate bill.
CircleCI and Semaphore too
The same machines and per-minute prices run CircleCI jobs through a self-hosted runner and Semaphore jobs through a self-hosted agent, so one vendor covers every pipeline.
Bigger runners when you need them
Sizes from 2 to 64 vCPU on x64 and arm64, plus Docker builder runners that keep layers between builds.
What's supported: Linux x64 and arm64 runners on Ubuntu 24.04 with Docker, for GitHub Actions, CircleCI and Semaphore.
FAQ
Is BuildPulse cheaper per minute than Blacksmith?
The list price per minute is the same at 2 vCPU: $0.004 on x64 and $0.0025 on arm64. The difference is the rest of the invoice. BuildPulse includes 250 GB of cache storage and 4 fixed egress IPs, and flaky test detection comes with every run.
How fast are BuildPulse runners compared with Blacksmith’s?
We have not benchmarked Blacksmith’s runners, so this page makes no claim about their speed. Our published benchmark is against GitHub-hosted runners, and the repository is public if you want to add a lane for any other vendor.
How do I switch from Blacksmith?
Change the runs-on label on a job, for example from blacksmith-4vcpu-ubuntu-2404 to bp-ubuntu-latest-x64-4x. Your steps, secrets and matrix stay as they are. If a workflow uses Blacksmith’s own actions for caching or Docker builds, swap them for the standard actions. Run both for a day and keep whichever is faster on your repository.
Do I get free minutes?
Yes. Every account gets 3,000 base minutes a month, at every size, with no credit card to start.
Our speed numbers against GitHub-hosted runners are in the GitHub Actions benchmark and github.com/buildpulse/runner-benchmarks; the full comparison is BuildPulse vs GitHub-hosted runners.
Blacksmith prices from Blacksmith's pricing page and sizes from its instance types page, checked November 19, 2026. BuildPulse prices are the same ones on /pricing.
Run both for a day
Point one workflow at a BuildPulse label and keep whichever is faster on your repository. Nothing else in your workflow moves.
3,000 free minutes every month · No credit card required