CI Runnerscirunners.org
Head-to-head

TestFlows GitHub Hetzner Runners vs Ubicloud Runners

Answer in brief

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. Ubicloud Runners suits teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source. TestFlows GitHub Hetzner Runners is an open-source project you run yourself for GitHub Actions; Ubicloud Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.00125/min.

By the CI Runners editors · Updated

Key differences between TestFlows GitHub Hetzner Runners and Ubicloud Runners

  • Type: TestFlows GitHub Hetzner Runners is an open-source project you run yourself; Ubicloud Runners is a managed service hosted by the vendor.
  • Isolation: TestFlows GitHub Hetzner Runners: Hetzner Cloud VM. Ubicloud Runners: KVM VM.
  • Licence: TestFlows GitHub Hetzner Runners is Apache-2.0; Ubicloud Runners is AGPL-3.0.

What they have in common

  • Both run GitHub Actions jobs.
  • Both document Linux runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Both give every job a fresh environment.
  • Both are open source.
  • Both can be self-hosted.
  • Both document Docker layer caching.

TestFlows GitHub Hetzner Runners vs Ubicloud Runners at a glance

AttributeTestFlows GitHub Hetzner RunnersUbicloud Runners
What it isSelf-contained Python service that creates a Hetzner Cloud server for each queued GitHub Actions job, with no webhooks or GitHub App.Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal.
TypeOpen-source projectManaged runner service
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinuxLinux
Architecturesx64, arm64x64, arm64
IsolationEach 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 chosenEach job runs in a fresh virtual machine provisioned with Linux KVM, using Cloud Hypervisor as the virtual machine monitor; the VM and its block storage are destroyed when the job finishes
Fresh environment per jobYesYes
HardwareAny Hetzner Cloud server type, image and location, selected with job labelsStandard x64 runners use AMD EPYC 9454P (two vCPUs per physical core), premium x64 runners use AMD Ryzen 9 7950X3D, and arm64 runners use Ampere Altra Q80-30 with one physical core per vCPU; all have NVMe SSDs.
Performance (vendor claim)Not documentedUbicloud says premium runners are around 2x faster on CPU-heavy workflows and that its cache gives 4x faster downloads and 3x faster uploads (vendor claims)
Runner sizesNot documented2 to 30 vCPU with 8 to 120 GB RAM on x64; 2 to 30 vCPU with 6 to 90 GB on arm64
CachingUp 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.A transparent cache backend serves actions/cache, setup-* package caching and Docker layer caching through type=gha without workflow changes. Each repository gets 30 GB free (100 GB with premium runners enabled), entries unused for seven days are removed, and extra storage is $0.04 per GB per month on request.
Docker layer cachingYesYes
GPUNot documentedNot documented
ConcurrencyA maximum number of runners can be set, as can a limit per workflow runNot documented
Static IPsNot documentedNot documented
SSH into running jobsYesYes
PricingFree 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.Standard x64 per minute: $0.00125 (2 vCPU), $0.0025 (4), $0.005 (8), $0.01 (16) and $0.01875 (30 vCPU). Premium x64: $0.002 (2 vCPU) to $0.03 (30 vCPU). arm64 is priced the same as standard x64. Billing is per minute, and new users get premium runners by default with fallback to standard runners when premium capacity is full.
Free tierNot documented$2.5/month credit, which Ubicloud equates to 1,250 runner minutes
Open sourceYes (Apache-2.0)Yes (AGPL-3.0)
Self-host / your cloudYes / YesYes / Not documented
ComplianceNot documentedSOC 2 Type 2 report available through the Trust Center; GDPR data processing agreement offered
RegionsNot documentedEurope by default: Hetzner (Falkenstein, Germany) as the primary fleet and Leaseweb (Frankfurt), with AWS eu-central-1 as overflow; US runners are used only on explicit request
Company headquartersNot documentedSan Francisco, California, United States
Good fit forSingle-repository projects that want low-cost x64 or arm64 GitHub Actions runners on Hetzner Cloud with very little setupTeams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source

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

Which should you choose?

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

