GitLab-hosted runners
GitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size. The built-in runners for GitLab.com, suited to teams that want no runner administration and whose usage fits the compute-minute quota of their tier.
Overview
GitLab-hosted runners are the runners GitLab operates for projects on GitLab.com. They are enabled by default: a job with no tags runs on the small Linux x86-64 machine, and a tags entry such as saas-linux-medium-amd64 selects another size. Each job gets a newly provisioned VM that is deleted afterwards. Linux runners use the docker+machine executor on Google Compute Engine and run in privileged mode, so Docker-in-Docker builds work.
Usage is metered in compute minutes rather than priced per minute: job duration is multiplied by a cost factor that rises with machine size, and each tier includes a monthly quota. Larger Linux machines, the GPU runner and macOS runners require Premium or Ultimate. GitLab’s documentation labels the macOS and Windows runners as beta. Separate hosted runners exist for GitLab Dedicated.
Notable
- As of November 2026 GitLab’s documentation labels hosted runners on macOS and on Windows as beta
- As of November 2026 the documented macOS images are macos-15-xcode-16 and macos-26-xcode-26, with macos-27-xcode-27 in beta
- GitLab states a service level objective that 90% of CI/CD jobs start executing in 120 seconds or less
GitLab-hosted runners specifications
| Attribute | Details |
|---|---|
| CI systems | GitLab CI |
| Operating systems | Linux, macOS, Windows |
| Architectures | x64, arm64 |
| Deployment | First-party hosted runners |
| Isolation | Each job runs in a newly provisioned VM that serves a single job and is deleted right after it; firewall rules block inbound traffic and traffic between VMs |
| Fresh environment per job | Yes |
| Hardware | Linux runners are Google Compute Engine VMs running Container-Optimized OS; macOS runners are Apple silicon M1 and M2 Pro machines. GitLab notes that machine and processor types might change |
| Performance (vendor claim) | Not documented |
| Runner sizes | Linux x86-64: 2 vCPU / 8 GB to 32 vCPU / 128 GB; Linux Arm64: 2 vCPU / 8 GB to 8 vCPU / 32 GB; macOS: 4 vCPU / 8 GB (M1) and 6 vCPU / 16 GB (M2 Pro); Windows: 2 vCPU / 7.5 GB |
| Caching | Hosted runners share a distributed cache in Google Cloud Storage. Cache contents not updated in the last 14 days are removed, and an uploaded cache archive can be at most 5 GB. |
| Docker layer caching | Not documented |
| GPU | One GPU machine type on Linux x86-64 for Premium and Ultimate: 4 vCPU, 15 GB RAM and 1 NVIDIA Tesla T4 (or similar) with 16 GB, at cost factor 7. |
| Concurrency | Maximum jobs in active pipelines on GitLab.com: 500 on Free, 20,000 on Premium and 60,000 on Ultimate |
| Job limits | Jobs on GitLab.com hosted runners time out after 3 hours, regardless of the timeout configured in the project |
| Static IPs | Not documented |
| SSH into running jobs | Not documented |
| Observability | Compute minute usage per namespace on the instance runner usage dashboard, with notifications as a quota is approached. |
| Setup | Enabled by default for all projects on GitLab.com. Untagged jobs run on the small Linux x86-64 runner; add a tags entry in .gitlab-ci.yml to pick another machine type. |
| Example label | saas-linux-medium-amd64 |
| Pricing | No per-minute price is published. Jobs consume compute minutes at job duration times a cost factor: Linux small 1, medium 2, large 3, xlarge 6, 2xlarge 12; GPU 7; macOS M1 6 and M2 Pro 12 (beta); Windows 1 (beta). Additional compute minutes cost $10 per 1,000 minutes as a one-time purchase. |
| Free tier | 400 compute minutes per month on the Free tier; Premium includes 10,000 and Ultimate 50,000 per month |
| Compliance | Not documented |
| Regions | Linux x86-64 VMs run in Google Cloud us-east1 and us-east5; Linux Arm64 VMs run in us-central1 |
| Open source | No |
| Company headquarters | Not documented |
Facts from GitLab-hosted runners’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You host code on GitLab.com and want pipelines to run without registering any runner
- You want each job in its own VM that is deleted after the job
- You need Docker-in-Docker, which the Linux runners support by running in privileged mode
- You need Linux Arm64 or a GPU machine alongside x86-64 from the same platform
Trade-offs
- Hosted runners on macOS and on Windows are in beta
- Jobs time out after 3 hours regardless of the project timeout
- Large and bigger Linux machines, the GPU runner and macOS runners are limited to Premium and Ultimate
- GitLab says macOS machine availability is limited and jobs might queue for extended periods
Good fit for: Teams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes.
Use cases GitLab-hosted runners fits
- Docker builds: Linux runners run in privileged mode to support Docker-in-Docker image builds.
- ARM64 builds: Linux Arm64 machine types with 2, 4 and 8 vCPU are documented.
- macOS and iOS builds: macOS runners on M1 and M2 Pro hardware with Xcode images are available in beta for Premium and Ultimate.
- GPU jobs: A GPU-enabled Linux machine type with an NVIDIA Tesla T4 (or similar) is available on Premium and Ultimate.
- GitLab CI runners: These are GitLab’s own hosted runners for GitLab CI/CD on GitLab.com, enabled by default for all projects.
How GitLab-hosted runners compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
| 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 |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| Buildkite hosted agents | Buildkite | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral virtualized environment | $0.008/min | 64 vCPU / 256 GB | Yes | Not documented | No | 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 |
| AWS CodeBuild-hosted runners | GitHub Actions, GitLab CI, Buildkite | Linux, Windows, x64, arm64 | Your cloud account | Fresh build environment | $0.005/min | 72 vCPU / 144 GB | Yes | Yes | No | United States |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
Head-to-head: AWS CodeBuild-hosted runners vs GitLab-hosted runners · Buildkite hosted agents vs GitLab-hosted runners · GitHub-hosted runners vs GitLab-hosted runners · GitLab Runner vs GitLab-hosted runners · GitLab-hosted runners vs Microsoft-hosted agents · GitLab-hosted runners vs RunJob
Frequently asked questions
What is GitLab-hosted runners?
Which CI systems does GitLab-hosted runners work with?
How does GitLab-hosted runners isolate jobs?
Is GitLab-hosted runners open source?
How much does GitLab-hosted runners cost?
How do you set up GitLab-hosted runners?
saas-linux-medium-amd64.Does GitLab-hosted runners have a free tier?
Does GitLab-hosted runners support ARM64 runners?
Does GitLab-hosted runners offer macOS runners?
Does GitLab-hosted runners offer GPU runners?
How many jobs can run at once on GitLab-hosted runners?
Where do GitLab-hosted runners runners run?
What are the alternatives to GitLab-hosted runners?
Sources
- docs.gitlab.com/ci/runners/hosted_runners/
- docs.gitlab.com/ci/runners/hosted_runners/linux/
- docs.gitlab.com/ci/runners/hosted_runners/macos/
- docs.gitlab.com/ci/runners/hosted_runners/windows/
- docs.gitlab.com/ci/runners/hosted_runners/gpu_enabled/
- docs.gitlab.com/ci/pipelines/compute_minutes/
- docs.gitlab.com/subscriptions/gitlab_com/compute_minutes/
- docs.gitlab.com/user/gitlab_com/
- about.gitlab.com/pricing/
- about.gitlab.com/company/visiting/
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-hosted runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/gitlab-hosted-runners/