What is self-hosted runner?
A runner on a machine you (or a vendor acting for you) operate, registered with the CI system to pick up jobs in place of the platform’s hosted runners.
Self-hosted runner in CI
A self-hosted runner is the runner application installed on a machine the CI platform does not own: a cloud instance, a Kubernetes pod, a Mac mini under a desk. It registers with a repository, organisation or group, opens an outbound connection to the CI service and waits for jobs that match its labels. No inbound firewall port is needed.
To the CI platform, every third-party runner is a self-hosted runner. Managed vendors, bring-your-own-cloud products and open-source autoscalers all use this same mechanism; they differ in who operates the machine and where it sits. The security caveat is the same too: a persistent self-hosted runner keeps state between jobs, so prefer ephemeral runners.
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). What is self-hosted runner?. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/glossary/self-hosted-runner/