CI runner guides
Answer in brief
Start with What is a CI runner? if you are new to the topic, then use the buyer’s checklist and the comparison table to shortlist providers.
- GuideWhat is a CI runner?A plain-English explanation of CI runners: what they do, how they connect to GitHub Actions or GitLab CI, and the kinds you can choose from.
- GuideHow third-party GitHub Actions runners workHow drop-in GitHub Actions runners work: the GitHub App, the runs-on label, just-in-time ephemeral runners, caching, and what the vendor can see.
- GuideHow to choose a CI runner: a buyer’s checklistA step-by-step checklist for choosing a CI runner: CI system, platforms, deployment, isolation, caching, price, limits and how to run a fair trial.
- GuideCI runner pricing explainedHow CI runners are priced: per-minute rates by size and OS, free allowances, rounding, cache and storage charges, and the real cost of your own cloud.
- GuideCI runner security: a practical guideHow to secure CI runners: ephemeral runners, isolation boundaries, public-repository risk, secrets and OIDC, cache poisoning and network egress control.
- GuideDocker layer caching in CI, explainedWhy Docker builds are slow on ephemeral CI runners and how to fix it: registry and GitHub cache backends, persistent layer caches and native multi-arch.
- GuideSelf-hosting GitHub Actions runners: the optionsHow to run your own GitHub Actions runners: Actions Runner Controller on Kubernetes, cloud VM autoscalers, Firecracker managers and BYOC products.
- GuidemacOS CI runners explainedHow macOS CI runners work and why they cost more: Apple hardware and licence rules, hosted versus dedicated Macs, virtualization and image upkeep.
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.