GitHub-hosted runners vs runners.io: a GitHub Actions runner alternative
Both run your GitHub Actions jobs on a machine you do not manage, and the workflow stays in GitHub. A job moves by its runs-on label. Here are the two side by side, from GitHub’s own documentation, including the rows where GitHub is ahead.
Card required. 3,000 minutes a month at 2 vCPU are included.
Side by side
| Row | runners.io | GitHub-hosted |
|---|---|---|
| Price a minute | ||
| 2 vCPULinux x64, a minute | $0.004 | $0.006Standard runner1 |
| 4 vCPULinux x64, a minute | $0.008 | $0.012Larger runner1 |
| 8 vCPULinux x64, a minute | $0.016 | $0.022Larger runner1 |
| 16 vCPULinux x64, a minute | $0.032 | $0.042Larger runner1 |
| 32 vCPULinux x64, a minute | $0.064 | $0.082Larger runner1 |
| 2 vCPU ARM64Linux arm64, a minute | $0.004 | $0.0051 |
| 2 vCPU WindowsWindows Server x64, a minute | $0.010 | $0.0101 |
| Billing | ||
| Included each month | 3,000 run-minutesCard required | A dollar amount by planFree $12, Pro $18, Team $18, Enterprise Cloud $300 a month.2 |
| Larger and other machinesHow they use what is included | Run-minutes at each label's weightA 2 vCPU Linux minute is 1 run-minute; 4 vCPU uses 2, 2 vCPU ARM64 1 and 2 vCPU Windows 2.5. | Each runner's own rate, in dollarsNo minute multiplier is published. A larger runner may draw on the included amount on Team and Enterprise Cloud.2 |
| Public repositories | Billed like any otherOne with at least 500 stars runs free in our open-source program, for a badge in its README. | Standard runners are free. Larger runners are billed.2 |
| Limit what you spend | A monthly spending cap you set stops new jobs; running ones finish. | With a payment method on file, budgets can limit spending.2 |
| The machine | ||
| MemoryOn the 2 vCPU Linux runner | 7 GB | 8 GB3 |
| DiskOn the 2 vCPU Linux runner | 50 GB | 14 GB3 |
| Largest Linux x64 size | 32 vCPU | 96 vCPU5 |
| Concurrent jobs | 8 jobs | 20–500 by plan; 1,000 on larger runners4 |
| A fresh virtual machine per job | Its own virtual machine, starting fresh and shared with no other job. Nothing a job leaves on its machine can be seen by another job. | A new VM per job, except single-CPU runners, which get a container.3 |
| Features | ||
| Actions cache | Included. Not metered. | 10 GB per repository by default; more is billed.2 |
| Docker layer cache | $0.50/GB-month. | Not publishedNo managed layer cache published.3 |
| Sticky disk | $0.50/GB-month, billed on what you use. Reclaimed after 7 days idle. | Not publishedNo persistent runner disk published.3 |
| Nested virtualisationKVM inside the job, for Android emulators. Docker works on both | No /dev/kvm in the guest. Docker containers are unaffected. | KVM on Linux runners, for hardware-accelerated Android emulation.6 |
| GPU runners | GPU-enabled larger runners.5 | |
| A terminal into a running job | A terminal in your browser on a running Linux or Windows Server job, off until an owner or admin switches it on. They can limit it to the person who triggered the job. Fifteen minutes at most. | Not publishedNo first-party feature published.3 |
Sources
Our column is read from the rates that bill each size and from our own documentation. GitHub’s column is read from GitHub’s documentation, each page on the day given. Where GitHub’s documentation does not say, the cell reads “Not published”. A GitHub plan’s per-seat fee is left out of both columns: it is paid whichever runner a job uses.
- Actions runner pricing, docs.github.com, read 19 November 2026.
- GitHub Actions billing, docs.github.com, read 19 November 2026.
- GitHub-hosted runners reference, docs.github.com, read 19 November 2026.
- Actions limits, docs.github.com, read 19 November 2026.
- Larger runners reference, docs.github.com, read 19 November 2026.
- Changelog: hardware-accelerated Android virtualization on 2-vCPU Linux runners, github.blog, read 19 November 2026.
The sizes and the bill
Every size, its label and its rate, for Linux x64, ARM64 and Windows, is on the runners page. What is included, the spending cap and the add-ons are on the pricing page. Every comparison we publish is on the comparisons page.
Move one repository and compare
Change one line, watch your own build, then decide.
Card required. 3,000 minutes a month at 2 vCPU are included.