Blacksmith review

Blacksmith is a managed replacement for GitHub Actions runners: your workflows still run through GitHub Actions, but jobs use Blacksmith’s infrastructure. The product says you can switch by setting runs-on: ubuntu-latest, rather than rebuilding your CI setup around a different platform.

Blacksmith’s homepage says its runners use bare-metal gaming CPUs and are faster and cheaper than GitHub’s runners. It also advertises cache downloads up to 4× faster and Docker builds up to 40× faster. Those are vendor claims, not independent benchmarks in the material we reviewed.

Beyond running jobs, Blacksmith provides CI observability for finding slow or failing jobs and searching CI logs. It can also post failed-test logs as a comment on a GitHub pull request. The basic proposition is straightforward: keep GitHub Actions, change where the jobs run, and add tools for inspecting CI failures.

The appeal is a relatively small migration paired with published per-minute rates. The pricing page lists four runner types, each with 3,000 free minutes per month:

• Ubuntu x64: $0.004 per minute; general-purpose workloads.
• Ubuntu ARM: $0.0025 per minute; ARM-compatible workloads.
• Windows x64: $0.008 per minute.
• macOS M4: $0.08 per minute.

Each listed runner includes GitHub Actions observability, and the pricing page advertises 2× faster hardware and 4× faster cache downloads. The homepage separately claims 40× faster Docker builds with layer caching. That caching is an add-on at $0.50 per GB per month, so it is not included in the runner rate.

The observability and pull-request test logs could help teams locate a slow or broken job without changing CI providers. Static IPs and sticky disks are also available as paid add-ons. For enterprises, Blacksmith lists a custom plan with a 99.9% SLA, 24/7 priority support, a dedicated Slack channel, white-glove onboarding, and enterprise-grade concurrency.

The speed story needs a caveat: Blacksmith’s homepage claims faster builds and cache downloads, but the published material includes no independent benchmark or measured comparison with GitHub-hosted runners. The pricing page’s 2× hardware and 4× cache figures are also vendor claims. Teams should model their own workloads before assuming a migration will reduce build time or total spend.

Costs are usage-based, not a fixed monthly subscription. Each runner includes 3,000 free minutes per month, then the listed rates apply; annual billing is not listed. Docker layer caching costs an extra $0.50 per GB per month, sticky disks cost the same, and static IPs are $100 per IP per month. Those add-ons can change the bill, particularly for teams with large caches or multiple fixed IPs.

The pricing material does not publish a concurrency cap for standard plans, a monthly spend estimate, or a direct cost comparison with GitHub. Enterprise concurrency is described as a feature, but its price is custom. So Blacksmith gives buyers clear rates, but not enough published detail to forecast every team’s bill or verify the savings claim.

The pricing page lists per-minute rates, not flat monthly plans: Ubuntu ARM is $0.0025/minute, Ubuntu x64 $0.004, Windows x64 $0.008 and macOS M4 $0.08. That makes macOS 20 times the ARM rate; switching workloads between runner types can change your bill quickly. Each runner includes 3,000 free minutes per month, according to the pricing details. Check how that allowance applies to your setup before estimating costs. The listed rates are usage charges, and annual billing is not published.

Docker layer caching and sticky disks each add $0.50/GB/month; static IPs add $100/IP/month. Enterprise pricing is custom and includes a 99.9% SLA, 24/7 priority support, a dedicated Slack channel, white-glove onboarding and enterprise-grade concurrency. The pricing page does not list a flat monthly price for any runner tier. Blacksmith’s speed and cache improvements are vendor claims, not independently verified figures.

Blacksmith is designed as a GitHub Actions runner replacement: the product says jobs can use runs-on: ubuntu-latest. That suggests a narrower change than moving to a different CI platform, but the published material does not document migration steps, compatibility limits or a rollback process. Check your workflows and runner requirements before switching.

The product runs jobs on Blacksmith infrastructure and provides CI observability, including search across CI logs and inline failed-test logs in GitHub pull requests. The published material does not say how to export logs, cache artifacts or other data, or how long they remain available. Treat data portability and retention as questions to resolve before committing.

We don’t have Reddit posts or comments in the published published material, so we can’t report why users leave Blacksmith based on Reddit. The pricing details do identify practical reasons to reassess: no published flat monthly runner price, usage-based billing, and paid add-ons for Docker layer caching, sticky disks and static IPs.