Actions Runner Controller (ARC) vs GitHub-hosted runners
Actions Runner Controller (ARC) suits teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners. GitHub-hosted runners suits teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. Actions Runner Controller (ARC) is an open-source project you run yourself for GitHub Actions; GitHub-hosted runners is the CI platform’s own hosted runners for GitHub Actions, priced at $0.006/min.
Key differences between Actions Runner Controller (ARC) and GitHub-hosted runners
- Type: Actions Runner Controller (ARC) is an open-source project you run yourself; GitHub-hosted runners is the CI platform’s own hosted runners.
- Operating systems: Only GitHub-hosted runners documents macOS.
- Isolation: Actions Runner Controller (ARC): Kubernetes pod. GitHub-hosted runners: Fresh VM.
- Open source: Actions Runner Controller (ARC) is open source (Apache-2.0); GitHub-hosted runners is not.
- Self-hosting: Actions Runner Controller (ARC) documents a self-hosted option; GitHub-hosted runners does not.
- Your own cloud account: Actions Runner Controller (ARC) documents running in your own cloud account; GitHub-hosted runners does not.
What they have in common
- Both are from GitHub, Inc..
- Both run GitHub Actions jobs.
- Both document Linux and Windows runners.
- Both give every job a fresh environment.
Actions Runner Controller (ARC) vs GitHub-hosted runners at a glance
| Attribute | Actions Runner Controller (ARC) | GitHub-hosted runners |
|---|---|---|
| What it is | Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. | GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute. |
| Type | Open-source project | First-party hosted runners |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, Windows | Linux, macOS, Windows |
| Architectures | Not documented | x64, arm64 |
| Isolation | Each runner is a pod in your Kubernetes cluster; jobs that need containers use Docker-in-Docker, which requires privileged mode, or Kubernetes mode, which starts separate job pods | 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 |
| Fresh environment per job | Yes | Yes |
| Hardware | Not documented | 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 |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | Not documented | 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 |
| Caching | Not documented | 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. |
| Docker layer caching | Not documented | Not documented |
| GPU | Not documented | 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. |
| Concurrency | Set per runner scale set with minRunners and maxRunners; with both unset, runners follow the number of assigned jobs and scale down to zero when idle | 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 |
| Static IPs | Not documented | Yes |
| SSH into running jobs | Not documented | Not documented |
| Pricing | Free and open source; you pay for the infrastructure it runs on. | 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. |
| Free tier | Not documented | 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 |
| Open source | Yes (Apache-2.0) | No |
| Self-host / your cloud | Yes / Yes | No / No |
| Compliance | Not documented | Not documented |
| Regions | Not documented | 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 |
| Company headquarters | San Francisco, California, United States | San Francisco, California, United States |
| Good fit for | Teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners | Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Actions Runner Controller (ARC)
- You already run Kubernetes and want runners managed as pods and installed with Helm
- You want the autoscaling mode that GitHub itself maintains and supports
- You want runners that scale to zero when no jobs are assigned
- You need runners at repository, organization or enterprise level, including on GitHub Enterprise Server 3.9 or later
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
Trade-offs to check first
- Actions Runner Controller (ARC): Docker-in-Docker mode requires privileged containers
- Actions Runner Controller (ARC): Helm does not manage CRD upgrades, so upgrading means uninstalling the scale sets and the controller and reinstalling them
- 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
Run your slowest workflow on both before deciding. See the full Actions Runner Controller (ARC) profile and GitHub-hosted runners profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs Actuated
- Actions Runner Controller (ARC) vs AWS CodeBuild-hosted runners
- Actions Runner Controller (ARC) vs Fireactions
- Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager)
- Actions Runner Controller (ARC) vs RunsOn
- Actions Runner Controller (ARC) vs terraform-aws-github-runner
- Blacksmith vs GitHub-hosted runners
- Depot GitHub Actions Runners vs GitHub-hosted runners
- GitHub-hosted runners vs GitLab-hosted runners
- GitHub-hosted runners vs Namespace
- GitHub-hosted runners vs Ubicloud Runners
- GitHub-hosted runners vs WarpBuild
Frequently asked questions
Is Actions Runner Controller (ARC) or GitHub-hosted runners better?
What is the difference between Actions Runner Controller (ARC) and GitHub-hosted runners?
Which is open source, Actions Runner Controller (ARC) or GitHub-hosted runners?
How do Actions Runner Controller (ARC) and GitHub-hosted runners isolate jobs?
How does Actions Runner Controller (ARC) pricing compare with GitHub-hosted runners?
Do Actions Runner Controller (ARC) and GitHub-hosted runners offer GPU runners?
Where do Actions Runner Controller (ARC) and GitHub-hosted runners runners run?
Sources
- github.com/actions/actions-runner-controller
- github.com/actions/actions-runner-controller/releases
- github.com/actions/actions-runner-controller/discussions/2775
- docs.github.com/en/actions/concepts/runners/actions-runner-controller
- 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
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). Actions Runner Controller (ARC) vs GitHub-hosted runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actions-runner-controller-vs-github-hosted-runners/