Blacksmith alternatives

We build CRACI, so weigh that in; we describe every option from its own documentation and say when another tool fits better.

Why teams look for alternatives

Blacksmith is a managed runner service for GitHub Actions, focused on speed and cost. Jobs run in Firecracker microVMs on Ubuntu x64 and ARM from 2 to 32 vCPU, with Windows in public beta and macOS on Apple M4. A colocated cache works with the standard cache actions, sticky disks provide Docker layer caching, and SSH access, metrics and test analytics help with debugging. Blacksmith states it is SOC 2 Type 2 compliant. As of September 2026, 2 vCPU x64 costs $0.004 per minute and ARM $0.0025, with 3,000 free minutes a month.

That is a strong offer. The reasons to compare are about fit:

• Size. Some builds want more than 32 vCPU on a single machine.
• Location. You want runners in your own cloud account, which the Blacksmith pages we cite do not describe.
• Network control. Blacksmith offers static IPs for allowlisting ($100 per IP per month). You may want a policy that limits what a job can reach.
• Evidence. SBOMs and signed provenance are not among Blacksmith's documented features, and a customer or regulation may ask for them.
• Platform maturity. You need Windows runners that are generally available today.

What to look for

• Price per vCPU-minute on x64 and ARM, memory per vCPU, and how usage is rounded.
• The largest machine you need, and which operating systems.
• Dependency, Docker layer and build tool caching.
• Whether runners can live in your cloud account.
• Egress control, SBOMs and provenance.
• The compliance reports your procurement asks for.

The options

CRACI (our product)

Switching to CRACI is the same kind of change as switching to Blacksmith: install a GitHub App and change the label to runs-on: craci. Billing is €0.002 per vCPU-minute, metered per second, so 2 vCPU costs €0.004 per minute on x86-64 and on ARM64. The x64 list price is the same number as Blacksmith's in a different currency, and Blacksmith's ARM price is lower. What differs is what the runner records: each job produces an SBOM of what it fetched, with a completeness state, runs under an egress policy that fails closed, and produces signed provenance. CRACI then monitors those SBOMs and exports reports.

Best for: teams that want supply chain security handled by the CI itself, for Linux builds of software where you must show what went into each release.

Consider if: you want security built into the runner, not only speed. Like Blacksmith, CRACI runs builds about twice as fast as GitHub-hosted runners. CRACI is Linux only and does not hold a SOC 2 report; its Trust Center documents policies and controls.

CRACI vs Blacksmith

Depot

Depot offers fast runners and caching, plus build services. Linux runners go up to 64 vCPUs, alongside Windows and macOS. depot build runs Docker builds on remote BuildKit hosts with a persistent NVMe cache, and a remote cache serves Bazel, Gradle, Turborepo and sccache. Linux runners support egress allow and deny rules, and on the Business plan Depot Managed runs the data plane in your own AWS account. As of September 2026, the Developer plan is $20 per month with 2,000 minutes, and 2 vCPU costs $0.006 per minute beyond that, tracked per second.

Best for: teams where Docker image builds dominate CI time.

Consider if: you need 64 vCPU runners or runners in your AWS account.

CRACI vs Depot

Namespace

Namespace runs Linux, Windows and macOS runners on hardware it operates, with Linux shapes up to 64 vCPUs. Cache volumes keep data on local storage between runs, and it offers Docker build caching and Bazel remote execution. Its egress policies block anything not allowed, or run in advisory mode first so you can build an allowlist from real traffic. As of September 2026, a 2 vCPU, 4 GB Linux runner costs $0.002 per minute in plan, and Team is $100 per month with 100,000 unit minutes. Usage has a one-minute minimum per job.

Best for: teams that want egress policy and fast caching from the same runner vendor.

Consider if: you also want Bazel remote execution or cloud dev environments.

CRACI vs Namespace

WarpBuild

WarpBuild lists the same x86-64 price as Blacksmith: $0.004 per minute for 2 vCPU, and $0.003 on arm64, as of September 2026. It offers Windows Server 2022 and 2025, macOS on Apple M4 Pro, container-layer caching and snapshot runners. Its bring-your-own-cloud option runs the same runners in your AWS, GCP or Azure account for $0.002 per minute plus your cloud bill. For enterprises it lists SAML SSO, SCIM and a 99.9% uptime SLA.

Best for: managed runners inside your own cloud account.

Consider if: you run GitHub Enterprise Server, which WarpBuild supports.

CRACI vs WarpBuild

GitHub larger runners

Staying with GitHub is a real alternative. Larger runners go up to 64 cores and add static IP addresses and Azure private networking. GitHub also offers artifact attestations, which it states provide SLSA v1.0 Build Level 2 (Level 3 with reusable workflows). The trade-off is price: as of September 2026 a 32-core larger runner is $0.082 per minute on x64 and $0.050 on arm64, and larger runners cannot use your plan's included minutes.

Best for: teams that want one vendor and a documented SLSA level.

Consider if: you already route builds through Azure networking.

CRACI vs GitHub-hosted runners

Self-hosted runners

You can run the GitHub Actions runner on your own machines, or on Kubernetes with Actions Runner Controller, which scales runner scale sets with the number of workflows running. GitHub does not charge per minute for self-hosted usage as of September 2026. You pay for the hosts, busy or idle, and you are responsible for patching, isolation and hardening; GitHub warns that self-hosted runners should almost never be used for public repositories.

Best for: jobs that must run inside your network or on your own hardware.

Consider if: you have spare capacity and the time to maintain it.

Managed vs self-hosted runners

Side by side

"Not stated" means we could not confirm it in the vendor's public pages. For the wider field, including StepSecurity Harden-Runner, see GitHub-hosted runner alternatives.

When to stay with Blacksmith

• Speed and cost are your goals, and Blacksmith's figures hold up on your own pipeline.
• You rely on sticky disks specifically, or SSH into running jobs.
• You want Linux, Windows and macOS from one runner vendor with a low ARM price.
• Your procurement needs a SOC 2 Type 2 vendor today.

Mixing is normal, since the runner is chosen per job. Read more about CI/CD integration and CRACI pricing.