Blacksmith
Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners. A managed GitHub Actions runner service on vendor-owned bare metal with microVM isolation, suited to organizations that want faster hardware plus integrated caching and observability.
Overview
Blacksmith is a managed replacement for GitHub-hosted runners. After installing its GitHub App on an organization, a team changes the runs-on label and jobs run on Blacksmith’s own fleet of bare-metal machines in the US and EU. Linux and Windows jobs each get a Firecracker microVM that is destroyed when the job ends. Runner images follow GitHub’s official images, and sizes range from 2 to 32 vCPU on Linux and Windows, with 6 and 12 vCPU Apple M4 macOS runners.
The service pairs compute with caching and tooling: standard cache actions are redirected to a co-located cache, Docker layers persist on NVMe-backed sticky disks, and a console provides logs, metrics, test analytics and SSH access to running jobs. Blacksmith documents no concurrency limits and offers four regions. The fleet is multi-tenant on shared hardware. It is available to GitHub organizations only, with GitHub Enterprise Server and data-residency setups arranged through support.
Notable
- Blacksmith announced a Series C led by Sequoia Capital at a $1B valuation on 21 October 2026, bringing total funding to $125M.
- A $45M Series B led by Peak XV Partners was announced on 12 August 2026; Blacksmith says the round closed in March 2026.
- Blacksmith published a post on building its macOS runners on 16 April 2026.
Blacksmith specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux, macOS, Windows |
| Architectures | x64, arm64 |
| Deployment | Managed runner service |
| Isolation | 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 |
| Fresh environment per job | Yes |
| Hardware | Blacksmith 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. |
| 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) |
| Runner sizes | 2 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 macOS |
| Caching | 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. |
| Docker layer caching | Yes |
| GPU | Not documented |
| Concurrency | Blacksmith documents no limit on concurrent jobs or vCPUs |
| Job limits | Not documented |
| Static IPs | Yes |
| SSH into running jobs | Yes |
| Observability | Console with run history, searchable logs, metrics, monitors, test analytics and CI analytics. |
| Setup | Install the Blacksmith GitHub App on a GitHub organization, then change runs-on in each workflow by hand or with the Migration Wizard. Personal repositories are not supported. |
| Example label | blacksmith-4vcpu-ubuntu-2404 |
| Pricing | 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. |
| Free tier | 3,000 free minutes per organization per month, counted as x64 2-vCPU minutes; larger, ARM, Windows and macOS runners consume them at weighted rates |
| Compliance | SOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progress |
| Regions | us-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting support |
| Open source | No |
| Company headquarters | San Francisco, California, United States · More from the United States |
Facts from Blacksmith’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- 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
- You need Linux, Windows and macOS runners from one vendor, with a 3,000-minute monthly free allowance
Trade-offs
- Available to GitHub organizations only, not personal repositories
- Windows runners are in public beta and do not support Docker Linux containers
- KVM and nested virtualization are supported on x64 Linux only, not ARM
- Docker layer caching and sticky disks are billed separately at $0.50/GB/month
Good fit for: Teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability.
Use cases Blacksmith fits
- Faster builds: Blacksmith runs jobs on bare-metal gaming CPUs with a co-located cache and says most CI jobs run about 2x faster (vendor claim).
- Lower CI cost: Listed rates start at $0.004/min for Ubuntu x64, which Blacksmith says is half of GitHub’s per-minute rate, with 3,000 free minutes per month.
- Docker builds: Docker layers persist across runs on NVMe-backed sticky disks through Blacksmith’s Docker builder actions.
- ARM64 builds: Native arm64 Linux runners from 2 to 32 vCPU are listed at $0.0025/min.
- macOS and iOS builds: Apple M4 macOS runners with 6 or 12 vCPU are available with macOS 15, 26 and 27 images.
- Windows builds: Windows Server 2025 x64 runners from 2 to 32 vCPU are offered in public beta.
How Blacksmith compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
| 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 |
| 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 |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| Luxor Runners | GitHub Actions | Linux, macOS, x64, arm64 | Vendor-hosted | Single-use VM | $0.004/min | 16 vCPU / 32 GB | Not documented | Not documented | No | 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 Depot GitHub Actions Runners · Blacksmith vs GitHub-hosted runners · Blacksmith vs Luxor Runners · Blacksmith vs Namespace · Blacksmith vs Ubicloud Runners · Blacksmith vs WarpBuild · Avrea vs Blacksmith · Blacksmith vs BuildPulse Runners · Blacksmith vs CRACI
Frequently asked questions
What is Blacksmith?
Which CI systems does Blacksmith work with?
How does Blacksmith isolate jobs?
Is Blacksmith open source?
How much does Blacksmith cost?
How do I switch from GitHub-hosted runners to Blacksmith?
blacksmith-4vcpu-ubuntu-2404.How fast is Blacksmith?
Does Blacksmith have a free tier?
Does Blacksmith support ARM64 runners?
Does Blacksmith offer macOS runners?
Does Blacksmith cache Docker layers?
How many jobs can run at once on Blacksmith?
Where do Blacksmith runners run?
What compliance certifications does Blacksmith have?
Where is Blacksmith Software Inc. based?
What are the alternatives to Blacksmith?
Sources
- blacksmith.sh/
- blacksmith.sh/pricing
- blacksmith.sh/security
- docs.blacksmith.sh/blacksmith-runners/overview
- docs.blacksmith.sh/blacksmith-runners/concurrency
- docs.blacksmith.sh/blacksmith-runners/static-ip
- docs.blacksmith.sh/blacksmith-caching/dependencies-actions
- docs.blacksmith.sh/blacksmith-caching/docker-builds
- docs.blacksmith.sh/blacksmith-observability/ssh-access
- docs.blacksmith.sh/introduction/quickstart
- docs.blacksmith.sh/introduction/github-enterprise
- docs.blacksmith.sh/about/privacy-policy
- blacksmith.sh/blog/series-c
- blacksmith.sh/blog/announcing-blacksmiths-series-b-led-by-peak-xv-partners
- blacksmith.sh/blog
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. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/blacksmith/