What is Blacksmith?
Blacksmith is a drop-in replacement for GitHub-hosted runners that runs GitHub Actions CI/CD jobs on faster hardware for less cost. It requires no workflow rewrite beyond changing the runs-on value, and it adds CI observability that GitHub does not provide natively.
Key features
- Drop-in runner replacement: Blacksmith runs existing GitHub Actions workflows by swapping the runner label, so teams keep their current pipeline configuration while moving execution to Blacksmith's infrastructure.
- 2x faster hardware: Jobs run on bare metal gaming CPUs selected for the highest single-core performance, which shortens build, test, and deploy times.
- 4x faster cache downloads: Cache artifacts are co-located in the same data center as the running jobs, reducing the latency of dependency cache retrieval.
- 40x faster Docker builds: Docker layers persist across CI runs on NVMe drives, so image builds reuse prior work instead of starting cold.
- Instant microVM provisioning: Runners are provisioned as microVMs to eliminate the "Waiting for a runner to pick up this job" queue state.
- CI observability console: A console surfaces what is happening inside the pipeline when something fails, filling a gap left by GitHub.
- Failure and performance triage: The console helps spot failing and slow jobs, identify misconfigurations, and catch performance regressions.
- Log search and inline PR feedback: Global search runs across all CI logs, and failed test logs can be posted as inline comments on the pull request.
Who is it for?
Blacksmith targets engineering teams that run CI/CD on GitHub Actions and feel the cost of slow feedback loops: DevOps engineers and platform teams managing runner spend, and application developers who wait on builds and tests before merging. It addresses two problems at once, the queue times and hardware limits of GitHub-hosted runners and the operational burden of self-hosted infrastructure, while adding visibility into pipeline failures that GitHub's native tooling does not surface well.
Use cases
- Pull request feedback loops: Teams that want reviewers to see passing builds and tests sooner can cut build, test, and deploy time roughly in half so PRs merge faster.
- Docker-heavy pipelines: Projects that build container images on every run can persist Docker layers across CI runs instead of rebuilding from scratch.
- Dependency-heavy Node.js projects: Workflows with large dependency trees benefit from co-located cache artifacts and faster cache downloads.
- Cost reduction programs: Organizations looking to lower GitHub Actions spend can compare per-job compute costs against GitHub runners and consolidate on Blacksmith.
- Debugging flaky tests: Teams chasing intermittent failures can search across all CI logs and post failed test output directly to the pull request.
Pricing
Blacksmith is positioned as costing 60% less than GitHub runners, with a free starting allowance of 3,000 minutes per month and no credit card required to try it. The source does not publish per-minute rates beyond the comparison figures shown for specific job types, so exact plan pricing should be confirmed directly with Blacksmith.
What's new and trending
Blacksmith announced a Series C funding round led by Sequoia at a $1B valuation, and the company reports backing from angels including Kelsey Hightower, Spencer Kimball, and NFL athlete Kelvin Beachum. The platform reports processing more than 100M jobs weekly across 10,000+ organizations and 200K+ developers. Published customer stories include Ashby, which reports cutting GitHub Actions costs by 75% and doubling deployment frequency, and VEED, which reports deploying 2x faster while cutting GitHub Actions costs by 70%.
Getting started
Developers start by signing up for the free tier, which requires no credit card, and then pointing existing workflows at Blacksmith runners by changing the runs-on value. Blacksmith publishes documentation covering setup and the console, and teams can book a live demo with Blacksmith engineers or contact the team for migration help.
Alternatives
The source compares Blacksmith against GitHub-hosted runners and self-hosted runners, positioning Blacksmith as cheaper than GitHub and far cheaper than the true cost of self-hosting, with advantages in provisioning, concurrency, dependency caching, and Docker caching. No other third-party CI vendors are named in the source material.
FAQ
What is Blacksmith used for? Blacksmith is used to run GitHub Actions workflows on faster, lower-cost infrastructure than GitHub-hosted runners. It speeds up builds, tests, and deployments, accelerates cache and Docker layer reuse, and adds a console for observing and debugging CI pipelines.
Is Blacksmith free? Blacksmith offers a free starting allowance of 3,000 minutes per month with no credit card required. Beyond that allowance, the source states Blacksmith costs 60% less than GitHub runners but does not list full plan pricing.
How does Blacksmith speed up GitHub Actions? Blacksmith runs jobs on bare metal gaming CPUs with high single-core performance, co-locates cache artifacts with running jobs for 4x faster cache downloads, and persists Docker layers on NVMe drives for 40x faster Docker builds. It also provisions microVMs instantly to remove queue times.
Do I have to rewrite my GitHub Actions workflows to use Blacksmith? No. Blacksmith is described as a drop-in replacement, so teams keep their workflows and change the runner configuration to use Blacksmith instead of GitHub-hosted runners.
What does the Blacksmith console show? The Blacksmith console shows what is happening inside a CI pipeline when something goes wrong, helping teams spot failing and slow jobs, debug flaky tests through global log search, and post inline logs of failed tests as GitHub comments on pull requests.
