CI Runnerscirunners.org
Head-to-head

Buildkite hosted agents vs GitLab-hosted runners

Answer in brief

Buildkite hosted agents suits teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. GitLab-hosted runners suits teams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes. Buildkite hosted agents is the CI platform’s own hosted runners for Buildkite, priced at $0.008/min; GitLab-hosted runners is the CI platform’s own hosted runners for GitLab CI, priced at $10 per 1,000 compute minutes.

By the CI Runners editors · Updated

Key differences between Buildkite hosted agents and GitLab-hosted runners

  • CI systems: Only Buildkite hosted agents documents Buildkite. Only GitLab-hosted runners documents GitLab CI.
  • Isolation: Buildkite hosted agents: Ephemeral virtualized environment. GitLab-hosted runners: Ephemeral VM.
  • Published price: $0.008/min (Buildkite hosted agents) versus $10 per 1,000 compute minutes (GitLab-hosted runners).
  • Largest runner: 64 vCPU / 256 GB (Buildkite hosted agents) versus 32 vCPU / 128 GB (GitLab-hosted runners).

What they have in common

  • Both are first-party runners from a CI platform.
  • Both document Linux, macOS and Windows runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Both give every job a fresh environment.
  • Neither is open source.

Buildkite hosted agents vs GitLab-hosted runners at a glance

AttributeBuildkite hosted agentsGitLab-hosted runners
What it isBuildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute.GitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size.
TypeFirst-party hosted runnersFirst-party hosted runners
CI systemsBuildkiteGitLab CI
Operating systemsLinux, macOS, WindowsLinux, macOS, Windows
Architecturesx64, arm64x64, arm64
IsolationEach job runs in its own virtualized environment that is destroyed with its data after the job; Buildkite describes hypervisor-level isolation between instances on hardware shared across customersEach 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 jobYesYes
HardwareBuildkite says it uses latest-generation Mac (M4) and AMD Zen-based hardware in a private cloud, with cache volumes on local NVMe-attached disksLinux 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)Buildkite says hosted agents deliver up to 3x faster performance than equivalent sized machines from other CI/CD providers and cloud platforms (vendor claim)Not documented
Runner sizesLinux AMD64 and ARM64: 2 vCPU / 4 GB to 64 vCPU / 256 GB (16 vCPU and above on Enterprise); macOS M4: 6 vCPU / 28 GB and 12 vCPU / 56 GB; Windows AMD64: 2 vCPU / 8 GB to 16 vCPU / 64 GBLinux 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
CachingCache volumes and Git mirror volumes on Linux and macOS at no additional cost, retained for up to 14 days from last use, plus an internal container registry per cluster. Remote Docker builders with Docker layer caching are available on the Enterprise plan.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 cachingYesNot documented
GPUNot documentedOne 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.
ConcurrencySet by plan as combined vCPUs in use: on Pro up to 256 Linux AMD64, 64 Linux ARM64, 48 M4 Mac and 64 Windows vCPU; on Free up to 20 Linux AMD64 vCPU; custom on EnterpriseMaximum jobs in active pipelines on GitLab.com: 500 on Free, 20,000 on Premium and 60,000 on Ultimate
Static IPsYesNot documented
SSH into running jobsYesNot documented
PricingPay-as-you-go on the Pro plan ($30 per active user per month): Linux $0.004 per vCPU minute on AMD64 and ARM64 ($0.008/min for 2 vCPU, $0.016 for 4, $0.032 for 8), Mac $0.02 per vCPU minute ($0.12/min for M4 Medium, $0.24 for M4 Large), Windows $0.008 per vCPU minute. Metered to the second with no minimums; cache storage is not charged.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 tierFree plan: up to 2,000 Linux vCPU minutes per month on the Small AMD64 shape. Pro includes 4,000 Linux AMD64 vCPU minutes per month. A 30-day all-access trial needs no credit card400 compute minutes per month on the Free tier; Premium includes 10,000 and Ultimate 50,000 per month
Open sourceNoNo
Self-host / your cloudNo / NoNo / No
ComplianceSOC 2 Type IINot documented
RegionsUS East Coast data centers onlyLinux x86-64 VMs run in Google Cloud us-east1 and us-east5; Linux Arm64 VMs run in us-central1
Company headquartersNot documentedNot documented
Good fit forTeams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machinesTeams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Buildkite hosted agents

  • You use Buildkite Pipelines and want agents that Buildkite provisions and scales
  • You need Apple silicon M4 macOS agents with terminal and browser-based desktop access
  • You want cache volumes and Git mirrors without a separate storage charge
  • You want billing by vCPU minute, metered to the second with no minimum charge

