Self-hosting GitHub Actions runners: the options
To self-host GitHub Actions runners you need three things: machines, something that starts a runner for each queued job, and an image to boot. On Kubernetes, GitHub’s own Actions Runner Controller does the scaling. On cloud VMs, open-source autoscalers launch an instance per job. On bare metal, Firecracker-based managers start a microVM per job. Commercial bring-your-own-cloud products package the same pattern with support. In every case use ephemeral runners.
Why teams self-host
- Network access: jobs that must reach private registries, databases or internal APIs.
- Data control: source and secrets stay on infrastructure you operate.
- Cost: raw instance prices, spot capacity, existing credits or hardware.
- Hardware: sizes, GPUs or architectures that hosted runners do not offer.
The price is operations. Someone builds and patches the image, upgrades the controller, watches capacity and is paged when jobs stop starting.
The four patterns
| Pattern | How it scales | Good for | Watch for |
|---|---|---|---|
| Kubernetes operator | A controller creates a runner pod per queued job | Teams already running Kubernetes | Docker builds inside pods need Docker-in-Docker or a container hook; pods share the node’s kernel |
| Cloud VM autoscaler | A webhook or listener launches a cloud instance per job and terminates it afterwards | A VM boundary per job; spot pricing | Instance boot time adds to queue time unless you keep a warm pool |
| MicroVM manager on bare metal | A daemon on your servers starts a Firecracker microVM per job | Fast starts and strong isolation on hardware you own | Needs KVM-capable hosts and capacity planning |
| Bring-your-own-cloud product | A vendor’s control plane launches runners in your cloud account | The benefits above with less to build | A licence or usage fee; usually one cloud |
Actions Runner Controller and scale sets
Actions Runner Controller (ARC) is GitHub’s open-source Kubernetes operator. In its current mode it manages runner scale sets: a listener pod holds a connection to GitHub, learns how many jobs are waiting and asks the controller for that many ephemeral runner pods. Workflows target a scale set by its name in runs-on.
Each job gets a new pod, and the set can scale to zero. Because the runner is a container, a job that builds images needs Docker-in-Docker or the Kubernetes container mode, and the isolation boundary between jobs is the pod rather than a VM. See the ARC profile.
GitHub supports the scale-set mode of ARC; the older community-maintained mode is community supported. For autoscaling outside Kubernetes, GitHub also publishes a runner scale set client, an open-source Go module that uses the same API to manage runners on VMs, containers or on-premises machines. GitHub describes it as a complement to ARC, not a replacement.
A self-hosting checklist
- Ephemeral runners only. One job per runner, then destroy it. See the security guide.
- Private repositories only, unless every job runs in a throwaway VM and outside contributions need approval.
- An image pipeline. Track the tools on GitHub’s runner images that your workflows assume, and rebuild on a schedule.
- A cache. Ephemeral runners need a remote dependency cache and a plan for Docker layer caching.
- Scale to zero and a ceiling. Cap maximum runners so a runaway workflow cannot run up the bill.
- Observability. Alert on queue time, not only on failures.
- Upgrades. With automatic updates disabled, GitHub stops assigning jobs to a runner that is not updated within 63 days of a new runner release, so plan for regular image rebuilds.
Open-source and self-hostable runner software
| Project | CI systems | Runs on | Licence | Notes |
|---|---|---|---|---|
| Actions Runner Controller (ARC) | GitHub Actions | Kubernetes | Apache-2.0 | Teams that already operate Kubernetes and want the GitHub-supported way to autoscale self-hosted GitHub Actions runners |
| Anka Build Cloud | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | Bare metal, AWS | Not documented | Organisations that run their own Mac fleet or EC2 Mac instances and want licensed macOS VM tooling with plugins for several CI systems |
| Aspect Workflows | GitHub Actions, Buildkite, GitLab CI, CircleCI | AWS, Google Cloud | Not documented | Bazel monorepo teams that want warm, persistent CI runners in their own AWS or GCP account alongside remote cache and remote execution |
| Cilicon | GitHub Actions, GitLab CI, Buildkite | Bare metal | MIT | Teams with one or a few dedicated Apple silicon Macs that want ephemeral self-hosted runners without an orchestration layer |
| ec2-github-runner | GitHub Actions | AWS | MIT | Repositories that occasionally need a job to run on a specific EC2 instance type or inside a private VPC, without operating a standing autoscaler |
| Elastic CI Stack for AWS | Buildkite | AWS | MIT | Buildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template |
| enomem | GitHub Actions | Azure | Not documented | Teams on GitHub Actions that already use Azure and want per-job Spot VMs inside their own subscription for a flat monthly licence |
| Fireactions | GitHub Actions | Bare metal | Apache-2.0 | Teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes |
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | AWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack, Akamai/Linode | Apache-2.0 | Teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure |
| GitLab Runner | GitLab CI | AWS, Google Cloud, Azure, Kubernetes, DigitalOcean, VMware vSphere, Bare metal | MIT | Teams on GitLab CI/CD that want to run jobs on their own machines, clusters or autoscaled cloud instances |
| HyperEnv for GitHub Actions Runner | GitHub Actions | AWS | Not documented | Teams that buy through AWS Marketplace and want GitHub Actions runners that run entirely inside their AWS account for a metered per-minute fee |
| myshoes | GitHub Actions | LXD, OpenStack, AWS | MIT | Platform teams that run a private cloud such as OpenStack or LXD and want to offer on-demand GitHub Actions runners to their organisation |
| Orka | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | MacStadium Cloud, AWS, Kubernetes, Bare metal | Not documented | Teams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems |
| RunsOn | GitHub Actions | AWS | Not documented | Teams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence |
| Tart | GitLab CI, Buildkite, GitHub Actions | Bare metal | FSL-1.1-ALv2 | Teams that run their own Apple silicon Macs and want scriptable, image-based macOS VMs for GitLab CI or Buildkite jobs |
| Tartelet | GitHub Actions | Bare metal | MIT | Small teams on GitHub Actions that want two isolated, ephemeral runners per Mac managed from a desktop app |
| terraform-aws-github-runner | GitHub Actions | AWS | MIT | Teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero |
| terraform-aws-gitlab-runner | GitLab CI | AWS | MIT | Teams on GitLab CI that manage AWS with Terraform and want autoscaling runners on spot instances |
| TestFlows GitHub Hetzner Runners | GitHub Actions | Hetzner | Apache-2.0 | Single-repository projects that want low-cost x64 or arm64 GitHub Actions runners on Hetzner Cloud with very little setup |
| Ubicloud Runners | GitHub Actions | Hetzner, Leaseweb, AWS, Bare metal | AGPL-3.0 | Teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source |
Frequently asked questions
Is self-hosting GitHub Actions runners worth it?
Can I run self-hosted runners without Kubernetes?
Sources
- docs.github.com/en/actions/reference/runners/self-hosted-runners
- docs.github.com/en/actions/concepts/runners/actions-runner-controller
- docs.github.com/en/actions/concepts/runners/runner-scale-sets
- docs.github.com/en/actions/concepts/runners/support-for-arc
- github.com/actions/actions-runner-controller
- github.com/actions/scaleset
- docs.github.com/en/actions/reference/security/secure-use
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). Self-hosting GitHub Actions runners: the options. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/guides/self-hosting-github-actions-runners/