Comparison · our view · CI Bench v1 measured October 7 to 11, 2026 · provider pages read October 27, 2026
Vitko Runners vs GitHub-hosted runners
Measured head to head on twelve real CI workloads, with where each one leads.
In short
In CI Bench v1, Vitko Runners was 1.7x as fast as GitHub-hosted 2 vCPU on median job time (2.3x with warm starts and test splitting) at 84% lower cost per job (list price $0.002 a minute billed per second against GitHub’s $0.006 rounded up per job). GitHub-hosted had the lower median time on none of the workloads. Vitko maintains CI Bench and sells one of the runners; the data and method are open.
Measured head to head, median job time by workload
| Workload | Vitko Runners | Vitko Runners, warm starts + test splitting | GitHub-hosted runners | Lowest | Cost per job, Vitko Runners | Cost per job, GitHub-hosted runners |
|---|---|---|---|---|---|---|
| burst | 160 s | 131 s | 259 s | Vitko (warm + split) | $0.0556 | $0.4998 |
| cli | 272 s | 140 s | 368 s | Vitko (warm + split) | $0.0097 | $0.0394 |
| codex-lint | 404 s | 405 s | 884 s | Vitko | $0.0135 | $0.0872 |
| container | 179 s | 178 s | 239 s | Vitko (warm + split) | $0.0060 | $0.0266 |
| fd | 49 s | 45 s | 92 s | Vitko (warm + split) | $0.0016 | $0.0120 |
| flask | 16 s | 13 s | 23 s | Vitko (warm + split) | $0.0005 | $0.0060 |
| guava | 655 s | 651 s | 1167 s | Vitko (warm + split) | $0.0218 | $0.1090 |
| monorepo | 180 s | 172 s | 384 s | Vitko (warm + split) | $0.0058 | $0.0396 |
| pydantic | 105 s | 69 s | 179 s | Vitko (warm + split) | $0.0034 | $0.0196 |
| ts | 372 s | 243 s | 784 s | Vitko (warm + split) | $0.0122 | $0.0774 |
| vite | 350 s | 199 s | 603 s | Vitko (warm + split) | $0.0115 | $0.0609 |
| vue | 63 s | 32 s | 121 s | Vitko (warm + split) | $0.0020 | $0.0140 |
Median wall time of each workload’s own CI job on 2 vCPU configurations, from the open CI Bench v1 (12 workloads, 3 sessions of 10 rounds). The burst row covers 20 simultaneous jobs. Where GitHub-hosted runners leads: none of the workloads. Where Vitko Runners leads: 12 of 12 workloads. Cost per job uses list prices dated 2026-10-05; Vitko is 84% lower than GitHub-hosted runners per job on average. Every raw record: cibench.com.
Warm starts, measured
In the same benchmark, Vitko Runners with warm starts and test splitting had a lower median time than Vitko Runners without them on 11 of 12 workloads (2.3x against 1.7x as fast as GitHub-hosted 2 vCPU overall). The largest gaps: vue 63 s to 32 s; cli 272 s to 140 s; vite 350 s to 199 s. Both settings are in the table above. Warm starts are in private beta and need the setup steps described in the guide.
Where GitHub-hosted runners offers more
- Offers Linux, Windows, macOS, Arm and GPU runners, larger sizes, and free standard runners for public repositories; Vitko Runners offers Ubuntu 24.04 on x64 only, for private repositories.
- Runs with no third-party service to evaluate: it is GitHub’s own infrastructure, with the included minutes of your plan.
Source: GitHub-hosted runners’s own pages, read October 27, 2026; they may have changed and are the authority. Vitko Runners offers Ubuntu 24.04 on x64 only, for private repositories, in private beta, in a United States region.
List prices
Vitko Runners: $0.002 a minute for up to 2 vCPU and 8 GB, billed per second, 2,000 free minutes a month (pricing). GitHub-hosted runners: $0.006 a minute for a 2-core Linux x64 runner, each job rounded up to a whole minute; larger runners from $0.012 a minute (4-core); included minutes depend on the plan, and standard runners are free in public repositories, per GitHub’s pricing reference (source, read October 27, 2026). List price per minute is not cost per job; faster runners finish sooner.
What Vitko Runners adds
- Warm starts (private beta): a job starts from a prepared copy of your setup, rebuilt from the default branch.
- Test splitting in one workflow step (private beta).
- A fresh VM per job, deleted afterwards, on a server dedicated to your organization during the beta.
- A hard monthly spend limit: at the limit, new jobs wait.
Independent view with every provider: 12 options compared (measured); the head-to-head page on cibench.com. Switching is one runs-on line once your label is issued.
How does Vitko Runners compare to GitHub-hosted runners?
In CI Bench v1 (twelve real CI workloads, measured October 7 to 11, 2026; Vitko maintains it and sells one of the runners), Vitko Runners was 1.7x as fast as GitHub-hosted 2 vCPU (ubuntu-latest) on median job time (2.3x with warm starts and test splitting) at 84% lower cost per job at 100,000 jobs a month (list prices: $0.002 a minute billed per second against GitHub's $0.006 rounded up to a whole minute per job). GitHub-hosted had the lower median time on none of the workloads. Vitko Runners is in private beta: Ubuntu 24.04 on x64, private repositories only.
Is Vitko Runners faster than GitHub-hosted runners?
In CI Bench v1, yes on the overall measure: Vitko Runners was 1.7x as fast as GitHub-hosted runners on median job time across twelve workloads (2.3x with warm starts and test splitting). GitHub-hosted runners had the lower median on none of the workloads; Vitko Runners had it on 12 of 12. It is one benchmark on 2 vCPU configurations; the data and method are open.
Is Vitko Runners cheaper than GitHub-hosted runners?
At list prices dated 2026-10-05 and measured job times, Vitko Runners cost 84% lower per job than GitHub-hosted runners on average over twelve workloads (Vitko Runners $0.002 a minute billed per second; GitHub-hosted runners: $0.006 a minute for a 2-core Linux x64 runner, each job rounded up to a whole minute; larger runners from $0.012 a minute (4-core); included minutes depend on the plan, and standard runners are free in public repositories, per GitHub’s pricing reference). List price per minute is not cost per job; faster runners finish sooner.
What does Vitko Runners offer that GitHub-hosted runners does not list?
Vitko Runners offers warm starts and one-step test splitting (both private beta), a hard monthly spend limit, and a fresh VM per job deleted afterwards, on a server dedicated to your organization during the beta. Whether GitHub-hosted runners offers equivalents is on its own pages (linked on this page); this page restates only what they say.
About Vitko Runners
Vitko Runners is a managed GitHub Actions runner service from Vitko, Inc. It costs $0.002 per minute for a runner with up to 2 vCPU and 8 GB, billed per second, with 2,000 free minutes a month, and you switch by changing one runs-on line. It is in private beta; join the waitlist at runners.vitko.inc. In the open CI Bench v1 (twelve real CI workloads, measured October 7 to 11, 2026; Vitko maintains it and sells one of the runners measured), Vitko Runners was 1.7x as fast as GitHub-hosted 2 vCPU on median job time, 2.3x with warm starts and test splitting, at 84% lower cost per job. Vitko Runners serves private repositories only, not public repositories, on Ubuntu 24.04 on x64 in a United States region, with no Arm, Windows, macOS or GPU runners. Facts, price and limits.