CI Runnerscirunners.org
Head-to-head

GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners

Answer in brief

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.

By the CI Runners editors · Updated

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

AttributeGARM (GitHub Actions Runner Manager)TestFlows GitHub Hetzner Runners
What it isSelf-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.
TypeOpen-source projectOpen-source project
CI systemsGitHub Actions, Forgejo/Gitea ActionsGitHub Actions
Operating systemsLinux, WindowsLinux
Architecturesx64, arm64x64, arm64
IsolationRunners are instances created by an external provider (cloud VMs, LXD or Incus instances, or Kubernetes pods), so the boundary depends on the provider you chooseEach 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
HardwareNot documentedAny Hetzner Cloud server type, image and location, selected with job labels
Performance (vendor claim)Not documentedNot documented
Runner sizesNot documentedNot documented
CachingNot documentedUp 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
GPUNot documentedNot documented
ConcurrencyEach pool or scale set has a maximum number of runners and a minimum number of idle runnersA 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 headquartersTimișoara, RomaniaNot documented
Good fit forTeams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructureSingle-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

Frequently asked questions

Is GARM (GitHub Actions Runner Manager) or TestFlows GitHub Hetzner Runners better?
Neither is better for every pipeline. 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.
What is the difference between GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners?
Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions. Only GARM (GitHub Actions Runner Manager) documents Windows. Isolation is Depends on provider on GARM (GitHub Actions Runner Manager) and Hetzner Cloud VM on TestFlows GitHub Hetzner Runners.
Which is open source, GARM (GitHub Actions Runner Manager) or TestFlows GitHub Hetzner Runners?
Both are open source (GARM (GitHub Actions Runner Manager): Apache-2.0; TestFlows GitHub Hetzner Runners: Apache-2.0).
How do GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners isolate jobs?
GARM (GitHub Actions Runner Manager): 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. 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 GARM (GitHub Actions Runner Manager) pricing compare with TestFlows GitHub Hetzner Runners?
GARM (GitHub Actions Runner Manager): 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 GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners pricing pages before deciding.
Do GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners cache Docker layers?
GARM (GitHub Actions Runner Manager): 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.
Where do GARM (GitHub Actions Runner Manager) and TestFlows GitHub Hetzner Runners runners run?
GARM (GitHub Actions Runner Manager) is an open-source project you run yourself (AWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack and Akamai/Linode). TestFlows GitHub Hetzner Runners is an open-source project you run yourself (Hetzner).

Sources

  1. github.com/cloudbase/garm
  2. github.com/cloudbase/garm/releases
  3. github.com/cloudbase/garm/releases/tag/v0.2.0
  4. github.com/cloudbase/garm/blob/main/doc/pools-and-scaling.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). 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/