Guides
Run your own CI runners
Setup guides for self-hosted runners and build agents, one per platform. Each covers installation, registration, autoscaling, ephemeral jobs and security.
- Self-hosted GitHub Actions runners: setup, autoscaling and ephemeral jobs
- GitLab CI custom runners: install, register with glrt- tokens, and autoscale
- GitLab CI/CD for GitHub and Bitbucket repositories, with your own runners
- GitLab Pages on a custom runner: faster static site builds without burning compute minutes
- Gitea Actions runners: register gitea-runner (the renamed act_runner) on a VM, Docker or Kubernetes
- Forgejo Actions runners: install, register and secure forgejo-runner
- CI on Codeberg: hosted Forgejo Actions, ci.codeberg.org and your own runners
- Bitbucket Pipelines self-hosted runners: Docker, shell, Windows, macOS and autoscaling
- Azure Pipelines self-hosted agents: install, register, run in Docker and autoscale
- Jenkins agents on demand: inbound and SSH agents, Kubernetes pods and cloud VMs
- Woodpecker CI agents: connect, label and scale your own agents
- Buildkite agents: tokens, queues, one-job agents and autoscaling
- CircleCI self-hosted runners: resource classes, machine runner 3 and container runner
- Drone CI runners: Docker, exec and Kubernetes runners, routing and autoscaling
- TeamCity build agents: installation, agent pools, cloud profiles and licensing
- CI for Gogs: webhooks, Drone, Jenkins and the move to Gitea or Forgejo
- builds.sr.ht runners: manifests, hosted limits and self-hosted build workers