GitLab Runner
The open-source agent that runs GitLab CI/CD jobs, with executors for Docker, Kubernetes, shell and autoscaled cloud instances. The official open-source runner for GitLab CI/CD, with executors ranging from a local shell to autoscaled cloud instances; it suits any team that self-hosts GitLab runners.
Overview
GitLab Runner is the application that works with GitLab CI/CD to run the jobs in a pipeline. It is written in Go, distributed as a single binary under the MIT licence, and runs on Linux, macOS and Windows. An executor decides where each job runs: Docker, Kubernetes, Shell, SSH, VirtualBox, Parallels, Custom, or the autoscaling Docker Autoscaler and Instance executors. It works with GitLab.com, GitLab Self-Managed and GitLab Dedicated.
Autoscaling on public clouds uses the Docker Autoscaler and Instance executors, which create instances on demand through fleeting plugins. GitLab maintains plugins for AWS Auto Scaling groups, Google Cloud instance groups and Azure scale sets; community plugins cover VMware vSphere, DigitalOcean, Magalu Cloud and libvirt. With capacity and use count set to one, each job gets an instance that is deleted afterwards. The older Docker Machine executor is deprecated in favour of this autoscaler.
Notable
- GitLab Runner v19.6.0 was released on 19 November 2026
- The Docker Machine executor was deprecated in GitLab 17.5 and is scheduled for removal in GitLab 20.0 (May 2027)
- The Docker Autoscaler and Instance executors became generally available in GitLab Runner 17.1
GitLab Runner specifications
| Attribute | Details |
|---|---|
| CI systems | GitLab CI |
| Operating systems | Linux, macOS, Windows |
| Architectures | x64, arm64 |
| Deployment | Open-source project |
| Where it can run | AWS, Google Cloud, Azure, Kubernetes, DigitalOcean, VMware vSphere, Bare metal |
| Isolation | Depends on the executor: Docker and Kubernetes run jobs in containers, the Docker Autoscaler and Instance executors create cloud instances through fleeting plugins, and the Shell and SSH executors run on the host without a clean build environment |
| Fresh environment per job | Not documented |
| Hardware | Not documented |
| Performance (vendor claim) | Not documented |
| Runner sizes | Not documented |
| Caching | The docs describe a distributed cache that uses an object storage server (the example uses S3) to share the cache between Docker hosts, and a Docker registry mirror for autoscaled hosts. |
| Docker layer caching | Not documented |
| GPU | GPU use is documented for the Shell, Docker (gpus option with the NVIDIA Container Toolkit), Kubernetes and Docker Machine executors. |
| Concurrency | Set by the concurrent setting in config.toml; for autoscaling the docs set it to max_instances multiplied by capacity_per_instance |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Not documented |
| Observability | Embedded Prometheus metrics HTTP server |
| Setup | Install the runner from a package, binary, Docker image, Helm chart or Operator, register it with your GitLab instance and choose an executor in config.toml. For autoscaling, add a fleeting plugin and run gitlab-runner fleeting install. |
| Example label | Not documented |
| Pricing | Free and open source; you pay for the infrastructure it runs on. The docs list it for the Free, Premium and Ultimate tiers. |
| Free tier | Not documented |
| Compliance | Not documented |
| Regions | Not documented |
| Open source | Yes (MIT) |
| Company headquarters | Not documented |
Facts from GitLab Runner’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You use GitLab CI/CD and want to run jobs on infrastructure you control
- You want a choice of executors, from containers on Docker or Kubernetes to full cloud instances
- You want autoscaling on AWS, Google Cloud or Azure with plugins that GitLab maintains
- You need runners on Linux, macOS and Windows from the same project
- You want one single-use instance per job, which the autoscaling executors document
Trade-offs
- The Docker Machine executor is deprecated and scheduled for removal in GitLab 20.0
- SSH, Shell, Parallels, VirtualBox, Custom and Docker Machine executors receive critical security updates only, with no new features planned
- Community fleeting plugins are maintained outside GitLab, which says it cannot test them
- When an instance runs several jobs, the Instance executor docs say there is little isolation between them and the jobs should be trusted
Good fit for: Teams on GitLab CI/CD that want to run jobs on their own machines, clusters or autoscaled cloud instances.
Use cases GitLab Runner fits
- macOS and iOS builds: The runner installs on macOS on Apple Silicon and Intel systems.
- GPU jobs: GPU configuration is documented for the Shell, Docker and Kubernetes executors.
- Your own cloud: Fleeting plugins create job instances in your own AWS, Google Cloud or Azure account.
- Open source and self-hosted: The runner is MIT licensed and distributed as a single binary.
- GitLab CI runners: It is the official runner application for GitLab CI/CD.
How GitLab Runner compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| GitLab Runner | GitLab CI | Linux, macOS, Windows, x64, arm64 | Self-hosted | Depends on executor | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| GitLab-hosted runners | GitLab CI | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral VM | $10 per 1,000 compute minutes | 32 vCPU / 128 GB | Not documented | Yes | No | Not documented |
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | Linux, Windows, x64, arm64 | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Romania |
| Elastic CI Stack for AWS | Buildkite | Linux, Windows, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Australia |
| terraform-aws-github-runner | GitHub Actions | Linux, Windows, macOS, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| Microsoft-hosted agents | Azure Pipelines | Linux, macOS, Windows, x64 | Platform-hosted | Fresh VM | $40/month per parallel job | 2 vCPU / 7 GB | Not documented | Not documented | No | United States |
Head-to-head: Elastic CI Stack for AWS vs GitLab Runner · GitLab Runner vs GitLab-hosted runners · GitLab Runner vs terraform-aws-gitlab-runner
Frequently asked questions
What is GitLab Runner?
Which CI systems does GitLab Runner work with?
How does GitLab Runner isolate jobs?
Is GitLab Runner open source?
How much does GitLab Runner cost?
How do you set up GitLab Runner?
Does GitLab Runner support ARM64 runners?
Does GitLab Runner offer macOS runners?
Does GitLab Runner offer GPU runners?
How many jobs can run at once on GitLab Runner?
What are the alternatives to GitLab Runner?
Sources
- docs.gitlab.com/runner/
- docs.gitlab.com/runner/executors/
- docs.gitlab.com/runner/executors/docker_autoscaler/
- docs.gitlab.com/runner/executors/instance/
- docs.gitlab.com/runner/executors/docker_machine/
- docs.gitlab.com/runner/fleet_scaling/fleeting/
- docs.gitlab.com/runner/runner_autoscale/
- docs.gitlab.com/runner/configuration/autoscale/
- docs.gitlab.com/runner/configuration/gpus/
- docs.gitlab.com/runner/install/
- docs.gitlab.com/runner/install/linux-manually/
- gitlab.com/gitlab-org/gitlab-runner
- gitlab.com/gitlab-org/gitlab-runner/-/releases
- gitlab.com/gitlab-org/gitlab-runner/-/blob/main/LICENSE
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). GitLab Runner. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/gitlab-runner/