Blacksmith vs Namespace
Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. Namespace suits teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; Namespace is a managed service hosted by the vendor for GitHub Actions and Buildkite, priced at $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB).
Key differences between Blacksmith and Namespace
- CI systems: Only Namespace documents Buildkite.
- Isolation: Blacksmith: Firecracker microVM. Namespace: Virtual machine.
- Published price: $0.004/min (Blacksmith) versus $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) (Namespace).
- Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 64 vCPU / 512 GB (Namespace).
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.
Blacksmith vs Namespace at a glance
| Attribute | Blacksmith | Namespace |
|---|---|---|
| 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 runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. |
| Type | Managed runner service | Managed runner service |
| CI systems | GitHub Actions | GitHub Actions, Buildkite |
| Operating systems | Linux, macOS, Windows | Linux, macOS, Windows |
| 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 | Every job runs in its own instance inside a virtual machine that is discarded when the job ends; the hypervisor is not named |
| 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. | Namespace says it deploys its own hardware in its own racks: AMD EPYC for Linux and Windows amd64, AmpereOne for Linux arm64 (Linux on Apple Silicon is in early access), and Apple M4 Pro and M5 Max for macOS. |
| 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) | Not documented |
| 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 | Linux up to 64 vCPU and 512 GB RAM, Windows up to 32 vCPU and 512 GB, macOS up to 16 vCPU and 56 GB; standard label shapes run from 2 vCPU / 4 GB to 32 vCPU / 64 GB, and instances over 64 GB RAM need special access |
| 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. | Cache Volumes persist data across runs; a runner profile can cache container images, toolchain downloads, action downloads and Git checkouts, and nscloud-cache-action replaces actions/cache. Docker builds go to Remote Builders with layer caching by default, and there are cache integrations for Bazel, Turborepo, Pants and Moonrepo. |
| Docker layer caching | Yes | Yes |
| GPU | Not documented | Not documented |
| Concurrency | Blacksmith documents no limit on concurrent jobs or vCPUs | Per plan: Developer 32 Linux vCPU and 12 macOS vCPU; Team 64 Linux, 24 macOS and 32 Windows vCPU; Business 160 Linux, 48 macOS and 80 Windows vCPU; custom on Enterprise |
| Static IPs | Yes | Yes |
| 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. | Billed in unit minutes (vCPU × minutes × platform multiplier: Linux 1, Windows 2, macOS 10), with a 1-minute minimum. Team is $100/month with 100,000 unit minutes and Business $250/month with 250,000; Developer is pay as you go. A 2 vCPU / 4 GB Linux runner is listed at $0.002/min prepaid and $0.003/min overage, 2 vCPU / 8 GB at $0.004 and $0.006, and macOS 6 vCPU / 14 GB at $0.06 and $0.09. Cache volume storage is $0.0048/GB-day on Developer, with free allowances on Team and Business. |
| 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 | 30-day free trial of Developer plan features, no credit card required |
| 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 | SOC 2 Type II |
| Regions | us-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting support | Specific regions are not named; Namespace says it runs its own hardware at multiple sites, offers a regional preference on all plans and region-exclusive residency on enterprise plans |
| Company headquarters | San Francisco, California, United States | Not documented |
| 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 or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes |
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 Namespace
- You want each job in its own virtual machine that is discarded when the job ends
- You want cache volumes that persist container images, toolchains, action downloads and Git checkouts between runs
- You need Linux, macOS and Windows runners, with Linux shapes up to 64 vCPU and 512 GB RAM
- You run Buildkite as well as GitHub Actions and want one provider for both
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
- Namespace: Concurrency is capped per plan, for example 32 Linux vCPU on Developer and 64 on Team
- Namespace: Maximum instance duration is 3 hours on Developer and 5 hours on Team
Run your slowest workflow on both before deciding. See the full Blacksmith profile and Namespace profile, or the complete comparison.
More comparisons
- Blacksmith vs Depot GitHub Actions Runners
- Blacksmith vs GitHub-hosted runners
- Blacksmith vs Luxor Runners
- Blacksmith vs Ubicloud Runners
- Blacksmith vs WarpBuild
- Avrea vs Blacksmith
- Blacksmith vs BuildPulse Runners
- Blacksmith vs CRACI
- Depot GitHub Actions Runners vs Namespace
- GitHub-hosted runners vs Namespace
- Namespace vs Ubicloud Runners
- Namespace vs WarpBuild
Frequently asked questions
Is Blacksmith or Namespace better?
What is the difference between Blacksmith and Namespace?
Which is open source, Blacksmith or Namespace?
How do Blacksmith and Namespace isolate jobs?
How does Blacksmith pricing compare with Namespace?
Is Blacksmith or Namespace faster?
Do Blacksmith and Namespace cache Docker layers?
Where do Blacksmith and Namespace 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 Namespace. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/blacksmith-vs-namespace/