terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners
terraform-aws-github-runner suits teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero. 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. terraform-aws-github-runner 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.
Key differences between terraform-aws-github-runner and TestFlows GitHub Hetzner Runners
- Operating systems: Only terraform-aws-github-runner documents Windows and macOS.
- Isolation: terraform-aws-github-runner: EC2 instance. TestFlows GitHub Hetzner Runners: Hetzner Cloud VM.
- Licence: terraform-aws-github-runner is MIT; TestFlows GitHub Hetzner Runners is Apache-2.0.
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 use a virtual machine per runner.
- Both are open source.
- Both can be self-hosted.
terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners at a glance
| Attribute | terraform-aws-github-runner | TestFlows GitHub Hetzner Runners |
|---|---|---|
| What it is | Terraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions. | 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 | GitHub Actions |
| Operating systems | Linux, Windows, macOS | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each runner is an EC2 instance in your AWS account; by default runners are reused until they are idle, and in ephemeral mode each instance takes one job with a just-in-time configuration and is then terminated | 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 | Not documented | Yes |
| Hardware | EC2 instance types that you list, spot or on-demand, launched through the EC2 CreateFleet API; Graviton types for arm64 and EC2 Mac dedicated hosts for the experimental macOS support | 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 | With dynamic labels enabled, ghr-ec2 override labels can request EC2 instance requirements that include GPU accelerator types. | Not documented |
| Concurrency | The scale-up Lambda stops creating instances once the configured maximum number of runners is reached; an optional pool keeps a scheduled minimum of ephemeral org-level 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 (MIT) | Yes (Apache-2.0) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Not documented | Not documented |
| Good fit for | Teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero | 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 terraform-aws-github-runner
- You want runners on EC2 spot instances that scale down to zero when no workflows are active
- You manage AWS with Terraform and want the whole runner stack defined as a module
- You need Linux x64, Linux arm64 and Windows runners from one deployment through the multi-runner module
- You want to bring your own AMI, instance types and subnets
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
- terraform-aws-github-runner: Enterprise-level runners are not supported; runners are registered at organization or repository level
- terraform-aws-github-runner: The maintainers describe the project as maintained on a best-effort basis
- 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 terraform-aws-github-runner profile and TestFlows GitHub Hetzner Runners profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs terraform-aws-github-runner
- AWS CodeBuild-hosted runners vs terraform-aws-github-runner
- Cirun vs terraform-aws-github-runner
- GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner
- HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner
- RunsOn vs terraform-aws-github-runner
- ec2-github-runner vs terraform-aws-github-runner
- Fireactions vs TestFlows GitHub Hetzner Runners
- GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners
- TestFlows GitHub Hetzner Runners vs Ubicloud Runners
Frequently asked questions
Is terraform-aws-github-runner or TestFlows GitHub Hetzner Runners better?
What is the difference between terraform-aws-github-runner and TestFlows GitHub Hetzner Runners?
Which is open source, terraform-aws-github-runner or TestFlows GitHub Hetzner Runners?
How do terraform-aws-github-runner and TestFlows GitHub Hetzner Runners isolate jobs?
How does terraform-aws-github-runner pricing compare with TestFlows GitHub Hetzner Runners?
Do terraform-aws-github-runner and TestFlows GitHub Hetzner Runners cache Docker layers?
Do terraform-aws-github-runner and TestFlows GitHub Hetzner Runners offer GPU runners?
Where do terraform-aws-github-runner and TestFlows GitHub Hetzner Runners runners run?
Sources
- github.com/github-aws-runners/terraform-aws-github-runner
- github.com/github-aws-runners/terraform-aws-github-runner/releases
- github.com/github-aws-runners/terraform-aws-github-runner/blob/main/CHANGELOG.md
- github.com/github-aws-runners/terraform-aws-github-runner/blob/main/LICENSE.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). terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/terraform-aws-github-runner-vs-github-hetzner-runners/