CI Runnerscirunners.org
Runner profile · Open-source project

Actions Runner Controller (ARC)

Answer in brief

Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. A Kubernetes operator, maintained together with GitHub, that autoscales ephemeral runner pods; it suits teams that already operate a cluster.

By the CI Runners editors · Updated

Overview

Actions Runner Controller (ARC) is a Kubernetes operator that orchestrates and scales self-hosted runners for GitHub Actions. In its runner scale set mode, a listener pod waits for job messages from the GitHub Actions service, and the controller creates ephemeral runner pods that register with a just-in-time configuration token and are removed after their job. Scale sets are installed with Helm and can serve a repository, an organization or an enterprise.

The project has two modes. GitHub supports only the autoscaling runner scale sets (the actions.github.com API group). The older pull-driven and webhook-driven modes (actions.summerwind.net) are called legacy in the README and are maintained by the community only. Windows runners are documented only for the legacy mode. GitHub documents ARC on Kubernetes and OpenShift, and on GitHub Enterprise Server 3.9 and later.

Notable

  • A repository discussion dated 25 July 2023 sets out that GitHub maintains and supports the autoscaling runner scale sets mode, while the earlier scaling modes continue under community maintenance
  • Release gha-runner-scale-set-0.15.1 was published on 23 October 2026
  • The 0.15 release notes also list experimental Helm charts, which they say are not supported for production workloads

Actions Runner Controller (ARC) specifications

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux, Windows
ArchitecturesNot documented
DeploymentOpen-source project
Where it can runKubernetes
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 pods
Fresh environment per jobYes
HardwareNot documented
Performance (vendor claim)Not documented
Runner sizesNot documented
CachingNot documented
Docker layer cachingNot documented
GPUNot 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 idle
Job limitsThe GitHub Actions service unassigns a job if no runner accepts it within 24 hours
Static IPsNot documented
SSH into running jobsNot documented
ObservabilityThe controller-manager and listener pods emit metrics in Prometheus format (from gha-runner-scale-set 0.5.0)
SetupInstall the controller and one or more runner scale sets with Helm, authenticating with a GitHub App or a personal access token. The scale set installation name is the value workflows use in runs-on.
Example labelarc-runner-set
PricingFree and open source; you pay for the infrastructure it runs on.
Free tierNot documented
ComplianceNot documented
RegionsNot documented
Open sourceYes (Apache-2.0)
Company headquartersSan Francisco, California, United States · More from the United States

Facts from Actions Runner Controller (ARC)’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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

Trade-offs

  • Docker-in-Docker mode requires privileged containers
  • Helm does not manage CRD upgrades, so upgrading means uninstalling the scale sets and the controller and reinstalling them
  • GitHub Support treats Kubernetes setup, networking, storage provisioning and image building as out of scope
  • The legacy scaling modes receive community support only

Good fit for: Teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners.

Use cases Actions Runner Controller (ARC) fits

How Actions Runner Controller (ARC) compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States

Head-to-head: 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 GitHub-hosted runners · Actions Runner Controller (ARC) vs RunsOn · Actions Runner Controller (ARC) vs terraform-aws-github-runner

See all Actions Runner Controller (ARC) alternatives →

Frequently asked questions

What is Actions Runner Controller (ARC)?
Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. A Kubernetes operator, maintained together with GitHub, that autoscales ephemeral runner pods; it suits teams that already operate a cluster.
Which CI systems does Actions Runner Controller (ARC) work with?
Actions Runner Controller (ARC) runs jobs for GitHub Actions, on Linux and Windows.
How does Actions Runner Controller (ARC) isolate jobs?
Actions Runner Controller (ARC) documents its isolation as: 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 gets a fresh environment that is discarded afterwards.
Is Actions Runner Controller (ARC) open source?
Yes (Apache-2.0). It can be self-hosted.
How much does Actions Runner Controller (ARC) cost?
Free and open source; you pay for the infrastructure it runs on. Check the official pricing page for current rates.
How do you set up Actions Runner Controller (ARC)?
Install the controller and one or more runner scale sets with Helm, authenticating with a GitHub App or a personal access token. The scale set installation name is the value workflows use in runs-on. An example label is arc-runner-set.
How many jobs can run at once on Actions Runner Controller (ARC)?
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.
Where is GitHub, Inc. based?
GitHub, Inc., the organisation behind Actions Runner Controller (ARC), is headquartered in San Francisco, California, United States. That is where the company is based, not where jobs run.
What are the alternatives to Actions Runner Controller (ARC)?

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. docs.github.com/en/actions/tutorials/use-actions-runner-controller/deploy-runner-scale-sets
  6. docs.github.com/en/actions/tutorials/use-actions-runner-controller/quickstart
  7. docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-support-for-actions-runner-controller
  8. github.com/actions/actions-runner-controller/blob/master/docs/configuring-windows-runners.md
  9. github.com/actions/actions-runner-controller/blob/master/LICENSE
  10. docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement

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). cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/actions-runner-controller/