GitHub-hosted runners vs RunsOn: prices, limits and features.
GitHub-hosted runners publishes a price a minute for a 4 vCPU Linux job; RunsOn does not. Here is where they differ, from each one's own pages, plus a third option if neither fits.
The short answer
GitHub-hosted runners are the machines GitHub runs Actions jobs on, picked with labels like ubuntu-latest. RunsOn is software that runs GitHub Actions jobs on EC2 instances in your own AWS account, for a yearly license.
Pick GitHub-hosted runners if you want
- arm64, Windows, macOS: arm64, Windows and macOS (RunsOn: arm64, Windows and GPU; no macOS)
- largest size: 96 vCPU (RunsOn: 64 vCPU by default, or any EC2 family)
- free to start: $12 a month of usage on Free; standard runners free in public repos (RunsOn: 15-day trial; free for non-commercial use)
Pick RunsOn if you want
- billed by the second: Yes: AWS bills the instances by the second (GitHub-hosted runners: No)
- runs in your own cloud: Yes: it only runs in your own AWS account, which GitHub-hosted runners's pages do not state
Or Groundbox if you want
Groundbox is not ahead of both on any row below.
Where GitHub-hosted runners or RunsOn is ahead of Groundbox: arm64, Windows, macOS, largest size, runs in your own cloud.
Side by side
a rust mark means that side is ahead · each value links to its source · checked 2026-11-20
Each against Groundbox: Groundbox vs GitHub-hosted runners and Groundbox vs RunsOn. Every other comparison is on /compare.
Sources
GitHub-hosted runners
- GitHub: Actions runner pricing, checked 2026-11-19
- GitHub: Actions billing, checked 2026-11-19
- GitHub: GitHub-hosted runners, checked 2026-11-19
RunsOn
- RunsOn pricing, checked 2026-11-20
- RunsOn home page, checked 2026-11-19
- RunsOn docs: Linux runners, checked 2026-11-19