Reasons to choose Ubicloud Runners

  • You want Linux runners at $0.00125 per minute for 2 vCPU, on x64 or arm64
  • You want the underlying cloud platform to be open source and self-hostable
  • You need jobs to run in European data centers by default
  • You want existing actions/cache and type=gha Docker layer caching to work without workflow changes

Trade-offs to check first

  • TestFlows GitHub Hetzner Runners: Group runners are not supported
  • TestFlows GitHub Hetzner Runners: A unique Hetzner Cloud project must be used for each repository
  • Ubicloud Runners: Windows and macOS runners are not documented
  • Ubicloud Runners: Runner prices were raised twice in 2026, in May and September

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

More comparisons

Frequently asked questions

Is TestFlows GitHub Hetzner Runners or Ubicloud Runners better?
Neither is better for every pipeline. 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. Ubicloud Runners suits teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source.
What is the difference between TestFlows GitHub Hetzner Runners and Ubicloud Runners?
TestFlows GitHub Hetzner Runners is an open-source project you run yourself; Ubicloud Runners is a managed service hosted by the vendor. Isolation is Hetzner Cloud VM on TestFlows GitHub Hetzner Runners and KVM VM on Ubicloud Runners. TestFlows GitHub Hetzner Runners is licensed Apache-2.0; Ubicloud Runners is licensed AGPL-3.0.
Which is open source, TestFlows GitHub Hetzner Runners or Ubicloud Runners?
Both are open source (TestFlows GitHub Hetzner Runners: Apache-2.0; Ubicloud Runners: AGPL-3.0).
How do TestFlows GitHub Hetzner Runners and Ubicloud Runners isolate 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. Ubicloud Runners: Each job runs in a fresh virtual machine provisioned with Linux KVM, using Cloud Hypervisor as the virtual machine monitor; the VM and its block storage are destroyed when the job finishes.
How does TestFlows GitHub Hetzner Runners pricing compare with Ubicloud Runners?
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. Ubicloud Runners: Standard x64 per minute: $0.00125 (2 vCPU), $0.0025 (4), $0.005 (8), $0.01 (16) and $0.01875 (30 vCPU). Premium x64: $0.002 (2 vCPU) to $0.03 (30 vCPU). arm64 is priced the same as standard x64. Billing is per minute, and new users get premium runners by default with fallback to standard runners when premium capacity is full. Rates change, so check the TestFlows GitHub Hetzner Runners and Ubicloud Runners pricing pages before deciding.
Is TestFlows GitHub Hetzner Runners or Ubicloud Runners faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: TestFlows GitHub Hetzner Runners: Not documented. Ubicloud Runners: Ubicloud says premium runners are around 2x faster on CPU-heavy workflows and that its cache gives 4x faster downloads and 3x faster uploads (vendor claims).
Do TestFlows GitHub Hetzner Runners and Ubicloud Runners cache Docker layers?
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. Ubicloud Runners: A transparent cache backend serves actions/cache, setup-* package caching and Docker layer caching through type=gha without workflow changes. Each repository gets 30 GB free (100 GB with premium runners enabled), entries unused for seven days are removed, and extra storage is $0.04 per GB per month on request.
Where do TestFlows GitHub Hetzner Runners and Ubicloud Runners runners run?
TestFlows GitHub Hetzner Runners is an open-source project you run yourself (Hetzner). Ubicloud Runners is a managed service hosted by the vendor (Hetzner, Leaseweb, AWS and Bare metal).

Sources

  1. github.com/testflows/TestFlows-GitHub-Hetzner-Runners
  2. github.com/testflows/TestFlows-GitHub-Hetzner-Runners/releases
  3. github.com/testflows/TestFlows-GitHub-Hetzner-Runners/blob/main/LICENSE
  4. github.com/testflows/TestFlows-GitHub-Hetzner-Runners/wiki/Recycling-Powered-Off-Servers
  5. ubicloud.com/use-cases/github-actions
  6. ubicloud.com/docs/about/pricing
  7. ubicloud.com/docs/github-actions-integration/quickstart
  8. ubicloud.com/docs/github-actions-integration/runner-types

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