actions-runner-controllervsruns-on
Two self-hosted CI/CD projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| actions-runner-controller | runs-on | |
|---|---|---|
| Score | 71/100 | 57/100 |
| Rank in category | #6 of 28 in CI/CD | #15 of 28 in CI/CD |
| GitHub stars | 6 680 | 1 428 |
| Stars, last 30 days | +102 | +61 |
| Stable releases, 12 months | 6 | 25 |
| Latest release | gha-runner-scale-set-0.15.1 · 23 Oct 2026 | v3.6.2 · 13 Nov 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | — |
Which one should you pick?
actions-runner-controller scores 71/100 against 57/100 for runs-on, so it is the safer default.
runs-on ships more often: 25 stable releases in the past year, against 6 for actions-runner-controller.
If you want the quickest setup, runs-on is easier to run; actions-runner-controller needs more configuration.
Key differences
- License: actions-runner-controller is Apache-2.0, runs-on is MIT.
- Features only actions-runner-controller lists: Autoscaling runner scale sets, Custom volumes support, Ephemeral container-based runners, GitHub App Authentication and 5 more.
- Features only runs-on lists: Approved runner catalog (Fleet), Bring your own AMI, Build caching, Cost control and budgets and 11 more.
actions-runner-controller details →runs-on details →All CI/CD projects →