Actions Runner Controller (ARC) vs Fireactions
Actions Runner Controller (ARC) suits teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners. Fireactions suits teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes. Actions Runner Controller (ARC) is an open-source project you run yourself for GitHub Actions; Fireactions is an open-source project you run yourself for GitHub Actions.
Key differences between Actions Runner Controller (ARC) and Fireactions
- Operating systems: Only Actions Runner Controller (ARC) documents Windows.
- Isolation: Actions Runner Controller (ARC): Kubernetes pod. Fireactions: Firecracker microVM.
- Company headquarters: GitHub, Inc. is based in San Francisco, United States; Hostinger is based in Vilnius, Lithuania.
What they have in common
- Both are open-source projects you run yourself.
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both give every job a fresh environment.
- Both are open source.
- Both can be self-hosted.
Actions Runner Controller (ARC) vs Fireactions at a glance
| Attribute | Actions Runner Controller (ARC) | Fireactions |
|---|---|---|
| What it is | Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. | Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts. |
| Type | Open-source project | Open-source project |
| CI systems | GitHub Actions | GitHub Actions |
| 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 runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs |
| Fresh environment per job | Yes | Yes |
| Hardware | Not documented | Any Linux host with KVM on x86_64 or aarch64: a bare-metal server or a VM with nested virtualization, plus a dedicated block device for containerd image storage |
| Performance (vendor claim) | Not documented | The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim) |
| Runner sizes | Not documented | vCPU count and memory are set per pool in the Firecracker machine configuration |
| Caching | Not documented | A tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images. |
| Docker layer caching | Not documented | Not documented |
| GPU | Not documented | The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support. |
| 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 keeps a configured number of runner replicas |
| 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 | Vilnius, Lithuania |
| Good fit for | Teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners | Teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes |
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 Fireactions
- You want each job in its own Firecracker microVM that is destroyed afterwards
- You have bare-metal Linux servers, or VMs with nested virtualization, on x86_64 or arm64
- You prefer a standalone binary configured with one YAML file to a Kubernetes operator
- You want to build runner images with ordinary Docker tooling
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
- Fireactions: Only GitHub organisation accounts are supported
- Fireactions: GPU workloads are not supported
Run your slowest workflow on both before deciding. See the full Actions Runner Controller (ARC) profile and Fireactions 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 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 Fireactions
- Fireactions vs GARM (GitHub Actions Runner Manager)
- Fireactions vs myshoes
- Fireactions vs TestFlows GitHub Hetzner Runners
Frequently asked questions
Is Actions Runner Controller (ARC) or Fireactions better?
What is the difference between Actions Runner Controller (ARC) and Fireactions?
Which is open source, Actions Runner Controller (ARC) or Fireactions?
How do Actions Runner Controller (ARC) and Fireactions isolate jobs?
How does Actions Runner Controller (ARC) pricing compare with Fireactions?
Is Actions Runner Controller (ARC) or Fireactions faster?
Do Actions Runner Controller (ARC) and Fireactions offer GPU runners?
Where do Actions Runner Controller (ARC) and Fireactions 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/hostinger/fireactions
- github.com/hostinger/fireactions/releases
- github.com/hostinger/fireactions/blob/main/LICENSE
- github.com/hostinger/fireactions/blob/main/ADOPTERS.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 Fireactions. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actions-runner-controller-vs-fireactions/