Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager)
Actions Runner Controller (ARC) suits teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners. GARM (GitHub Actions Runner Manager) suits teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure. Actions Runner Controller (ARC) is an open-source project you run yourself for GitHub Actions; GARM (GitHub Actions Runner Manager) is an open-source project you run yourself for GitHub Actions and Forgejo/Gitea Actions.
Key differences between Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager)
- CI systems: Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions.
- Isolation: Actions Runner Controller (ARC): Kubernetes pod. GARM (GitHub Actions Runner Manager): Depends on provider.
- Company headquarters: GitHub, Inc. is based in San Francisco, United States; Cloudbase Solutions is based in Timișoara, Romania.
What they have in common
- Both are open-source projects you run yourself.
- Both run GitHub Actions jobs.
- Both document Linux and Windows runners.
- Both give every job a fresh environment.
- Both are open source.
- Both can be self-hosted.
Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager) at a glance
| Attribute | Actions Runner Controller (ARC) | GARM (GitHub Actions Runner Manager) |
|---|---|---|
| What it is | Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. | Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins. |
| Type | Open-source project | Open-source project |
| CI systems | GitHub Actions | GitHub Actions, Forgejo/Gitea Actions |
| Operating systems | Linux, Windows | Linux, 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 | Runners are instances created by an external provider (cloud VMs, LXD or Incus instances, or Kubernetes pods), so the boundary depends on the provider you choose |
| Fresh environment per job | Yes | Yes |
| Hardware | Not documented | Not documented |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | Not documented | Not documented |
| Caching | Not documented | Not documented |
| Docker layer caching | Not documented | Not documented |
| GPU | Not documented | Not documented |
| 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 | Each pool or scale set has a maximum number of runners and a minimum number of idle runners |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Not documented | Yes |
| Pricing | Free and open source; you pay for the infrastructure it runs on. | Free and open source; you pay for the infrastructure it runs on. |
| Free tier | Not documented | Not documented |
| Open source | Yes (Apache-2.0) | Yes (Apache-2.0) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | San Francisco, California, United States | Timișoara, Romania |
| Good fit for | Teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners | Teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure |
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 GARM (GitHub Actions Runner Manager)
- You want one controller that manages runners in several clouds and on private infrastructure at once
- You want a single binary with an embedded SQLite database instead of an external database or message broker
- You run Gitea or GitHub Enterprise Server as well as github.com
- You want to choose between webhook-driven pools and GitHub runner scale sets
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
- GARM (GitHub Actions Runner Manager): Pools rely on workflow_job webhooks, so the forge must be able to reach GARM; the release notes cite lost webhook deliveries as a risk that scale sets avoid
- GARM (GitHub Actions Runner Manager): Scale set labels can only be set at creation time and cannot be updated afterwards
Run your slowest workflow on both before deciding. See the full Actions Runner Controller (ARC) profile and GARM (GitHub Actions Runner Manager) 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 GitHub-hosted runners
- Actions Runner Controller (ARC) vs RunsOn
- Actions Runner Controller (ARC) vs terraform-aws-github-runner
- Cirun vs GARM (GitHub Actions Runner Manager)
- Fireactions vs GARM (GitHub Actions Runner Manager)
- GARM (GitHub Actions Runner Manager) vs myshoes
- GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner
- GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners
Frequently asked questions
Is Actions Runner Controller (ARC) or GARM (GitHub Actions Runner Manager) better?
What is the difference between Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager)?
Which is open source, Actions Runner Controller (ARC) or GARM (GitHub Actions Runner Manager)?
How do Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager) isolate jobs?
How does Actions Runner Controller (ARC) pricing compare with GARM (GitHub Actions Runner Manager)?
Where do Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager) 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
- github.com/cloudbase/garm
- github.com/cloudbase/garm/releases
- github.com/cloudbase/garm/releases/tag/v0.2.0
- github.com/cloudbase/garm/blob/main/doc/pools-and-scaling.md
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 GARM (GitHub Actions Runner Manager). cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actions-runner-controller-vs-garm/