Latchkey Learn

GitHub Actions runners compared

Neutral comparisons of GitHub Actions runner vendors, alternatives to GitHub-hosted and self-hosted runners, and migration guides. Prices are read from each vendor's public page on a stated date.

Start here four stops, in order

Contents 5 sections · 63 entries

Vendor vs vendor 24 entries

Head-to-head comparisons with a fixed table.

Alternatives and roundups 11 entries

Every vendor in one table, ranked by the criterion you care about.

Migration guides 9 entries

Moving off a vendor, with the YAML diff and a checklist.

3.1Migrate from CodeBuild runners
3.2Migrate from Actions Runner Controller
3.3Migrate from Cirrus CI
3.4Migrate from Blacksmith
3.5Migrate from BuildJet
3.6Migrate from Depot
3.7Migrate from Namespace runners
3.8Migrate from self-hosted runners
3.9Migrate from WarpBuild

Hosted, self-hosted, managed 11 entries

The three ways to run Actions, compared.

Vendor explainers 8 entries

What each vendor is, costs, and does well.

Explore other topics

GitHub Actions costWhat Actions really costs, and how to cut it. Runner failures Latchkey repairsOut of memory, disk full, rate limits, lost runners: reproduced and fixed. GitHub Actions workflow errorsWorkflow, YAML, permissions and artifact errors, diagnosed and fixed. Docker in CI: Registry, Build & RuntimeRegistry, runtime and build errors on CI runners. Faster GitHub ActionsCaching, parallelism and cold starts, measured. CI for coding agentsGive your coding agent a runner.