CI Runnerscirunners.org
Head-to-head

Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager)

Answer in brief

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.

By the CI Runners editors · Updated

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

AttributeActions Runner Controller (ARC)GARM (GitHub Actions Runner Manager)
What it isKubernetes 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.
TypeOpen-source projectOpen-source project
CI systemsGitHub ActionsGitHub Actions, Forgejo/Gitea Actions
Operating systemsLinux, WindowsLinux, Windows
ArchitecturesNot documentedx64, arm64
IsolationEach 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 podsRunners 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 jobYesYes
HardwareNot documentedNot documented
Performance (vendor claim)Not documentedNot documented
Runner sizesNot documentedNot documented
CachingNot documentedNot documented
Docker layer cachingNot documentedNot documented
GPUNot documentedNot documented
ConcurrencySet per runner scale set with minRunners and maxRunners; with both unset, runners follow the number of assigned jobs and scale down to zero when idleEach pool or scale set has a maximum number of runners and a minimum number of idle runners
Static IPsNot documentedNot documented
SSH into running jobsNot documentedYes
PricingFree and open source; you pay for the infrastructure it runs on.Free and open source; you pay for the infrastructure it runs on.
Free tierNot documentedNot documented
Open sourceYes (Apache-2.0)Yes (Apache-2.0)
Self-host / your cloudYes / YesYes / Yes
ComplianceNot documentedNot documented
RegionsNot documentedNot documented
Company headquartersSan Francisco, California, United StatesTimișoara, Romania
Good fit forTeams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runnersTeams 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

Frequently asked questions

Is Actions Runner Controller (ARC) or GARM (GitHub Actions Runner Manager) better?
Neither is better for every pipeline. 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.
What is the difference between Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager)?
Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions. Isolation is Kubernetes pod on Actions Runner Controller (ARC) and Depends on provider on GARM (GitHub Actions Runner Manager). GitHub, Inc. is based in San Francisco, United States; Cloudbase Solutions is based in Timișoara, Romania.
Which is open source, Actions Runner Controller (ARC) or GARM (GitHub Actions Runner Manager)?
Both are open source (Actions Runner Controller (ARC): Apache-2.0; GARM (GitHub Actions Runner Manager): Apache-2.0).
How do Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager) isolate jobs?
Actions Runner Controller (ARC): 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. GARM (GitHub Actions Runner Manager): 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.
How does Actions Runner Controller (ARC) pricing compare with GARM (GitHub Actions Runner Manager)?
Actions Runner Controller (ARC): Free and open source; you pay for the infrastructure it runs on. GARM (GitHub Actions Runner Manager): Free and open source; you pay for the infrastructure it runs on. Rates change, so check the Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager) pricing pages before deciding.
Where do Actions Runner Controller (ARC) and GARM (GitHub Actions Runner Manager) runners run?
Actions Runner Controller (ARC) is an open-source project you run yourself (Kubernetes). GARM (GitHub Actions Runner Manager) is an open-source project you run yourself (AWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack and Akamai/Linode).

Sources

  1. github.com/actions/actions-runner-controller
  2. github.com/actions/actions-runner-controller/releases
  3. github.com/actions/actions-runner-controller/discussions/2775
  4. docs.github.com/en/actions/concepts/runners/actions-runner-controller
  5. github.com/cloudbase/garm
  6. github.com/cloudbase/garm/releases
  7. github.com/cloudbase/garm/releases/tag/v0.2.0
  8. 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/