CI Runnerscirunners.org
Use case · GitLab CI runners

Choosing runners for GitLab CI

Answer in brief

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.

By the CI Runners editors · Updated

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.

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.

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

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
Anka Build CloudGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCitymacOS, arm64, x64Your cloud or hardwaremacOS VMNot documentedSet by your infrastructureNot documentedYesNoUnited States
Aspect WorkflowsGitHub Actions, Buildkite, GitLab CI, CircleCILinux, x64, arm64Your cloud or hardwarePersistent VMAnnual platform fee (quote) + cloud costSet by your infrastructureNot documentedYesNoNot documented
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
CiliconGitHub Actions, GitLab CI, BuildkitemacOS, arm64Self-hostedmacOS VMFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
GetMacGitHub Actions, GitLab CI, BuildkitemacOS, arm64Vendor-hostedmacOS VM$0.012/min (macOS M4, Developer plan)Not documentedNot documentedNot documentedNoLithuania
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
OrkaGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCitymacOS, arm64Your cloud or hardwaremacOS VMFrom $109/mo per hosted Mac mini (Orka by quote)Set by your infrastructureNot documentedNot documentedNoUnited States
RunJobGitHub Actions, GitLab CILinux, x64Vendor-hostedKVM virtual machine€0.00002 per vCPU-second used48 vCPU / 96 GBNoYesNoEstonia
TartGitLab CI, Buildkite, GitHub ActionsmacOS, Linux, arm64Your cloud or hardwareApple Virtualization VMNot documentedSet by your infrastructureNot documentedNot documentedNoUnited States
terraform-aws-gitlab-runnerGitLab CILinuxSelf-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented

Frequently asked questions

Can I use my own runners with GitLab.com?
Yes. Install the open-source GitLab Runner on your own machines or cloud instances and register it with a project, group or instance. Jobs that run on your own runners do not consume GitLab compute minutes.

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/