Reasons to choose GitLab-hosted runners

  • 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 to check first

  • Buildkite hosted agents: Hosted exclusively in US East Coast data centers
  • Buildkite hosted agents: Signed pipeline validation is not supported for hosted agents
  • GitLab-hosted runners: Hosted runners on macOS and on Windows are in beta
  • GitLab-hosted runners: Jobs time out after 3 hours regardless of the project timeout

Run your slowest workflow on both before deciding. See the full Buildkite hosted agents profile and GitLab-hosted runners profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Buildkite hosted agents or GitLab-hosted runners better?
Neither is better for every pipeline. Buildkite hosted agents suits teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. GitLab-hosted runners suits teams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes.
What is the difference between Buildkite hosted agents and GitLab-hosted runners?
Only Buildkite hosted agents documents Buildkite. Only GitLab-hosted runners documents GitLab CI. Isolation is Ephemeral virtualized environment on Buildkite hosted agents and Ephemeral VM on GitLab-hosted runners. Published price: $0.008/min (Buildkite hosted agents) versus $10 per 1,000 compute minutes (GitLab-hosted runners). Largest runner: 64 vCPU / 256 GB (Buildkite hosted agents) versus 32 vCPU / 128 GB (GitLab-hosted runners).
Which is open source, Buildkite hosted agents or GitLab-hosted runners?
Neither is open source.
How do Buildkite hosted agents and GitLab-hosted runners isolate jobs?
Buildkite hosted agents: Each job runs in its own virtualized environment that is destroyed with its data after the job; Buildkite describes hypervisor-level isolation between instances on hardware shared across customers. GitLab-hosted runners: 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.
How does Buildkite hosted agents pricing compare with GitLab-hosted runners?
Buildkite hosted agents: Pay-as-you-go on the Pro plan ($30 per active user per month): Linux $0.004 per vCPU minute on AMD64 and ARM64 ($0.008/min for 2 vCPU, $0.016 for 4, $0.032 for 8), Mac $0.02 per vCPU minute ($0.12/min for M4 Medium, $0.24 for M4 Large), Windows $0.008 per vCPU minute. Metered to the second with no minimums; cache storage is not charged. GitLab-hosted runners: 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. Rates change, so check the Buildkite hosted agents and GitLab-hosted runners pricing pages before deciding.
Is Buildkite hosted agents or GitLab-hosted runners faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Buildkite hosted agents: Buildkite says hosted agents deliver up to 3x faster performance than equivalent sized machines from other CI/CD providers and cloud platforms (vendor claim). GitLab-hosted runners: Not documented.
Do Buildkite hosted agents and GitLab-hosted runners cache Docker layers?
Buildkite hosted agents: Cache volumes and Git mirror volumes on Linux and macOS at no additional cost, retained for up to 14 days from last use, plus an internal container registry per cluster. Remote Docker builders with Docker layer caching are available on the Enterprise plan. GitLab-hosted runners: Docker layer caching is not documented.
Do Buildkite hosted agents and GitLab-hosted runners offer GPU runners?
Buildkite hosted agents: Not documented. GitLab-hosted runners: 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.
Where do Buildkite hosted agents and GitLab-hosted runners runners run?
Buildkite hosted agents is the CI platform’s own hosted runners. GitLab-hosted runners is the CI platform’s own hosted runners.

Sources

  1. buildkite.com/docs/agent/buildkite-hosted
  2. buildkite.com/docs/agent/buildkite-hosted/linux
  3. buildkite.com/docs/agent/buildkite-hosted/macos
  4. buildkite.com/docs/agent/buildkite-hosted/windows
  5. docs.gitlab.com/ci/runners/hosted_runners/
  6. docs.gitlab.com/ci/runners/hosted_runners/linux/
  7. docs.gitlab.com/ci/runners/hosted_runners/macos/
  8. docs.gitlab.com/ci/runners/hosted_runners/windows/

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). Buildkite hosted agents vs GitLab-hosted runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/buildkite-hosted-agents-vs-gitlab-hosted-runners/