CI Runnerscirunners.org
Runner profile · Open-source project

Fireactions

Answer in brief

Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts. An open-source Firecracker orchestrator from Hostinger for ephemeral GitHub Actions runners on your own Linux hosts; it suits teams that want microVM isolation without Kubernetes.

By the CI Runners editors · Updated

Overview

Fireactions is an orchestrator for GitHub Actions runners that Hostinger built for its own infrastructure and describes as BYOM, bring your own metal. A server process reads pools from a YAML file and keeps the configured number of runners available in each. Every runner is a Firecracker microVM booted from an OCI image, registered with a just-in-time token, and shut down when its job finishes.

It is a standalone application, which the FAQ contrasts with Kubernetes-based Actions Runner Controller, and it runs on a bare-metal server or a VM with nested virtualization. Hostinger publishes Ubuntu 20.04, 22.04 and 24.04 base images with Docker preinstalled, and custom images can be built with Docker. The CLI can list machines, stream agent logs and open an SSH session to a running VM. Hostinger is the only adopter listed in the repository.

Notable

  • v2.2.2 was released on 17 November 2026
  • The README notes many breaking changes and names v2.0.0 as the stable version to use in production
  • The docs say the project is in the early stages of development and that Hostinger uses it fully in production

Fireactions specifications

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux
Architecturesx64, arm64
DeploymentOpen-source project
Where it can runBare metal
IsolationEach runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs
Fresh environment per jobYes
HardwareAny 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)The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim)
Runner sizesvCPU count and memory are set per pool in the Firecracker machine configuration
CachingA tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images.
Docker layer cachingNot documented
GPUThe FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support.
ConcurrencyEach pool keeps a configured number of runner replicas
Job limitsNot documented
Static IPsNot documented
SSH into running jobsYes
ObservabilityPrometheus metrics endpoint, with an example Grafana dashboard in the docs
SetupInstall Firecracker, containerd, the CNI plugins and the Fireactions binary on a KVM-capable Linux host. Create a GitHub App for your organisation and define pools in a YAML configuration file.
Example label[self-hosted, fireactions]
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 headquartersVilnius, Lithuania · More from Lithuania

Facts from Fireactions’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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
  • You want to SSH into a running runner VM from the CLI when debugging

Trade-offs

  • Only GitHub organisation accounts are supported
  • GPU workloads are not supported
  • The docs describe the project as still in the early stages of development
  • Running it inside a VM rather than on bare metal may affect performance, according to the FAQ

Good fit for: Teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes.

Use cases Fireactions fits

  • ARM64 builds: aarch64 hosts are supported alongside x86_64.
  • Your own cloud: It runs on your own bare-metal servers or nested-virtualization VMs.
  • Open source and self-hosted: Fireactions is Apache-2.0 licensed and runs as a standalone binary on hosts you operate.
  • Security and compliance: Each job runs in its own Firecracker microVM, which the docs recommend for untrusted workloads such as CI jobs.

How Fireactions compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
myshoesGitHub ActionsLinuxSelf-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
TestFlows GitHub Hetzner RunnersGitHub ActionsLinux, x64, arm64Self-hostedHetzner Cloud VMFree software + your infrastructureSet by your infrastructureYesNot documentedYesNot documented
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States

Head-to-head: Actions Runner Controller (ARC) vs Fireactions · Actuated vs Fireactions · Fireactions vs GARM (GitHub Actions Runner Manager) · Fireactions vs myshoes · Fireactions vs TestFlows GitHub Hetzner Runners

See all Fireactions alternatives →

Frequently asked questions

What is Fireactions?
Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts. An open-source Firecracker orchestrator from Hostinger for ephemeral GitHub Actions runners on your own Linux hosts; it suits teams that want microVM isolation without Kubernetes.
Which CI systems does Fireactions work with?
Fireactions runs jobs for GitHub Actions, on Linux, x64 and arm64.
How does Fireactions isolate jobs?
Fireactions documents its isolation as: Each runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs. Each job gets a fresh environment that is discarded afterwards.
Is Fireactions open source?
Yes (Apache-2.0). It can be self-hosted.
How much does Fireactions 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 Fireactions?
Install Firecracker, containerd, the CNI plugins and the Fireactions binary on a KVM-capable Linux host. Create a GitHub App for your organisation and define pools in a YAML configuration file. An example label is [self-hosted, fireactions].
How fast is Fireactions?
The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim). Speed figures are the provider’s own and depend on the workload.
Does Fireactions support ARM64 runners?
Yes, Fireactions documents arm64 runners (Linux).
Does Fireactions offer GPU runners?
The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support.
How many jobs can run at once on Fireactions?
Each pool keeps a configured number of runner replicas.
Where is Hostinger based?
Hostinger, the organisation behind Fireactions, is headquartered in Vilnius, Lithuania. That is where the company is based, not where jobs run.
What are the alternatives to Fireactions?

Sources

  1. github.com/hostinger/fireactions
  2. github.com/hostinger/fireactions/releases
  3. github.com/hostinger/fireactions/blob/main/LICENSE
  4. github.com/hostinger/fireactions/blob/main/ADOPTERS.md
  5. fireactions.io/latest/
  6. github.com/hostinger/fireactions/blob/main/docs/user-guide/overview.md
  7. github.com/hostinger/fireactions/blob/main/docs/user-guide/installation.md
  8. github.com/hostinger/fireactions/blob/main/docs/user-guide/images.md
  9. github.com/hostinger/fireactions/blob/main/docs/help/faq.md
  10. hostinger.com/about

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