Choosing runners for GitLab CI
GitLab CI jobs run on GitLab-hosted runners, billed in compute minutes with a cost factor per machine size, or on runners you manage with the open-source GitLab Runner. Self-managed runners cost no compute minutes and work with GitLab.com and self-managed GitLab alike. A smaller set of third-party products host or orchestrate GitLab runners for you.
What GitLab CI pipelines need from a runner
- Hosted or self-managed: GitLab-hosted runners need no setup; self-managed runners use your infrastructure and no compute-minute quota.
- Executor: GitLab Runner runs jobs through an executor (Docker, Kubernetes, shell, or autoscaled instances). The executor decides isolation and scaling.
- Autoscaling: instance-based autoscaling starts cloud VMs for the queue; the Kubernetes executor starts a pod per job.
- Isolation: one VM per job for untrusted code; shared Docker hosts only for trusted projects.
- Caching: a distributed cache in object storage so autoscaled runners share dependencies.
Runners that fit, by kind
12 runners document what this workload needs. They are grouped by kind and listed alphabetically; the order is not a ranking. Shortlist two or three, then try them with your own workflows.
Managed runners for GitHub Actions
Third-party runners you switch to by changing the runs-on label in a workflow.
RunJob
EU-based managed runners for GitHub Actions and GitLab CI that run each job in a fresh KVM virtual machine and bill only CPU and memory used.
- KVM virtual machine
- Ephemeral
- GPU
Why it fits: RunJob registers managed runners for GitLab.com and self-hosted GitLab without changes to existing pipelines.
Runners from your CI platform or cloud
The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services.
AWS CodeBuild-hosted runners
AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job.
- Fresh build environment
- Ephemeral
- arm64
- Windows
- Docker layer cache
- GPU
- BYOC
Why it fits: CodeBuild can host self-managed GitLab runners triggered by a GitLab webhook.
Full profile →AWS CodeBuild-hosted runners alternativesWebsite ↗
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.
- Ephemeral VM
- Ephemeral
- arm64
- macOS
- Windows
- GPU
Why it fits: These are GitLab’s own hosted runners for GitLab CI/CD on GitLab.com, enabled by default for all projects.
Runners in your own cloud or on your hardware
Commercial products that launch runners inside your cloud account or on servers you own.
Actuated
Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI.
- Firecracker microVM
- Ephemeral
- arm64
- Docker layer cache
- GPU
- BYOC
Why it fits: GitLab CI is supported for GitLab.com and self-managed GitLab, with jobs opted in through an actuated tag.
Aspect Workflows
Bazel-focused platform whose auto-scaling CI runners register with your existing CI and can run in your own AWS account or GCP project.
- Persistent VM
- arm64
- GPU
- BYOC
- Self-hostable
Why it fits: Runner groups register with GitLab and are selected with GitLab CI tags.
Open-source autoscalers for self-hosted runners
Software you deploy to run and scale self-hosted runners on Kubernetes, cloud VMs or bare metal.
GitLab Runner
The open-source agent that runs GitLab CI/CD jobs, with executors for Docker, Kubernetes, shell and autoscaled cloud instances.
- Depends on executor
- arm64
- macOS
- Windows
- GPU
- Open source
- BYOC
- Self-hostable
Why it fits: It is the official runner application for GitLab CI/CD.
terraform-aws-gitlab-runner
Terraform module that deploys GitLab Runner on AWS and autoscales its job workers on EC2 spot instances.
- EC2 instance
- Open source
- BYOC
- Self-hostable
Why it fits: The module deploys and registers GitLab Runner agents and their autoscaled workers.
Full profile →terraform-aws-gitlab-runner alternativesWebsite ↗
macOS runners for iOS and Mac builds
Apple-silicon runners and virtualization tools for building and testing iOS and macOS apps.
Anka Build Cloud
Commercial macOS virtualization for CI: a controller and registry manage on-demand Anka VMs on your own Macs, hosted Macs or AWS EC2 Mac.
- macOS VM
- Ephemeral
- arm64
- macOS
- GPU
- BYOC
- Self-hostable
Why it fits: Veertu maintains a GitLab Runner custom executor that runs GitLab jobs in Anka VMs through the Controller.
Cilicon
Open-source macOS app that runs ephemeral CI virtual machines on a single Apple silicon Mac using Apple’s Virtualization framework.
- macOS VM
- Ephemeral
- arm64
- macOS
- Open source
- BYOC
- Self-hostable
Why it fits: A GitLab Runner provisioner registers a runner inside each VM using an authentication token.
GetMac
Managed macOS runners on vendor-owned Apple silicon M4 hardware in Lithuania, sold as monthly plans of included compute minutes.
- macOS VM
- Ephemeral
- arm64
- macOS
Why it fits: A custom GitLab Runner executor creates a fresh GetMac VM for each GitLab job and deletes it afterwards.
Orka
Kubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs.
- macOS VM
- arm64
- macOS
- BYOC
- Self-hostable
Why it fits: MacStadium documents GitLab shell executors and a custom executor that creates an Orka VM per pipeline.
Tart
Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs.
- Apple Virtualization VM
- Ephemeral
- arm64
- macOS
- BYOC
- Self-hostable
Why it fits: The GitLab Tart Executor runs GitLab jobs in ephemeral Tart VMs through GitLab Runner’s custom executor.
Side by side
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Actuated | GitHub Actions, GitLab CI | Linux, x64, arm64 | Your cloud or hardware | Firecracker microVM | $150/mo per server + your servers | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Anka Build Cloud | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | macOS, arm64, x64 | Your cloud or hardware | macOS VM | Not documented | Set by your infrastructure | Not documented | Yes | No | United States |
| Aspect Workflows | GitHub Actions, Buildkite, GitLab CI, CircleCI | Linux, x64, arm64 | Your cloud or hardware | Persistent VM | Annual platform fee (quote) + cloud cost | Set by your infrastructure | Not documented | Yes | No | Not documented |
| 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 |
| Cilicon | GitHub Actions, GitLab CI, Buildkite | macOS, arm64 | Self-hosted | macOS VM | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| GetMac | GitHub Actions, GitLab CI, Buildkite | macOS, arm64 | Vendor-hosted | macOS VM | $0.012/min (macOS M4, Developer plan) | Not documented | Not documented | Not documented | No | Lithuania |
| 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 |
| Orka | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | macOS, arm64 | Your cloud or hardware | macOS VM | From $109/mo per hosted Mac mini (Orka by quote) | Set by your infrastructure | Not documented | Not documented | No | United States |
| RunJob | GitHub Actions, GitLab CI | Linux, x64 | Vendor-hosted | KVM virtual machine | €0.00002 per vCPU-second used | 48 vCPU / 96 GB | No | Yes | No | Estonia |
| Tart | GitLab CI, Buildkite, GitHub Actions | macOS, Linux, arm64 | Your cloud or hardware | Apple Virtualization VM | Not documented | Set by your infrastructure | Not documented | Not documented | No | United States |
| terraform-aws-gitlab-runner | GitLab CI | Linux | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
Frequently asked questions
Can I use my own runners with GitLab.com?
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). Choosing runners for GitLab CI. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/use-cases/gitlab/