CI Runnerscirunners.org
Head-to-head

Actions Runner Controller (ARC) vs Fireactions

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. 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.

By the CI Runners editors · Updated

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

AttributeActions Runner Controller (ARC)Fireactions
What it isKubernetes 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.
TypeOpen-source projectOpen-source project
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinux, WindowsLinux
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 runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs
Fresh environment per jobYesYes
HardwareNot documentedAny 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 documentedThe Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim)
Runner sizesNot documentedvCPU count and memory are set per pool in the Firecracker machine configuration
CachingNot documentedA tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images.
Docker layer cachingNot documentedNot documented
GPUNot documentedThe FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support.
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 keeps a configured number of runner replicas
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 StatesVilnius, Lithuania
Good fit forTeams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runnersTeams 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

Frequently asked questions

Is Actions Runner Controller (ARC) or Fireactions 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. Fireactions suits teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes.
What is the difference between Actions Runner Controller (ARC) and Fireactions?
Only Actions Runner Controller (ARC) documents Windows. Isolation is Kubernetes pod on Actions Runner Controller (ARC) and Firecracker microVM on Fireactions. GitHub, Inc. is based in San Francisco, United States; Hostinger is based in Vilnius, Lithuania.
Which is open source, Actions Runner Controller (ARC) or Fireactions?
Both are open source (Actions Runner Controller (ARC): Apache-2.0; Fireactions: Apache-2.0).
How do Actions Runner Controller (ARC) and Fireactions 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. Fireactions: Each runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs.
How does Actions Runner Controller (ARC) pricing compare with Fireactions?
Actions Runner Controller (ARC): Free and open source; you pay for the infrastructure it runs on. Fireactions: Free and open source; you pay for the infrastructure it runs on. Rates change, so check the Actions Runner Controller (ARC) and Fireactions pricing pages before deciding.
Is Actions Runner Controller (ARC) or Fireactions faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Actions Runner Controller (ARC): Not documented. Fireactions: The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim).
Do Actions Runner Controller (ARC) and Fireactions offer GPU runners?
Actions Runner Controller (ARC): Not documented. Fireactions: The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support.
Where do Actions Runner Controller (ARC) and Fireactions runners run?
Actions Runner Controller (ARC) is an open-source project you run yourself (Kubernetes). Fireactions is an open-source project you run yourself (Bare metal).

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/hostinger/fireactions
  6. github.com/hostinger/fireactions/releases
  7. github.com/hostinger/fireactions/blob/main/LICENSE
  8. 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/