CI Runnerscirunners.org
Head-to-head

Actions Runner Controller (ARC) vs RunsOn

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. RunsOn suits teams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence. Actions Runner Controller (ARC) is an open-source project you run yourself for GitHub Actions; RunsOn is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, priced at €300/yr licence + AWS cost.

By the CI Runners editors · Updated

Key differences between Actions Runner Controller (ARC) and RunsOn

  • Type: Actions Runner Controller (ARC) is an open-source project you run yourself; RunsOn is a product that runs runners in your own cloud account or on your own hardware.
  • Isolation: Actions Runner Controller (ARC): Kubernetes pod. RunsOn: EC2 instance.
  • Open source: Actions Runner Controller (ARC) is open source (Apache-2.0); RunsOn is not.
  • Company headquarters: GitHub, Inc. is based in San Francisco, United States; RunsOn is based in Thorigné-Fouillard, France.

What they have in common

  • Both run GitHub Actions jobs.
  • Both document Linux and Windows runners.
  • Both give every job a fresh environment.
  • Both can be self-hosted.

Actions Runner Controller (ARC) vs RunsOn at a glance

AttributeActions Runner Controller (ARC)RunsOn
What it isKubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets.Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job.
TypeOpen-source projectRuns in your cloud or on your hardware
CI systemsGitHub ActionsGitHub 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 podsEach job runs on an EC2 instance that no other job has used and that is terminated when the job ends
Fresh environment per jobYesYes
HardwareNot documentedAny EC2 instance family selected by label, including Graviton and families with local NVMe; the docs cite 1 to 896 vCPUs.
Performance (vendor claim)Not documentedRunsOn says Rust builds run 2.0x, TypeScript 2.1x and Docker builds 2.6x faster than on GitHub-hosted runners in its own benchmarks (vendor claim)
Runner sizesNot documentedPredefined runners from 1 to 64 vCPU on x64 and arm64; labels can request any EC2 instance type, which the docs describe as 1 to 896 vCPUs
CachingNot documentedMagic Cache redirects actions/cache and Buildx type=gha to an S3 bucket in your account with no size cap (extras=s3-cache). Docker layers can also be cached in a per-stack ECR registry or on sticky EBS disks, and v3.6.0 added S3-backed remote caches for Bazel, Go, Gradle, sccache and Turborepo.
Docker layer cachingNot documentedYes
GPUNot documentedGPU images with NVIDIA drivers are published for x64 and Graviton instances (examples use g4dn, g5 and g5g); GPU compute is billed by AWS and no RunsOn GPU price is published.
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 idleNo RunsOn concurrency limit is documented; the Flex mode is recommended for up to about 50,000 jobs a day
Static IPsNot documentedYes
SSH into running jobsNot documentedYes
PricingFree and open source; you pay for the infrastructure it runs on.Flat annual licence per legal entity: Starter €300/year (under 50k jobs/month), Growth €900/year (under 200k), Scale €1,800/year (under 500k), Sponsorship €3,600/year (unlimited jobs, source access). EC2, EBS and S3 are billed by AWS with no RunsOn markup; RunsOn says the control plane costs from about $7/month.
Free tierNot documentedFree licence for non-commercial use (open source, non-profit, educational, personal) with a public link back; 15-day trial on Starter, Growth and Scale
Open sourceYes (Apache-2.0)No
Self-host / your cloudYes / YesYes / Yes
ComplianceNot documentedNot documented
RegionsNot documentedNot documented
Company headquartersSan Francisco, California, United StatesThorigné-Fouillard, Brittany, France
Good fit forTeams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runnersTeams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence

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 RunsOn

  • You want every job on a fresh EC2 instance inside your own AWS account, with code, secrets, caches and logs staying there
  • You prefer a flat annual licence by job volume over per-minute fees, with compute billed directly by AWS
  • You need Linux x64, arm64, Windows or GPU runners chosen per job through labels
  • You need static egress IPs, private subnets, or SSM and SSH access to running jobs

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
  • RunsOn: AWS only, and macOS is not supported: macOS jobs stay on GitHub-hosted runners
  • RunsOn: The server and agent are proprietary; full source is offered only with the €3,600/year Sponsorship licence

Run your slowest workflow on both before deciding. See the full Actions Runner Controller (ARC) profile and RunsOn profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Actions Runner Controller (ARC) or RunsOn 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. RunsOn suits teams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence.
What is the difference between Actions Runner Controller (ARC) and RunsOn?
Actions Runner Controller (ARC) is an open-source project you run yourself; RunsOn is a product that runs runners in your own cloud account or on your own hardware. Isolation is Kubernetes pod on Actions Runner Controller (ARC) and EC2 instance on RunsOn. Actions Runner Controller (ARC) is open source (Apache-2.0); RunsOn is not. GitHub, Inc. is based in San Francisco, United States; RunsOn is based in Thorigné-Fouillard, France.
Which is open source, Actions Runner Controller (ARC) or RunsOn?
Actions Runner Controller (ARC) is open source (Apache-2.0); RunsOn is not open source.
How do Actions Runner Controller (ARC) and RunsOn 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. RunsOn: Each job runs on an EC2 instance that no other job has used and that is terminated when the job ends.
How does Actions Runner Controller (ARC) pricing compare with RunsOn?
Actions Runner Controller (ARC): Free and open source; you pay for the infrastructure it runs on. RunsOn: Flat annual licence per legal entity: Starter €300/year (under 50k jobs/month), Growth €900/year (under 200k), Scale €1,800/year (under 500k), Sponsorship €3,600/year (unlimited jobs, source access). EC2, EBS and S3 are billed by AWS with no RunsOn markup; RunsOn says the control plane costs from about $7/month. Rates change, so check the Actions Runner Controller (ARC) and RunsOn pricing pages before deciding.
Is Actions Runner Controller (ARC) or RunsOn faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Actions Runner Controller (ARC): Not documented. RunsOn: RunsOn says Rust builds run 2.0x, TypeScript 2.1x and Docker builds 2.6x faster than on GitHub-hosted runners in its own benchmarks (vendor claim).
Do Actions Runner Controller (ARC) and RunsOn cache Docker layers?
Actions Runner Controller (ARC): Docker layer caching is not documented. RunsOn: Magic Cache redirects actions/cache and Buildx type=gha to an S3 bucket in your account with no size cap (extras=s3-cache). Docker layers can also be cached in a per-stack ECR registry or on sticky EBS disks, and v3.6.0 added S3-backed remote caches for Bazel, Go, Gradle, sccache and Turborepo.
Do Actions Runner Controller (ARC) and RunsOn offer GPU runners?
Actions Runner Controller (ARC): Not documented. RunsOn: GPU images with NVIDIA drivers are published for x64 and Graviton instances (examples use g4dn, g5 and g5g); GPU compute is billed by AWS and no RunsOn GPU price is published.
Where do Actions Runner Controller (ARC) and RunsOn runners run?
Actions Runner Controller (ARC) is an open-source project you run yourself (Kubernetes). RunsOn is a product that runs runners in your own cloud account or on your own hardware (AWS).

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. runs-on.com/
  6. runs-on.com/pricing/
  7. runs-on.com/docs/
  8. runs-on.com/docs/flex-vs-fleet/

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 RunsOn. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actions-runner-controller-vs-runs-on/