GitHub-hosted runners vs Namespace
GitHub-hosted runners suits teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. 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. GitHub-hosted runners is the CI platform’s own hosted runners for GitHub Actions, priced at $0.006/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 GitHub-hosted runners and Namespace
- Type: GitHub-hosted runners is the CI platform’s own hosted runners; Namespace is a managed service hosted by the vendor.
- CI systems: Only Namespace documents Buildkite.
- Isolation: GitHub-hosted runners: Fresh VM. Namespace: Virtual machine.
- Published price: $0.006/min (GitHub-hosted runners) versus $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) (Namespace).
- Largest runner: 96 vCPU / 384 GB (GitHub-hosted runners) versus 64 vCPU / 512 GB (Namespace).
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux, macOS and Windows runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Neither is open source.
GitHub-hosted runners vs Namespace at a glance
| Attribute | GitHub-hosted runners | Namespace |
|---|---|---|
| What it is | GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute. | Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. |
| Type | First-party hosted runners | 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 job runs in a new virtual machine hosted by GitHub; the 1-vCPU ubuntu-slim runner instead runs in an unprivileged container on a shared VM | 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 | Azure virtual machines, with eligible 2-core and 4-core Linux jobs also scheduled on AWS; standard macOS runners are 3-core M1 or 4-core Intel, and the macOS XLarge runner is a 5-core M2 | 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) | Not documented | Not documented |
| Runner sizes | Standard: 1 vCPU / 5 GB (ubuntu-slim); 2 vCPU / 8 GB in private and 4 vCPU / 16 GB in public repositories on Linux and Windows, x64 and arm64. Larger runners: 2 to 96 vCPU on x64 and 2 to 64 vCPU on arm64; macOS 3 to 12 cores | 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 | Dependency caching through the cache action, with 10 GB per repository included; entries not accessed for 7 days are removed and the oldest are evicted at the limit. The limit can be raised, billed at $0.07 per GB per month. Larger runners can use custom VM images. | 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 | Not documented | Yes |
| GPU | GPU larger runners have 4 vCPU, 28 GB RAM and one Tesla T4 with 16 GB VRAM, at $0.052/min on Linux and $0.102/min on Windows. | Not documented |
| Concurrency | Standard runners: 20 concurrent jobs on Free, 40 on Pro, 60 on Team and 500 on Enterprise, of which 5 macOS (50 on Enterprise). Larger runners: up to 1,000 concurrent jobs and 100 GPU jobs | 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 | Not documented | Yes |
| Pricing | Private repositories, per minute: Linux 2-core x64 $0.006, Linux 2-core arm64 $0.005, Linux 1-core $0.002, Windows 2-core $0.010, macOS 3- or 4-core $0.062. Larger Linux x64 runners run from $0.012 (4-core) to $0.252 (96-core); larger macOS runners are $0.077 (12-core Intel) and $0.102 (M2 Pro). Usage is rounded up to the whole minute. | 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 | Standard runners are free in public repositories. Private repositories get $12 of included compute usage per month on GitHub Free, $18 on Pro and Team, and $300 on Enterprise Cloud | 30-day free trial of Developer plan features, no credit card required |
| Open source | No | No |
| Self-host / your cloud | No / No | No / Not documented |
| Compliance | Not documented | SOC 2 Type II |
| Regions | Regions are not documented for github.com. GitHub says Windows runners and other Linux runners run on Microsoft Azure, eligible Linux jobs on Azure or AWS, and macOS runners in Azure data centers | 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 runners with no setup, and public repositories that can use the free standard runners | 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 GitHub-hosted runners
- You want runners that need no installation or account beyond GitHub itself
- You maintain public repositories, where standard runners are free
- You need Linux, Windows and macOS, on x64 and arm64, from one provider
- You want every job to start in a clean VM that is not reused
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
- GitHub-hosted runners: Larger runners are billed in public repositories and need a GitHub Team or Enterprise Cloud plan
- GitHub-hosted runners: Jobs are limited to 6 hours of execution time
- 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 GitHub-hosted runners profile and Namespace profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs GitHub-hosted runners
- Blacksmith vs GitHub-hosted runners
- Depot GitHub Actions Runners vs GitHub-hosted runners
- GitHub-hosted runners vs GitLab-hosted runners
- GitHub-hosted runners vs Ubicloud Runners
- GitHub-hosted runners vs WarpBuild
- Blacksmith vs Namespace
- Depot GitHub Actions Runners vs Namespace
- Namespace vs Ubicloud Runners
- Namespace vs WarpBuild
Frequently asked questions
Is GitHub-hosted runners or Namespace better?
What is the difference between GitHub-hosted runners and Namespace?
Which is open source, GitHub-hosted runners or Namespace?
How do GitHub-hosted runners and Namespace isolate jobs?
How does GitHub-hosted runners pricing compare with Namespace?
Do GitHub-hosted runners and Namespace cache Docker layers?
Do GitHub-hosted runners and Namespace offer GPU runners?
Where do GitHub-hosted runners and Namespace runners run?
Sources
- docs.github.com/en/billing/reference/actions-runner-pricing
- docs.github.com/en/billing/concepts/product-billing/github-actions
- docs.github.com/en/actions/reference/runners/github-hosted-runners
- docs.github.com/en/actions/reference/runners/larger-runners
- namespace.so/
- namespace.so/pricing
- namespace.so/docs/solutions/github-actions
- namespace.so/docs/reference/github-actions/runner-configuration
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). GitHub-hosted runners vs Namespace. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/github-hosted-runners-vs-namespace/