Self-Hosted Runner
ELI5 — The Vibe Check
A self-hosted runner is your own machine running CI/CD jobs instead of GitHub's cloud machines. Need GPU access? Special hardware? Network access to internal services? Slap a runner agent on your server and GitHub Actions sends it work. Your machine, their orchestration.
Real Talk
Self-hosted runners are machines you manage that execute GitHub Actions jobs. They provide custom hardware, pre-installed software, network access to private resources, and persistent environments. Runners register with GitHub and poll for jobs, running them locally.
When You'll Hear This
"Our ML pipeline runs on a self-hosted runner with 4 GPUs." / "We use self-hosted runners for builds that need access to our private network."
Related Terms
Buildkite
Buildkite is CI/CD for teams who want full control. The orchestration is in the cloud, but your builds run on YOUR machines.
GitHub Actions
GitHub Actions is CI/CD built right into GitHub. Push code, run tests, deploy — all from YAML files in your repo. No separate CI server needed.
GitHub Environments
GitHub Environments are like VIP rooms for your deployments.
Jenkins
Jenkins is the grandpa of CI/CD tools. It's been building code since 2011 and has a plugin for literally everything.