Actuated vs Fireactions
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. Fireactions suits teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes. 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; Fireactions is an open-source project you run yourself for GitHub Actions.
Key differences between Actuated and Fireactions
- Type: Actuated is a product that runs runners in your own cloud account or on your own hardware; Fireactions is an open-source project you run yourself.
- CI systems: Only Actuated documents GitLab CI.
- Open source: Fireactions is open source (Apache-2.0); Actuated is not.
- Self-hosting: Fireactions documents a self-hosted option; Actuated does not.
- GPUs: Actuated documents GPU runners; Fireactions does not.
- Company headquarters: OpenFaaS Ltd is based in Peterborough, United Kingdom; Hostinger is based in Vilnius, Lithuania.
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both document arm64 runners.
- Both use microVM isolation.
- Both give every job a fresh environment.
Actuated vs Fireactions at a glance
| Attribute | Actuated | Fireactions |
|---|---|---|
| What it is | Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI. | Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts. |
| Type | Runs in your cloud or on your hardware | Open-source project |
| CI systems | GitHub Actions, GitLab CI | GitHub Actions |
| Operating systems | Linux | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | 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) | 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 | 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. | 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) | 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) | The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim) |
| Runner sizes | 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 | vCPU count and memory are set per pool in the Firecracker machine configuration |
| Caching | 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. | A tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images. |
| Docker layer caching | Yes | Not documented |
| GPU | 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. | The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support. |
| Concurrency | The Self-Service plan lists unlimited concurrency; jobs queue once the RAM and CPU of your servers are allocated | Each pool keeps a configured number of runner replicas |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Yes | Yes |
| Pricing | 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 and open source; you pay for the infrastructure it runs on. |
| Free tier | Not documented | Not documented |
| Open source | No | Yes (Apache-2.0) |
| Self-host / your cloud | No / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | Wherever your servers are; the FAQ says the control plane is hosted in the United Kingdom | Not documented |
| Company headquarters | Peterborough, England, United Kingdom | Vilnius, Lithuania |
| Good fit for | 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 | 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 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
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
- Actuated: Windows and macOS are not supported
- Actuated: Servers must be bare metal or support nested virtualisation, and Arm hosts must be bare metal
- Fireactions: Only GitHub organisation accounts are supported
- Fireactions: GPU workloads are not supported
Run your slowest workflow on both before deciding. See the full Actuated profile and Fireactions profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Actuated or Fireactions better?
What is the difference between Actuated and Fireactions?
Which is open source, Actuated or Fireactions?
How do Actuated and Fireactions isolate jobs?
How does Actuated pricing compare with Fireactions?
Is Actuated or Fireactions faster?
Do Actuated and Fireactions cache Docker layers?
Do Actuated and Fireactions offer GPU runners?
Where do Actuated and Fireactions 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). Actuated vs Fireactions. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actuated-vs-fireactions/