GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners
GARM (GitHub Actions Runner Manager) suits teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure. 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. GARM (GitHub Actions Runner Manager) is an open-source project you run yourself for GitHub Actions and Forgejo/Gitea Actions; TestFlows GitHub Hetzner Runners is an open-source project you run yourself for GitHub Actions.
Key differences between GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners
- CI systems: Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions.
- Operating systems: Only GARM (GitHub Actions Runner Manager) documents Windows.
- Isolation: GARM (GitHub Actions Runner Manager): Depends on provider. 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.
GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners at a glance
| Attribute | GARM (GitHub Actions Runner Manager) | TestFlows GitHub Hetzner Runners |
|---|---|---|
| What it is | Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins. | Self-contained Python service that creates a Hetzner Cloud server for each queued GitHub Actions job, with no webhooks or GitHub App. |
| Type | Open-source project | Open-source project |
| CI systems | GitHub Actions, Forgejo/Gitea Actions | GitHub Actions |
| Operating systems | Linux, Windows | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Runners are instances created by an external provider (cloud VMs, LXD or Incus instances, or Kubernetes pods), so the boundary depends on the provider you choose | 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 |
| Fresh environment per job | Yes | Yes |
| Hardware | Not documented | Any Hetzner Cloud server type, image and location, selected with job labels |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | Not documented | Not documented |
| Caching | Not documented | 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 caching | Not documented | Yes |
| GPU | Not documented | Not documented |
| Concurrency | Each pool or scale set has a maximum number of runners and a minimum number of idle runners | A maximum number of runners can be set, as can a limit per workflow run |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Yes | Yes |
| Pricing | Free 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 tier | Not documented | Not documented |
| Open source | Yes (Apache-2.0) | Yes (Apache-2.0) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Timișoara, Romania | Not documented |
| Good fit for | Teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure | Single-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 GARM (GitHub Actions Runner Manager)
- You want one controller that manages runners in several clouds and on private infrastructure at once
- You want a single binary with an embedded SQLite database instead of an external database or message broker
- You run Gitea or GitHub Enterprise Server as well as github.com
- You want to choose between webhook-driven pools and GitHub runner scale sets
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
- GARM (GitHub Actions Runner Manager): Pools rely on workflow_job webhooks, so the forge must be able to reach GARM; the release notes cite lost webhook deliveries as a risk that scale sets avoid
- GARM (GitHub Actions Runner Manager): Scale set labels can only be set at creation time and cannot be updated afterwards
- 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 GARM (GitHub Actions Runner Manager) profile and TestFlows GitHub Hetzner Runners profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager)
- Cirun vs GARM (GitHub Actions Runner Manager)
- Fireactions vs GARM (GitHub Actions Runner Manager)
- GARM (GitHub Actions Runner Manager) vs myshoes
- GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner
- Fireactions vs TestFlows GitHub Hetzner Runners
- terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners
- TestFlows GitHub Hetzner Runners vs Ubicloud Runners
Frequently asked questions
Is GARM (GitHub Actions Runner Manager) or TestFlows GitHub Hetzner Runners better?
What is the difference between GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners?
Which is open source, GARM (GitHub Actions Runner Manager) or TestFlows GitHub Hetzner Runners?
How do GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners isolate jobs?
How does GARM (GitHub Actions Runner Manager) pricing compare with TestFlows GitHub Hetzner Runners?
Do GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners cache Docker layers?
Where do GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners runners run?
Sources
- github.com/cloudbase/garm
- github.com/cloudbase/garm/releases
- github.com/cloudbase/garm/releases/tag/v0.2.0
- github.com/cloudbase/garm/blob/main/doc/pools-and-scaling.md
- github.com/testflows/TestFlows-GitHub-Hetzner-Runners
- github.com/testflows/TestFlows-GitHub-Hetzner-Runners/releases
- github.com/testflows/TestFlows-GitHub-Hetzner-Runners/blob/main/LICENSE
- 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). GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/garm-vs-github-hetzner-runners/