CI Runnerscirunners.org
Head-to-head

Fireactions vs TestFlows GitHub Hetzner Runners

Answer in brief

Fireactions suits teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes. TestFlows GitHub Hetzner Runners suits single-repository projects that want low-cost x64 or arm64 GitHub Actions runners on Hetzner Cloud with very little setup. Fireactions is an open-source project you run yourself for GitHub Actions; TestFlows GitHub Hetzner Runners is an open-source project you run yourself for GitHub Actions.

By the CI Runners editors · Updated

Key differences between Fireactions and TestFlows GitHub Hetzner Runners

  • Isolation: Fireactions: Firecracker microVM. TestFlows GitHub Hetzner Runners: Hetzner Cloud VM.

What they have in common

  • Both are open-source projects you run yourself.
  • Both run GitHub Actions jobs.
  • Both document Linux runners.
  • Both document arm64 runners.
  • Both give every job a fresh environment.
  • Both are open source.
  • Both can be self-hosted.

Fireactions vs TestFlows GitHub Hetzner Runners at a glance

AttributeFireactionsTestFlows GitHub Hetzner Runners
What it isOrchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts.Self-contained Python service that creates a Hetzner Cloud server for each queued GitHub Actions job, with no webhooks or GitHub App.
TypeOpen-source projectOpen-source project
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinuxLinux
Architecturesx64, arm64x64, arm64
IsolationEach runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobsEach job gets a dedicated Hetzner Cloud VM that is not shared between jobs; with recycling (on by default) a powered-off server is rebuilt from its image before reuse, unless the no-rebuild mode for trusted single-tenant setups is chosen
Fresh environment per jobYesYes
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 storageAny Hetzner Cloud server type, image and location, selected with job labels
Performance (vendor claim)The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim)Not documented
Runner sizesvCPU count and memory are set per pool in the Firecracker machine configurationNot documented
CachingA tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images.Up to sixteen persistent Hetzner Cloud volumes of 10 GB to 10 TB per runner, requested with volume labels and mounted under /mnt. The wiki describes ways to keep Docker data on them and warns that volumes are never deleted automatically.
Docker layer cachingNot documentedYes
GPUThe FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support.Not documented
ConcurrencyEach pool keeps a configured number of runner replicasA maximum number of runners can be set, as can a limit per workflow run
Static IPsNot documentedNot documented
SSH into running jobsYesYes
PricingFree and open source; you pay for the infrastructure it runs on.Free and open source; you pay for the infrastructure it runs on. The README notes that Hetzner Cloud bills servers hourly, so without recycling the minimum cost of a job is one server-hour plus a public IPv4 address.
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 headquartersVilnius, LithuaniaNot documented
Good fit forTeams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running KubernetesSingle-repository projects that want low-cost x64 or arm64 GitHub Actions runners on Hetzner Cloud with very little setup

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

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

Reasons to choose TestFlows GitHub Hetzner Runners

  • You want each job on its own Hetzner Cloud VM with full root access and native Docker
  • You want a setup with no webhooks, no GitHub App and no Kubernetes
  • You need arm64 as well as x64 runners
  • You want persistent volumes for caches that survive between jobs

Trade-offs to check first

  • Fireactions: Only GitHub organisation accounts are supported
  • Fireactions: GPU workloads are not supported
  • TestFlows GitHub Hetzner Runners: Group runners are not supported
  • TestFlows GitHub Hetzner Runners: A unique Hetzner Cloud project must be used for each repository

Run your slowest workflow on both before deciding. See the full Fireactions profile and TestFlows GitHub Hetzner Runners profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Fireactions or TestFlows GitHub Hetzner Runners better?
Neither is better for every pipeline. Fireactions suits teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes. TestFlows GitHub Hetzner Runners suits single-repository projects that want low-cost x64 or arm64 GitHub Actions runners on Hetzner Cloud with very little setup.
What is the difference between Fireactions and TestFlows GitHub Hetzner Runners?
Isolation is Firecracker microVM on Fireactions and Hetzner Cloud VM on TestFlows GitHub Hetzner Runners.
Which is open source, Fireactions or TestFlows GitHub Hetzner Runners?
Both are open source (Fireactions: Apache-2.0; TestFlows GitHub Hetzner Runners: Apache-2.0).
How do Fireactions and TestFlows GitHub Hetzner Runners isolate jobs?
Fireactions: Each runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs. TestFlows GitHub Hetzner Runners: Each job gets a dedicated Hetzner Cloud VM that is not shared between jobs; with recycling (on by default) a powered-off server is rebuilt from its image before reuse, unless the no-rebuild mode for trusted single-tenant setups is chosen.
How does Fireactions pricing compare with TestFlows GitHub Hetzner Runners?
Fireactions: Free and open source; you pay for the infrastructure it runs on. TestFlows GitHub Hetzner Runners: Free and open source; you pay for the infrastructure it runs on. The README notes that Hetzner Cloud bills servers hourly, so without recycling the minimum cost of a job is one server-hour plus a public IPv4 address. Rates change, so check the Fireactions and TestFlows GitHub Hetzner Runners pricing pages before deciding.
Is Fireactions or TestFlows GitHub Hetzner Runners faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Fireactions: The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim). TestFlows GitHub Hetzner Runners: Not documented.
Do Fireactions and TestFlows GitHub Hetzner Runners cache Docker layers?
Fireactions: Docker layer caching is not documented. TestFlows GitHub Hetzner Runners: Up to sixteen persistent Hetzner Cloud volumes of 10 GB to 10 TB per runner, requested with volume labels and mounted under /mnt. The wiki describes ways to keep Docker data on them and warns that volumes are never deleted automatically.
Do Fireactions and TestFlows GitHub Hetzner Runners offer GPU runners?
Fireactions: The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support. TestFlows GitHub Hetzner Runners: Not documented.
Where do Fireactions and TestFlows GitHub Hetzner Runners runners run?
Fireactions is an open-source project you run yourself (Bare metal). TestFlows GitHub Hetzner Runners is an open-source project you run yourself (Hetzner).

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. github.com/testflows/TestFlows-GitHub-Hetzner-Runners
  6. github.com/testflows/TestFlows-GitHub-Hetzner-Runners/releases
  7. github.com/testflows/TestFlows-GitHub-Hetzner-Runners/blob/main/LICENSE
  8. github.com/testflows/TestFlows-GitHub-Hetzner-Runners/wiki/Recycling-Powered-Off-Servers

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 vs TestFlows GitHub Hetzner Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/fireactions-vs-github-hetzner-runners/