Blacksmith vs Ubicloud Runners
Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. Ubicloud Runners suits teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source. Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; Ubicloud Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.00125/min.
Key differences between Blacksmith and Ubicloud Runners
- Operating systems: Only Blacksmith documents macOS and Windows.
- Isolation: Blacksmith: Firecracker microVM. Ubicloud Runners: KVM VM.
- Published price: $0.004/min (Blacksmith) versus $0.00125/min (Ubicloud Runners).
- Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 30 vCPU / 120 GB (Ubicloud Runners).
- Open source: Ubicloud Runners is open source (AGPL-3.0); Blacksmith is not.
- Self-hosting: Ubicloud Runners documents a self-hosted option; Blacksmith does not.
What they have in common
- Both companies are based in the United States.
- Both are managed services hosted by the vendor.
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both document arm64 runners.
- Both give every job a fresh environment.
- Both document Docker layer caching.
Blacksmith vs Ubicloud Runners at a glance
| Attribute | Blacksmith | Ubicloud Runners |
|---|---|---|
| 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 from an open-source cloud platform that runs on leased bare metal. |
| 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 a fresh virtual machine provisioned with Linux KVM, using Cloud Hypervisor as the virtual machine monitor; the VM and its block storage are destroyed when the job finishes |
| Fresh environment per job | Yes | 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. | Standard x64 runners use AMD EPYC 9454P (two vCPUs per physical core), premium x64 runners use AMD Ryzen 9 7950X3D, and arm64 runners use Ampere Altra Q80-30 with one physical core per vCPU; all have NVMe SSDs. |
| 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) | Ubicloud says premium runners are around 2x faster on CPU-heavy workflows and that its cache gives 4x faster downloads and 3x faster uploads (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 | 2 to 30 vCPU with 8 to 120 GB RAM on x64; 2 to 30 vCPU with 6 to 90 GB on arm64 |
| 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. | A transparent cache backend serves actions/cache, setup-* package caching and Docker layer caching through type=gha without workflow changes. Each repository gets 30 GB free (100 GB with premium runners enabled), entries unused for seven days are removed, and extra storage is $0.04 per GB per month on request. |
| Docker layer caching | Yes | Yes |
| GPU | Not documented | Not documented |
| Concurrency | Blacksmith documents no limit on concurrent jobs or vCPUs | Not documented |
| Static IPs | Yes | Not documented |
| SSH into running jobs | Yes | Yes |
| 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. | Standard x64 per minute: $0.00125 (2 vCPU), $0.0025 (4), $0.005 (8), $0.01 (16) and $0.01875 (30 vCPU). Premium x64: $0.002 (2 vCPU) to $0.03 (30 vCPU). arm64 is priced the same as standard x64. Billing is per minute, and new users get premium runners by default with fallback to standard runners when premium capacity is full. |
| 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 | $2.5/month credit, which Ubicloud equates to 1,250 runner minutes |
| Open source | No | Yes (AGPL-3.0) |
| Self-host / your cloud | No / Not documented | Yes / Not documented |
| Compliance | SOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progress | SOC 2 Type 2 report available through the Trust Center; GDPR data processing agreement offered |
| Regions | us-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting support | Europe by default: Hetzner (Falkenstein, Germany) as the primary fleet and Leaseweb (Frankfurt), with AWS eu-central-1 as overflow; US runners are used only on explicit request |
| Company headquarters | San Francisco, California, United States | San Francisco, California, United States |
| 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 low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source |
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 Ubicloud Runners
- You want Linux runners at $0.00125 per minute for 2 vCPU, on x64 or arm64
- You want the underlying cloud platform to be open source and self-hostable
- You need jobs to run in European data centers by default
- You want existing actions/cache and type=gha Docker layer caching to work without workflow changes
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
- Ubicloud Runners: Windows and macOS runners are not documented
- Ubicloud Runners: Runner prices were raised twice in 2026, in May and September
Run your slowest workflow on both before deciding. See the full Blacksmith profile and Ubicloud Runners profile, or the complete comparison.
More comparisons
- Blacksmith vs Depot GitHub Actions Runners
- Blacksmith vs GitHub-hosted runners
- Blacksmith vs Luxor Runners
- Blacksmith vs Namespace
- Blacksmith vs WarpBuild
- Avrea vs Blacksmith
- Blacksmith vs BuildPulse Runners
- Blacksmith vs CRACI
- Depot GitHub Actions Runners vs Ubicloud Runners
- GitHub-hosted runners vs Ubicloud Runners
- Namespace vs Ubicloud Runners
- TestFlows GitHub Hetzner Runners vs Ubicloud Runners
- Ubicloud Runners vs WarpBuild
Frequently asked questions
Is Blacksmith or Ubicloud Runners better?
What is the difference between Blacksmith and Ubicloud Runners?
Which is open source, Blacksmith or Ubicloud Runners?
How do Blacksmith and Ubicloud Runners isolate jobs?
How does Blacksmith pricing compare with Ubicloud Runners?
Is Blacksmith or Ubicloud Runners faster?
Do Blacksmith and Ubicloud Runners cache Docker layers?
Where do Blacksmith and Ubicloud Runners 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 Ubicloud Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/blacksmith-vs-ubicloud/