GitHub-hosted Runners
What you'll learn: You'll discover what GitHub-hosted runners are, the operating systems available, and their computational specifications so you can choose the right environment for your workflows.
What Are GitHub-hosted Runners?
GitHub-hosted runners are virtual machines managed entirely by GitHub that execute your workflow jobs. Think of them as temporary, pre-configured computers that GitHub spins up on-demand when your workflow triggers, runs your steps, then disappears afterward. You don't manage the infrastructure—GitHub handles provisioning, maintenance, and cleanup.
When you define a job in your workflow file without specifying runs-on: self-hosted, you're using GitHub's infrastructure.
Available Operating Systems
GitHub provides runners with three major operating systems:
- Ubuntu Linux (latest, 22.04, 20.04)
- Windows Server (latest, 2022, 2019)
- macOS (latest, 13, 12, 11)
Each OS comes pre-installed with common development tools, runtimes, and utilities relevant to that platform—similar to a developer's fresh workstation setup.
Compute Specifications
Standard GitHub-hosted runners provide:
- 2-core CPU (x86_64 architecture)
- 7 GB RAM
- 14 GB SSD storage
These specs suit most CI/CD tasks like building applications, running tests, and deploying artifacts. For resource-intensive operations (like large compilations or heavy integration tests), you'll need to consider performance implications or explore larger runners (available on paid plans).
Why This Matters
Understanding runner capabilities helps you design efficient workflows. You know immediately whether your build will fit memory constraints, which OS to target for platform-specific tasks, and that you have a clean environment every time—no leftover artifacts from previous runs.
Key Takeaway: GitHub-hosted runners are managed virtual machines with Ubuntu, Windows, or macOS that provide 2 cores, 7 GB RAM, and 14 GB storage—perfect for automated builds and tests without infrastructure overhead.