Avrea vs Blacksmith
Avrea suits teams on GitHub Actions that need Linux, macOS and Windows runners from one vendor, with built-in caching and SSH debugging. Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. Avrea is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min.
Key differences between Avrea and Blacksmith
- Isolation: Avrea: Per-job VM. Blacksmith: Firecracker microVM.
- Company headquarters: Avrea Oy is based in Helsinki, Finland; Blacksmith Software Inc. is based in San Francisco, United States.
What they have in common
- Both are managed services hosted by the vendor.
- Both run GitHub Actions jobs.
- Both document Linux, macOS and Windows runners.
- Both document arm64 runners.
- Both give every job a fresh environment.
- Neither is open source.
- Both document Docker layer caching.
Avrea vs Blacksmith at a glance
| Attribute | Avrea | Blacksmith |
|---|---|---|
| What it is | Managed GitHub Actions runners for Linux, macOS and Windows on dedicated hardware, with colocated caches and SSH into running jobs. | Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners. |
| Type | Managed runner service | Managed runner service |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux, macOS, Windows |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Every CI job runs in its own VM on dedicated hardware, destroyed when the job ends; the hypervisor is not named | 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 | Yes |
| Hardware | Dedicated bare-metal AMD EPYC 4585PX hosts with DDR5 memory and local NVMe storage for x86 runners; Apple M5 Max machines for macOS and ARM Linux runners. | 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) | Avrea says CI runs 2x faster on hardware alone and up to 10x faster with cache hits (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 | Linux x86: 1 vCPU / 4 GB to 32 vCPU / 128 GB; Linux ARM: 1 vCPU / 4 GB to 16 vCPU / 64 GB; macOS: 8 vCPU / 24 GB or 16 vCPU / 48 GB; Windows: 2 vCPU / 8 GB to 16 vCPU / 64 GB | 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 | Colocated caches cover the GitHub Actions cache, build outputs, package downloads, Git checkouts and LFS data, with 25 GB per repository included. Docker layers are cached by pointing BuildKit’s type=gha backend at Avrea’s cache, and optional persistent disks can keep Docker state between Linux jobs. | 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 | Yes |
| GPU | Not documented | Not documented |
| Concurrency | Caps on concurrent jobs and vCPUs depend on usage and rise as usage grows; no figures are published | Blacksmith documents no limit on concurrent jobs or vCPUs |
| Static IPs | Yes | Yes |
| SSH into running jobs | Yes | Yes |
| Pricing | Per-minute rates, billed by the second. Linux x86: $0.002 (1 vCPU / 4 GB), $0.004 (2 vCPU / 8 GB), $0.008 (4 vCPU / 16 GB), $0.016 (8 vCPU / 32 GB), $0.032 (16 vCPU), $0.064 (32 vCPU). Linux ARM from $0.006 (1 vCPU) to $0.096 (16 vCPU); macOS $0.08 (8 vCPU) and $0.16 (16 vCPU); Windows $0.008 (2 vCPU) to $0.064 (16 vCPU). Extra cache is about $0.50 per GB per month. | 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 | $12 of credit each month on the pay-as-you-go plan, which Avrea says covers 3,000 minutes on a 2-vCPU Linux x86 runner | 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 |
| Open source | No | No |
| Self-host / your cloud | No / Not documented | No / Not documented |
| Compliance | ISO/IEC 27001:2022 certified; SOC 2 Type II attested | SOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progress |
| Regions | Not documented | us-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting support |
| Company headquarters | Helsinki, Finland | San Francisco, California, United States |
| Good fit for | Teams on GitHub Actions that need Linux, macOS and Windows runners from one vendor, with built-in caching and SSH debugging | Teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Avrea
- You need Linux x86, Linux ARM, macOS and Windows runners under one account and one label scheme
- You want to SSH into a running job from a browser or CLI without changing the workflow
- You want Actions, package, Docker layer and Git caches served from storage colocated with the runners
- You need an egress firewall per organization and repository, with a record of each job’s connections
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
Trade-offs to check first
- Avrea: Runner and data center locations are not published; the trust page says to contact Avrea about data location requirements
- Avrea: Dedicated static IP egress is listed as an Enterprise feature at $100 per IP per month
- Blacksmith: Available to GitHub organizations only, not personal repositories
- Blacksmith: Windows runners are in public beta and do not support Docker Linux containers
Run your slowest workflow on both before deciding. See the full Avrea profile and Blacksmith profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Avrea or Blacksmith better?
What is the difference between Avrea and Blacksmith?
Which is open source, Avrea or Blacksmith?
How do Avrea and Blacksmith isolate jobs?
How does Avrea pricing compare with Blacksmith?
Is Avrea or Blacksmith faster?
Do Avrea and Blacksmith cache Docker layers?
Where do Avrea and Blacksmith 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). Avrea vs Blacksmith. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/avrea-vs-blacksmith/