CI Bench

Comparison · Result set v1 · Measured Oct 7–11, 2026

Alternatives to GitHub-hosted runners, measured

8 configurations compared with GitHub-hosted (ubuntu-latest) on 12 real CI workloads: speed, cost per job at three volumes, and what each one is.

All alternatives, against GitHub-hosted (ubuntu-latest)

Alternatives to GitHub-hosted runners
RankConfigurationTypeSpeedCost per job at 10,000 jobs a monthList price per minuteFailed runs
1Vitko Runners (warm starts + test splitting)VitkoManaged2.3x faster84% lower$0.002 a minute3 of 360
2Vitko RunnersVitkoManaged1.7x faster84% lower$0.002 a minute0 of 360
3GitHub-hosted larger runner (4 vCPU)Managed1.6x faster39% higher$0.012 a minute3 of 360
4BlacksmithManaged1.6x faster52% lower$0.004 a minute3 of 360
5Self-hosted runners on Google CloudSelf-hosted1.5x faster59% loweryour cloud bill1 of 360
6RunsOnSelf-hosted1.2x faster75% loweryour cloud bill1 of 360
7Self-hosted runners on AWS (one VM per job)Self-hosted1.2x faster60% loweryour cloud bill0 of 360
8UbicloudManaged1.1x faster83% lower$0.00125 a minute1 of 360

Managed services bill per minute or per second; self-hosted options run in your own cloud account and are priced all-in, with fixed monthly costs spread over the volume. The head-to-head pages show each pair in detail, workload by workload.

Head to head: Vitko Runners vs Blacksmith · Vitko Runners vs Ubicloud · Vitko Runners vs RunsOn · Vitko Runners vs Self-hosted runners on AWS · Vitko Runners vs Self-hosted runners on Google Cloud · Vitko Runners vs GitHub-hosted larger runner (4 vCPU) · Vitko Runners vs GitHub-hosted (ubuntu-latest) · Blacksmith vs GitHub-hosted (ubuntu-latest).

More: speed ranking · cost ranking · alternatives to GitHub-hosted · monorepo workload · self-hosted vs managed · list prices · free minutes · alternatives to Blacksmith, RunsOn, Ubicloud.

Maintained by Vitko, Inc., which sells one of the products measured. Measured October 7 to 11, 2026 (result set v1); page generated October 27, 2026. Every number comes from results.json; the workflows and every raw job record are in the repository, and the method says how the runs were made.