TestFlows GitHub Hetzner Runners
Self-contained Python service that creates a Hetzner Cloud server for each queued GitHub Actions job, with no webhooks or GitHub App. A single-command autoscaler that puts each GitHub Actions job on its own Hetzner Cloud server; it suits individual repositories that want inexpensive runners and accept hands-on operation.
Overview
TestFlows GitHub Hetzner Runners is a Python command-line service that watches a repository for queued GitHub Actions jobs and creates a Hetzner Cloud server for each one. The server registers as an ephemeral runner, powers off when the job completes, and is then deleted or recycled. It needs only a classic GitHub token and a Hetzner Cloud token: there are no webhooks, no GitHub App and no Kubernetes.
Job labels select the server type, image, location and network, and both x64 and arm64 servers are supported. Because Hetzner bills by the hour, powered-off servers are recycled by default and rebuilt from their image for the next job. Standby pools, persistent caching volumes, cost estimation, Prometheus metrics and an embedded dashboard are included. TestFlows presents a figure of up to 33× cheaper than GitHub-hosted runners as an upper bound (vendor claim). The README lists Altinity’s ClickHouse builds among its users.
Notable
- Release 1.10.260921.1182403 was published on 21 September 2026
- Persistent caching volumes were added in version 1.9, according to the README
- The README lists Altinity’s ClickHouse builds and regression tests as users
TestFlows GitHub Hetzner Runners specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux |
| Architectures | x64, arm64 |
| Deployment | Open-source project |
| Where it can run | Hetzner |
| Isolation | 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 |
| Hardware | Any Hetzner Cloud server type, image and location, selected with job labels |
| Performance (vendor claim) | Not documented |
| Runner sizes | Not documented |
| Caching | 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 | Yes |
| GPU | Not documented |
| Concurrency | A maximum number of runners can be set, as can a limit per workflow run |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Yes |
| Observability | Prometheus metrics endpoint and an embedded dashboard showing cost per hour, servers, runners, queued and running jobs, scale-up errors and logs |
| Setup | pip install testflows.github.hetzner.runners, then supply a classic GitHub token, the repository and a Hetzner Cloud token. Run the service locally or deploy it to a Hetzner instance with github-hetzner-runners cloud deploy. |
| Example label | [self-hosted, type-cpx22] |
| Pricing | 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 |
| Compliance | Not documented |
| Regions | Not documented |
| Open source | Yes (Apache-2.0) |
| Company headquarters | Not documented |
Facts from TestFlows GitHub Hetzner Runners’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- 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
- You want to SSH into a runner server with a single command when debugging
Trade-offs
- Group runners are not supported
- A unique Hetzner Cloud project must be used for each repository
- A classic GitHub token is required; fine-grained tokens are not supported
- The README says manual monitoring is required to make sure servers are cleaned up and costs stay under control
Good fit for: Single-repository projects that want low-cost x64 or arm64 GitHub Actions runners on Hetzner Cloud with very little setup.
Use cases TestFlows GitHub Hetzner Runners fits
- Lower CI cost: TestFlows presents Hetzner Cloud servers as up to 33× cheaper than GitHub-hosted runners at full hourly utilisation (vendor claim).
- Docker builds: Runners are full VMs with Docker preinstalled, and caching volumes can hold Docker data between jobs.
- ARM64 builds: Hetzner arm64 server types are supported alongside x64.
- Your own cloud: Servers are created in your own Hetzner Cloud project.
- Open source and self-hosted: The service is Apache-2.0 licensed and installed from PyPI.
How TestFlows GitHub Hetzner Runners compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
| terraform-aws-github-runner | GitHub Actions | Linux, Windows, macOS, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| 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 |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Fireactions | GitHub Actions | Linux, x64, arm64 | Self-hosted | Firecracker microVM | Free software + your infrastructure | Set by your infrastructure | Not documented | No | Yes | Lithuania |
| 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 |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
Head-to-head: Fireactions vs TestFlows GitHub Hetzner Runners · GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners · terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners · TestFlows GitHub Hetzner Runners vs Ubicloud Runners
Frequently asked questions
What is TestFlows GitHub Hetzner Runners?
Which CI systems does TestFlows GitHub Hetzner Runners work with?
How does TestFlows GitHub Hetzner Runners isolate jobs?
Is TestFlows GitHub Hetzner Runners open source?
How much does TestFlows GitHub Hetzner Runners cost?
How do you set up TestFlows GitHub Hetzner Runners?
[self-hosted, type-cpx22].Does TestFlows GitHub Hetzner Runners support ARM64 runners?
Does TestFlows GitHub Hetzner Runners cache Docker layers?
How many jobs can run at once on TestFlows GitHub Hetzner Runners?
What are the alternatives to TestFlows GitHub Hetzner Runners?
Sources
- 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
- github.com/testflows/TestFlows-GitHub-Hetzner-Runners/wiki/Using-Caching-Volumes
- github.com/testflows/TestFlows-GitHub-Hetzner-Runners/wiki/Opening-The-SSH-Client-To-The-Server
- testflows.com/
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). TestFlows GitHub Hetzner Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/github-hetzner-runners/