What are GitHub Actions self-hosted runners, and why might an organization choose them over GitHub-hosted runners?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Self-hosted runners are your own machines enrolled in GitHub Actions. You get total control: custom software, internal network access, specific hardware, no per-minute billing. Perfect when the GitHub-hosted runners can't reach your internal databases or need specialized tools.
Full explanation below image
Full Explanation
GitHub Actions provides two runner types: GitHub-hosted runners (managed by GitHub, ephemeral, various OS options) and self-hosted runners (machines you own and manage that connect to GitHub to receive and execute workflow jobs). Organizations choose self-hosted runners for: (1) Access to internal networks/resources that GitHub-hosted runners cannot reach (databases, internal APIs), (2) Custom software, specific hardware (GPUs, specialized tools), (3) Cost optimization for long-running jobs (no per-minute charges), (4) Compliance requirements around where code executes. Self-hosted runners can be configured at repository, organization, or enterprise level. They are NOT a premium GitHub tier and are NOT containers GitHub provisions.