Blacksmith vs CRACI
Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. CRACI suits teams on GitHub Actions that want European-hosted Linux runners with per-job SBOMs and network egress policy. Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; CRACI is a managed service hosted by the vendor for GitHub Actions, priced at €0.004/min.
Key differences between Blacksmith and CRACI
- Operating systems: Only Blacksmith documents macOS and Windows.
- Isolation: Blacksmith: Firecracker microVM. CRACI: Per-job VM.
- Published price: $0.004/min (Blacksmith) versus €0.004/min (CRACI).
- Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 32 vCPU / 96 GB (CRACI).
- Company headquarters: Blacksmith Software Inc. is based in San Francisco, United States; CRACI Corporation Oy is based in Helsinki, Finland.
What they have in common
- Both are managed services hosted by the vendor.
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both document arm64 runners.
- Neither is open source.
Blacksmith vs CRACI at a glance
| Attribute | Blacksmith | CRACI |
|---|---|---|
| What it is | Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners. | Managed Linux runners for GitHub Actions on European bare metal that record a build-time SBOM and apply an egress policy to each job. |
| Type | Managed runner service | Managed runner service |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| 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 | Each job runs in its own isolated virtual machine on bare-metal infrastructure; the hypervisor is not named |
| Fresh environment per job | Yes | Not documented |
| 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. | European bare-metal infrastructure in data centers in Finland and Sweden; CPU models are not published. |
| 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) | CRACI says jobs run twice as fast as on GitHub-hosted runners (vendor claim) |
| 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 | Any size from 1 to 32 vCPU with 3 GiB of memory per vCPU on Starter (default 2 vCPU / 6 GiB); up to 64 vCPU on Secure and Enterprise |
| 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. | Autocaching for common public packages is included, with private sources on the Secure plan. Other cache features are not documented; the docs note that an SBOM may be incomplete when a job restores dependencies from a cache. |
| Docker layer caching | Yes | Not documented |
| GPU | Not documented | Not documented |
| Concurrency | Blacksmith documents no limit on concurrent jobs or vCPUs | No limit on parallel jobs on any plan; while running on free credits, jobs can use 8 vCPUs in total at a time |
| Static IPs | Yes | Not documented |
| SSH into running jobs | Yes | Not documented |
| 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. | €0.002 per vCPU-minute, billed by the second, at the same rate on x86-64 and ARM64: €0.004/min (2 vCPU / 6 GB), €0.008 (4 vCPU), €0.016 (8 vCPU), €0.032 (16 vCPU), €0.064 (32 vCPU). Starter has no platform fee; Secure is €2,000/month plus usage with 10% off compute. |
| 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 | €10 of free credit on the Starter plan, with no card needed |
| Open source | No | No |
| Self-host / your cloud | No / Not documented | No / Not documented |
| Compliance | SOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progress | ISO/IEC 27001 (certificate issued by Into Certification) |
| Regions | us-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting support | Data centers in Finland and Sweden |
| Company headquarters | San Francisco, California, United States | Helsinki, Finland |
| Good fit for | Teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability | Teams on GitHub Actions that want European-hosted Linux runners with per-job SBOMs and network egress policy |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Blacksmith
- 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
Reasons to choose CRACI
- You need CI jobs to run on bare-metal infrastructure in Finland and Sweden
- You want an SBOM and network trace recorded for every job without adding workflow steps
- You want to restrict outbound network access from jobs with a policy checked before the job starts
- You want x86-64 and ARM64 runners at the same per-vCPU rate, with no limit on parallel jobs
Trade-offs to check first
- Blacksmith: Available to GitHub organizations only, not personal repositories
- Blacksmith: Windows runners are in public beta and do not support Docker Linux containers
- CRACI: Runs Linux jobs only; macOS and Windows jobs stay on other runners (quickstart)
- CRACI: GitHub Actions is the only CI system supported today
Run your slowest workflow on both before deciding. See the full Blacksmith profile and CRACI profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Blacksmith or CRACI better?
What is the difference between Blacksmith and CRACI?
Which is open source, Blacksmith or CRACI?
How do Blacksmith and CRACI isolate jobs?
How does Blacksmith pricing compare with CRACI?
Is Blacksmith or CRACI faster?
Do Blacksmith and CRACI cache Docker layers?
Where do Blacksmith and CRACI runners run?
Sources
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 vs CRACI. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/blacksmith-vs-craci/