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.
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
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux |
| Architectures | x64, arm64 |
| Deployment | Open-source project |
| Where it can run | Bare metal |
| Isolation | 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 |
| Hardware | 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) | The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim) |
| Runner sizes | vCPU count and memory are set per pool in the Firecracker machine configuration |
| Caching | A tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images. |
| Docker layer caching | Not documented |
| GPU | The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support. |
| Concurrency | Each pool keeps a configured number of runner replicas |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Yes |
| Observability | Prometheus metrics endpoint, with an example Grafana dashboard in the docs |
| Setup | 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. |
| Example label | [self-hosted, fireactions] |
| Pricing | Free and open source; you pay for the infrastructure it runs on. |
| Free tier | Not documented |
| Compliance | Not documented |
| Regions | Not documented |
| Open source | Yes (Apache-2.0) |
| Company headquarters | Vilnius, 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
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Fireactions | GitHub Actions | Linux, x64, arm64 | Self-hosted | Firecracker microVM | Free software + your infrastructure | Set by your infrastructure | Not documented | No | Yes | Lithuania |
| Actuated | GitHub Actions, GitLab CI | Linux, x64, arm64 | Your cloud or hardware | Firecracker microVM | $150/mo per server + your servers | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | Linux, Windows, x64, arm64 | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Romania |
| myshoes | GitHub Actions | Linux | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| TestFlows GitHub Hetzner Runners | GitHub Actions | Linux, x64, arm64 | Self-hosted | Hetzner Cloud VM | Free software + your infrastructure | Set by your infrastructure | Yes | Not documented | Yes | Not documented |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United 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
Frequently asked questions
What is Fireactions?
Which CI systems does Fireactions work with?
How does Fireactions isolate jobs?
Is Fireactions open source?
How much does Fireactions cost?
How do you set up Fireactions?
[self-hosted, fireactions].How fast is Fireactions?
Does Fireactions support ARM64 runners?
Does Fireactions offer GPU runners?
How many jobs can run at once on Fireactions?
Where is Hostinger based?
What are the alternatives to Fireactions?
Sources
- github.com/hostinger/fireactions
- github.com/hostinger/fireactions/releases
- github.com/hostinger/fireactions/blob/main/LICENSE
- github.com/hostinger/fireactions/blob/main/ADOPTERS.md
- fireactions.io/latest/
- github.com/hostinger/fireactions/blob/main/docs/user-guide/overview.md
- github.com/hostinger/fireactions/blob/main/docs/user-guide/installation.md
- github.com/hostinger/fireactions/blob/main/docs/user-guide/images.md
- github.com/hostinger/fireactions/blob/main/docs/help/faq.md
- 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/