CI Runnerscirunners.org
Runner profile · Open-source project

GitLab Runner

Answer in brief

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.

By the CI Runners editors · Updated

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

AttributeDetails
CI systemsGitLab CI
Operating systemsLinux, macOS, Windows
Architecturesx64, arm64
DeploymentOpen-source project
Where it can runAWS, Google Cloud, Azure, Kubernetes, DigitalOcean, VMware vSphere, Bare metal
IsolationDepends 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 jobNot documented
HardwareNot documented
Performance (vendor claim)Not documented
Runner sizesNot documented
CachingThe 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 cachingNot documented
GPUGPU use is documented for the Shell, Docker (gpus option with the NVIDIA Container Toolkit), Kubernetes and Docker Machine executors.
ConcurrencySet by the concurrent setting in config.toml; for autoscaling the docs set it to max_instances multiplied by capacity_per_instance
Job limitsNot documented
Static IPsNot documented
SSH into running jobsNot documented
ObservabilityEmbedded Prometheus metrics HTTP server
SetupInstall 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 labelNot documented
PricingFree and open source; you pay for the infrastructure it runs on. The docs list it for the Free, Premium and Ultimate tiers.
Free tierNot documented
ComplianceNot documented
RegionsNot documented
Open sourceYes (MIT)
Company headquartersNot 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

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
GitLab RunnerGitLab CILinux, macOS, Windows, x64, arm64Self-hostedDepends on executorFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
GitLab-hosted runnersGitLab CILinux, macOS, Windows, x64, arm64Platform-hostedEphemeral VM$10 per 1,000 compute minutes32 vCPU / 128 GBNot documentedYesNoNot documented
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
Elastic CI Stack for AWSBuildkiteLinux, Windows, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesAustralia
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
Microsoft-hosted agentsAzure PipelinesLinux, macOS, Windows, x64Platform-hostedFresh VM$40/month per parallel job2 vCPU / 7 GBNot documentedNot documentedNoUnited 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

See all GitLab Runner alternatives →

Frequently asked questions

What is 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.
Which CI systems does GitLab Runner work with?
GitLab Runner runs jobs for GitLab CI, on Linux, macOS, Windows, x64 and arm64.
How does GitLab Runner isolate jobs?
GitLab Runner documents its isolation as: 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.
Is GitLab Runner open source?
Yes (MIT). It can be self-hosted.
How much does GitLab Runner cost?
Free and open source; you pay for the infrastructure it runs on. The docs list it for the Free, Premium and Ultimate tiers. Check the official pricing page for current rates.
How do you set up GitLab Runner?
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.
Does GitLab Runner support ARM64 runners?
Yes, GitLab Runner documents arm64 runners (Linux, macOS and Windows).
Does GitLab Runner offer macOS runners?
Yes, GitLab Runner documents macOS runners alongside Linux and Windows.
Does GitLab Runner offer GPU runners?
GPU use is documented for the Shell, Docker (gpus option with the NVIDIA Container Toolkit), Kubernetes and Docker Machine executors.
How many jobs can run at once on GitLab Runner?
Set by the concurrent setting in config.toml; for autoscaling the docs set it to max_instances multiplied by capacity_per_instance.
What are the alternatives to GitLab Runner?

Sources

  1. docs.gitlab.com/runner/
  2. docs.gitlab.com/runner/executors/
  3. docs.gitlab.com/runner/executors/docker_autoscaler/
  4. docs.gitlab.com/runner/executors/instance/
  5. docs.gitlab.com/runner/executors/docker_machine/
  6. docs.gitlab.com/runner/fleet_scaling/fleeting/
  7. docs.gitlab.com/runner/runner_autoscale/
  8. docs.gitlab.com/runner/configuration/autoscale/
  9. docs.gitlab.com/runner/configuration/gpus/
  10. docs.gitlab.com/runner/install/
  11. docs.gitlab.com/runner/install/linux-manually/
  12. gitlab.com/gitlab-org/gitlab-runner
  13. gitlab.com/gitlab-org/gitlab-runner/-/releases
  14. 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/