Actions Runner Controller (ARC) vs Actuated
Actions Runner Controller (ARC) suits teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners. Actuated suits teams that want microVM isolation for GitHub Actions or GitLab CI jobs on their own bare-metal or nested-virtualisation servers at a flat monthly rate. Actions Runner Controller (ARC) is an open-source project you run yourself for GitHub Actions; Actuated is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions and GitLab CI, priced at $150/mo per server + your servers.
Key differences between Actions Runner Controller (ARC) and Actuated
- Type: Actions Runner Controller (ARC) is an open-source project you run yourself; Actuated is a product that runs runners in your own cloud account or on your own hardware.
- CI systems: Only Actuated documents GitLab CI.
- Operating systems: Only Actions Runner Controller (ARC) documents Windows.
- Isolation: Actions Runner Controller (ARC): Kubernetes pod. Actuated: Firecracker microVM.
- Open source: Actions Runner Controller (ARC) is open source (Apache-2.0); Actuated is not.
- Self-hosting: Actions Runner Controller (ARC) documents a self-hosted option; Actuated does not.
- Company headquarters: GitHub, Inc. is based in San Francisco, United States; OpenFaaS Ltd is based in Peterborough, United Kingdom.
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both give every job a fresh environment.
Actions Runner Controller (ARC) vs Actuated at a glance
| Attribute | Actions Runner Controller (ARC) | Actuated |
|---|---|---|
| What it is | Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. | Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI. |
| Type | Open-source project | Runs in your cloud or on your hardware |
| CI systems | GitHub Actions | GitHub Actions, GitLab CI |
| Operating systems | Linux, Windows | Linux |
| 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 its own Firecracker microVM on your server, created for one build and destroyed afterwards (Cloud Hypervisor is used on GPU hosts) |
| Fresh environment per job | Yes | Yes |
| Hardware | Not documented | Your own bare-metal servers or VMs with nested virtualisation; the docs recommend NVMe storage and list Ampere, Graviton and Apple Silicon (Asahi Linux) hosts for Arm. |
| Performance (vendor claim) | Not documented | Actuated says builds are often 2-3x faster, and cites a customer Arm build cut from about 6 hours under QEMU to 20 minutes (vendor claim) |
| Runner sizes | Not documented | No fixed sizes: vCPU and RAM are set per job in the label (for example actuated-4cpu-16gb) within the capacity of your server; fractional 0.25 and 0.5 vCPU sizes were announced in October 2025 |
| Caching | Not documented | A transparent cache announced in October 2025 redirects actions/cache, BuildKit and setup-* action caches to local NVMe on your server without workflow changes. The docs also cover a registry mirror and a self-hosted S3 cache (SeaweedFS or MinIO) on the host. |
| Docker layer caching | Not documented | Yes |
| GPU | Not documented | GPUs on the host are passed through whole to one job at a time via VFIO, which requires switching the server from Firecracker to Cloud Hypervisor; jobs add a gpu label. |
| 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 | The Self-Service plan lists unlimited concurrency; jobs queue once the RAM and CPU of your servers are allocated |
| 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. | Self-Service Plan: flat rate per server, $150 per month for the first and $125 for each additional, with unlimited build minutes, RAM/CPUs and concurrency. Servers are paid for separately. An October 2025 post says custom billing is available to customers needing more than 50 concurrent builds. |
| Free tier | Not documented | Not documented |
| Open source | Yes (Apache-2.0) | No |
| Self-host / your cloud | Yes / Yes | No / Yes |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Wherever your servers are; the FAQ says the control plane is hosted in the United Kingdom |
| Company headquarters | San Francisco, California, United States | Peterborough, England, United Kingdom |
| Good fit for | Teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners | Teams that want microVM isolation for GitHub Actions or GitLab CI jobs on their own bare-metal or nested-virtualisation servers at a flat monthly rate |
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 Actuated
- You want each job isolated in its own Firecracker microVM without privileged containers or Docker-in-Docker
- You already have, or want to rent, bare-metal or nested-virtualisation servers and prefer a flat monthly rate per server
- You need native 64-bit Arm builds on hardware such as Ampere or Graviton hosts
- You run GitLab CI as well as GitHub Actions and want the same runner model for both
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
- Actuated: Windows and macOS are not supported
- Actuated: Servers must be bare metal or support nested virtualisation, and Arm hosts must be bare metal
Run your slowest workflow on both before deciding. See the full Actions Runner Controller (ARC) profile and Actuated profile, or the complete comparison.
More comparisons
- 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
- Actuated vs Cirun
- Actuated vs Fireactions
- Actuated vs RunsOn
Frequently asked questions
Is Actions Runner Controller (ARC) or Actuated better?
What is the difference between Actions Runner Controller (ARC) and Actuated?
Which is open source, Actions Runner Controller (ARC) or Actuated?
How do Actions Runner Controller (ARC) and Actuated isolate jobs?
How does Actions Runner Controller (ARC) pricing compare with Actuated?
Is Actions Runner Controller (ARC) or Actuated faster?
Do Actions Runner Controller (ARC) and Actuated cache Docker layers?
Do Actions Runner Controller (ARC) and Actuated offer GPU runners?
Where do Actions Runner Controller (ARC) and Actuated runners run?
Sources
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 Actuated. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actions-runner-controller-vs-actuated/