Runners for GitHub Actionss
Runners are the machines that execute workflow jobs. GitHub-hosted runners are fresh virtual machines for Linux, Windows and macOS, billed or limited by plan. Self-hosted runners are machines you manage yourself, which allow custom hardware, private network access and caching, but need maintenance and careful security.
Stage: Runners and Deployment · Part of the GitHub Actions roadmap · Last reviewed 19 November 2026
What to learn in Runners
- Pick a runs-on label for Linux, Windows or macOS jobs
- Register a self-hosted runner and use labels to target it
- Explain the security risks of self-hosted runners on public repositories
- Group runners and restrict which repositories can use them
- Estimate minutes and cost for a heavily used workflow
Runners interview questions
When would you choose a self-hosted runner?
Choose one when you need special hardware such as GPUs, access to private network resources, specific software preinstalled, or lower cost at high volume. You must handle updates, scaling and isolation yourself.
Why are self-hosted runners risky for public repositories?
A pull request from a fork can run workflow code on your machine. Since self-hosted runners are not always clean and may sit inside your network, malicious code could persist or reach internal systems. Use ephemeral runners and restrict fork workflows.
Where Runners fits in the GitHub Actions roadmap
Runners belongs to the Runners and Deployment stage (beginner level). Run and ship.
Other units in this stage
Back to the full GitHub Actions roadmap