GitHub-hosted runners vs Ubicloud Runners
GitHub-hosted runners suits teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. 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. GitHub-hosted runners is the CI platform’s own hosted runners for GitHub Actions, priced at $0.006/min; Ubicloud Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.00125/min.
Key differences between GitHub-hosted runners and Ubicloud Runners
- Type: GitHub-hosted runners is the CI platform’s own hosted runners; Ubicloud Runners is a managed service hosted by the vendor.
- Operating systems: Only GitHub-hosted runners documents macOS and Windows.
- Isolation: GitHub-hosted runners: Fresh VM. Ubicloud Runners: KVM VM.
- Published price: $0.006/min (GitHub-hosted runners) versus $0.00125/min (Ubicloud Runners).
- Largest runner: 96 vCPU / 384 GB (GitHub-hosted runners) versus 30 vCPU / 120 GB (Ubicloud Runners).
- Open source: Ubicloud Runners is open source (AGPL-3.0); GitHub-hosted runners is not.
- Self-hosting: Ubicloud Runners documents a self-hosted option; GitHub-hosted runners does not.
What they have in common
- Both companies are based in the United States.
- 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.
GitHub-hosted runners vs Ubicloud Runners at a glance
| Attribute | GitHub-hosted runners | Ubicloud Runners |
|---|---|---|
| What it is | GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute. | Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal. |
| Type | First-party hosted runners | Managed runner service |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each job runs in a new virtual machine hosted by GitHub; the 1-vCPU ubuntu-slim runner instead runs in an unprivileged container on a shared VM | 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 |
| Fresh environment per job | Yes | Yes |
| Hardware | Azure virtual machines, with eligible 2-core and 4-core Linux jobs also scheduled on AWS; standard macOS runners are 3-core M1 or 4-core Intel, and the macOS XLarge runner is a 5-core M2 | Standard 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 documented | 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) |
| Runner sizes | Standard: 1 vCPU / 5 GB (ubuntu-slim); 2 vCPU / 8 GB in private and 4 vCPU / 16 GB in public repositories on Linux and Windows, x64 and arm64. Larger runners: 2 to 96 vCPU on x64 and 2 to 64 vCPU on arm64; macOS 3 to 12 cores | 2 to 30 vCPU with 8 to 120 GB RAM on x64; 2 to 30 vCPU with 6 to 90 GB on arm64 |
| Caching | Dependency caching through the cache action, with 10 GB per repository included; entries not accessed for 7 days are removed and the oldest are evicted at the limit. The limit can be raised, billed at $0.07 per GB per month. Larger runners can use custom VM images. | 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 caching | Not documented | Yes |
| GPU | GPU larger runners have 4 vCPU, 28 GB RAM and one Tesla T4 with 16 GB VRAM, at $0.052/min on Linux and $0.102/min on Windows. | Not documented |
| Concurrency | Standard runners: 20 concurrent jobs on Free, 40 on Pro, 60 on Team and 500 on Enterprise, of which 5 macOS (50 on Enterprise). Larger runners: up to 1,000 concurrent jobs and 100 GPU jobs | Not documented |
| Static IPs | Yes | Not documented |
| SSH into running jobs | Not documented | Yes |
| Pricing | Private repositories, per minute: Linux 2-core x64 $0.006, Linux 2-core arm64 $0.005, Linux 1-core $0.002, Windows 2-core $0.010, macOS 3- or 4-core $0.062. Larger Linux x64 runners run from $0.012 (4-core) to $0.252 (96-core); larger macOS runners are $0.077 (12-core Intel) and $0.102 (M2 Pro). Usage is rounded up to the whole minute. | 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 tier | Standard runners are free in public repositories. Private repositories get $12 of included compute usage per month on GitHub Free, $18 on Pro and Team, and $300 on Enterprise Cloud | $2.5/month credit, which Ubicloud equates to 1,250 runner minutes |
| Open source | No | Yes (AGPL-3.0) |
| Self-host / your cloud | No / No | Yes / Not documented |
| Compliance | Not documented | SOC 2 Type 2 report available through the Trust Center; GDPR data processing agreement offered |
| Regions | Regions are not documented for github.com. GitHub says Windows runners and other Linux runners run on Microsoft Azure, eligible Linux jobs on Azure or AWS, and macOS runners in Azure data centers | Europe 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 headquarters | San Francisco, California, United States | San Francisco, California, United States |
| Good fit for | Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners | Teams 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 GitHub-hosted runners
- You want runners that need no installation or account beyond GitHub itself
- You maintain public repositories, where standard runners are free
- You need Linux, Windows and macOS, on x64 and arm64, from one provider
- You want every job to start in a clean VM that is not reused
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
- GitHub-hosted runners: Larger runners are billed in public repositories and need a GitHub Team or Enterprise Cloud plan
- GitHub-hosted runners: Jobs are limited to 6 hours of execution time
- 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 GitHub-hosted runners profile and Ubicloud Runners profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs GitHub-hosted runners
- Blacksmith vs GitHub-hosted runners
- Depot GitHub Actions Runners vs GitHub-hosted runners
- GitHub-hosted runners vs GitLab-hosted runners
- GitHub-hosted runners vs Namespace
- GitHub-hosted runners vs WarpBuild
- Blacksmith vs Ubicloud Runners
- Depot GitHub Actions Runners vs Ubicloud Runners
- Namespace vs Ubicloud Runners
- TestFlows GitHub Hetzner Runners vs Ubicloud Runners
- Ubicloud Runners vs WarpBuild
Frequently asked questions
Is GitHub-hosted runners or Ubicloud Runners better?
What is the difference between GitHub-hosted runners and Ubicloud Runners?
Which is open source, GitHub-hosted runners or Ubicloud Runners?
How do GitHub-hosted runners and Ubicloud Runners isolate jobs?
How does GitHub-hosted runners pricing compare with Ubicloud Runners?
Is GitHub-hosted runners or Ubicloud Runners faster?
Do GitHub-hosted runners and Ubicloud Runners cache Docker layers?
Do GitHub-hosted runners and Ubicloud Runners offer GPU runners?
Where do GitHub-hosted runners and Ubicloud Runners runners run?
Sources
- docs.github.com/en/billing/reference/actions-runner-pricing
- docs.github.com/en/billing/concepts/product-billing/github-actions
- docs.github.com/en/actions/reference/runners/github-hosted-runners
- docs.github.com/en/actions/reference/runners/larger-runners
- ubicloud.com/use-cases/github-actions
- ubicloud.com/docs/about/pricing
- ubicloud.com/docs/github-actions-integration/quickstart
- 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). GitHub-hosted runners vs Ubicloud Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/github-hosted-runners-vs-ubicloud/