Larger runners without the larger-runner price.
GitHub bills its larger runners by the minute, by size, and in public repositories too. Here is its rate for each size next to ours, both read from the rate cards.
Card required. 3,000 minutes a month at 2 vCPU are included.
GitHub’s prices read 7 November 2026 from its runner pricing reference.
Per minute, by size
| Linux x64 | GitHub larger runner | runners.io | Less than GitHub | Memory every job gets here |
|---|---|---|---|---|
| 4 vCPU | $0.012 a minute | $0.008 a minute | 33% | 15 GB |
| 8 vCPU | $0.022 a minute | $0.016 a minute | 27% | 30 GB |
| 16 vCPU | $0.042 a minute | $0.032 a minute | 23% | 60 GB |
| 32 vCPU | $0.082 a minute | $0.064 a minute | 21% | 125 GB |
GitHub also sells 64 vCPU ($0.162 a minute) and 96 vCPU ($0.252 a minute) Linux runners. Our largest size is 32 vCPU, so there is no row of ours to put beside those. Prices are for GitHub-hosted larger runners and our runners at the same vCPU count. The shapes are not identical: the labels page lists the memory and disk of every size we sell, and the migration pull request tells you where a label you use moves to a size with less of either.
Our rates are read from the rate card that bills them, so this table moves when a price does. See pricing for the included minutes and how a minute is weighted.
The ones worth asking first
What do GitHub larger runners cost?
GitHub charges per minute and by size. On 7 November 2026, its rate reference listed 8 vCPU Linux at $0.022 a minute; ours is $0.016 a minute for the same vCPU count. The table above has every size.
Are GitHub larger runners free in public repositories?
No. GitHub's own rate reference says larger runners are not free for public repositories, where its standard runners are. Ours are billed per minute in every repository; open-source projects can apply to our open-source program.
Do I have to rewrite my workflows?
No. Change the runs-on label. The migration pull request maps a larger-runner label to a size we sell, and tells you when the memory or disk of the size it picked differs from the one you had.
Is the machine the same as GitHub's larger runner?
Not necessarily. The vCPU count matches by construction; memory and disk do not always. The memory in the table is the figure every job on that label gets, and the labels page in the documentation lists the disk.
Before you connect
Is my code safe on someone else's runner?
Each job gets 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.
What do you get from my GitHub account?
Access to the repositories you choose, and nothing else. We read their workflow files and job logs, register a runner for each job, and open the pull request that moves them across. Your secrets, environments and branch protection stay on GitHub, and every permission is listed, with what it is for, in the docs under Connect your account.
What if I do not want to depend on a vendor?
The one change a workflow needs is the runs-on label. Your actions, secrets and triggers are untouched, so there is nothing of ours to untangle.
How do I leave?
Change the label back and the job runs on GitHub again. We delete build output and test results 90 days after each job.
Move a larger-runner job and see the bill
Card required. 3,000 minutes a month at 2 vCPU are included.