CI Bench

Head to head · CI Bench v1

RunsOn vs GitHub-hosted (ubuntu-latest)

RunsOn ran jobs 1.2× faster than GitHub-hosted runners (ubuntu-latest, 2 vCPU) (95% interval 1.2× to 1.2×); RunsOn cost 88% less per job (at 100,000 jobs a month).

Self-hosted options spread fixed monthly costs over the monthly volume, so their cost per job changes with it; see the volume table.

Speed

× faster than GitHub-hosted (ubuntu-latest) · higher is better
RunsOn
1.2×
GitHub-hosted (ubuntu-latest)
1.0×

Cost per job

USD per $1.00 spent on GitHub-hosted (ubuntu-latest), at 100,000 jobs a month · lower is better
RunsOn
$0.12
GitHub-hosted (ubuntu-latest)
$1.00

Workload by workload

RunsOn had the lowest median time of the two on 11 of 12 workloads, GitHub-hosted (ubuntu-latest) on 1.
WorkloadRunsOnGitHub-hosted runners (ubuntu-latest, 2 vCPU)Lowest median
Burst: 20 jobs at once177 s259 sRunsOn
cli327 s368 sRunsOn
codex-lint623 s884 sRunsOn
container174 s239 sRunsOn
fd89 s92 sRunsOn
flask38 s23 sGitHub-hosted runners (ubuntu-latest, 2 vCPU)
guava897 s1167 sRunsOn
monorepo288 s384 sRunsOn
pydantic147 s179 sRunsOn
ts570 s784 sRunsOn
vite437 s603 sRunsOn
vue101 s121 sRunsOn

Cost by volume

Mean cost per job in USD, from the benchmark’s sensitivity results
VolumeRunsOnGitHub-hosted runners (ubuntu-latest, 2 vCPU)
100,000 jobs a month$0.121$1.000
10,000 jobs a month$0.250$1.000
1,000 jobs a month$1.431$1.000

Failed runs

Counted, never replaced
RunsOn
1 of 360 measured runs (0.3%)
GitHub-hosted runners (ubuntu-latest, 2 vCPU)
3 of 360 measured runs (0.8%)

Each configuration page lists where its failures happened. All losses.

All results for this pair

One line per configuration pairing, generated from the benchmark data