GitLab-hosted runners vs Microsoft-hosted agents
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. Microsoft-hosted agents suits teams on Azure DevOps Services that want pipelines to run on standard images without managing agents. GitLab-hosted runners is the CI platform’s own hosted runners for GitLab CI, priced at $10 per 1,000 compute minutes; Microsoft-hosted agents is the CI platform’s own hosted runners for Azure Pipelines, priced at $40/month per parallel job.
Key differences between GitLab-hosted runners and Microsoft-hosted agents
- CI systems: Only GitLab-hosted runners documents GitLab CI. Only Microsoft-hosted agents documents Azure Pipelines.
- Architectures: Only GitLab-hosted runners documents arm64.
- Isolation: GitLab-hosted runners: Ephemeral VM. Microsoft-hosted agents: Fresh VM.
- Published price: $10 per 1,000 compute minutes (GitLab-hosted runners) versus $40/month per parallel job (Microsoft-hosted agents).
- Largest runner: 32 vCPU / 128 GB (GitLab-hosted runners) versus 2 vCPU / 7 GB (Microsoft-hosted agents).
What they have in common
- Both are first-party runners from a CI platform.
- Both document Linux, macOS and Windows runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Neither is open source.
GitLab-hosted runners vs Microsoft-hosted agents at a glance
| Attribute | GitLab-hosted runners | Microsoft-hosted agents |
|---|---|---|
| What it is | GitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size. | Azure Pipelines’ built-in agents: a fresh 2-core VM per job on Windows, Linux or macOS, sold per parallel job rather than per minute. |
| Type | First-party hosted runners | First-party hosted runners |
| CI systems | GitLab CI | Azure Pipelines |
| Operating systems | Linux, macOS, Windows | Linux, macOS, Windows |
| Architectures | x64, arm64 | x64 |
| 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 | Each job gets a freshly imaged virtual machine that is discarded after one job; each agent is dedicated to a single organization and each VM hosts a single agent |
| Fresh environment per job | Yes | 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 | Windows and Linux agents run on Azure Standard_DS2_v2 general purpose VMs with 2 cores, 7 GB RAM and 14 GB SSD; macOS agents run on Mac Pros with a 3-core CPU and 14 GB RAM |
| Performance (vendor claim) | Not documented | 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 | One size: 2 vCPU / 7 GB on Windows and Linux and 3 cores / 14 GB on macOS. A separate pay-as-you-go GitHub-hosted agents pool offers 8- and 16-core Linux and Windows machines and Apple silicon macOS machines |
| 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. | Not documented |
| Docker layer caching | Not documented | 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. | Not documented |
| Concurrency | Maximum jobs in active pipelines on GitLab.com: 500 on Free, 20,000 on Premium and 60,000 on Ultimate | One job at a time per Microsoft-hosted parallel job; the free tier provides one parallel job |
| Static IPs | Not documented | No |
| SSH into running jobs | Not documented | No |
| 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. | Sold per parallel job, not per minute: $40 per month for each extra Microsoft-hosted parallel job with unlimited minutes. The separate GitHub-hosted agents pool is billed per minute with no free minutes; Microsoft’s retail price list shows Linux 8-core $0.022, Linux 16-core $0.042, Windows 8-core $0.042, Windows 16-core $0.082, macOS Standard $0.062 and macOS XL $0.102 per minute. |
| Free tier | 400 compute minutes per month on the Free tier; Premium includes 10,000 and Ultimate 50,000 per month | One free Microsoft-hosted parallel job with 1,800 minutes per month for private projects, limited to 60 minutes per job |
| Open source | No | No |
| Self-host / your cloud | No / No | No / No |
| Compliance | Not documented | Not documented |
| Regions | Linux x86-64 VMs run in Google Cloud us-east1 and us-east5; Linux Arm64 VMs run in us-central1 | Windows and Linux agents run in the Azure geography of the Azure DevOps organization (Asia Pacific, Australia, Canada, Europe, India, United Kingdom or United States); macOS agents always run in the US |
| Company headquarters | Not documented | Redmond, Washington, United States |
| 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 | Teams on Azure DevOps Services that want pipelines to run on standard images without managing agents |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
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
Reasons to choose Microsoft-hosted agents
- You use Azure DevOps Services and want agents with no installation or maintenance
- You prefer a flat monthly price per parallel job with unlimited minutes
- You want each job on a freshly imaged VM dedicated to your organization
- You want Windows and Linux agents to run in the same Azure geography as your organization
Trade-offs to check first
- 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
- Microsoft-hosted agents: Disk space and processing power cannot be increased on Microsoft-hosted agents
- Microsoft-hosted agents: No ability to connect remotely to an agent
Run your slowest workflow on both before deciding. See the full GitLab-hosted runners profile and Microsoft-hosted agents profile, or the complete comparison.
More comparisons
- 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 RunJob
- Buildkite hosted agents vs Microsoft-hosted agents
- Managed DevOps Pools vs Microsoft-hosted agents
Frequently asked questions
Is GitLab-hosted runners or Microsoft-hosted agents better?
What is the difference between GitLab-hosted runners and Microsoft-hosted agents?
Which is open source, GitLab-hosted runners or Microsoft-hosted agents?
How do GitLab-hosted runners and Microsoft-hosted agents isolate jobs?
How does GitLab-hosted runners pricing compare with Microsoft-hosted agents?
Do GitLab-hosted runners and Microsoft-hosted agents offer GPU runners?
Where do GitLab-hosted runners and Microsoft-hosted agents runners run?
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/
- learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/pipelines/agents/github-hosted?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/pipelines/licensing/concurrent-jobs?view=azure-devops
- azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/
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 vs Microsoft-hosted agents. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/gitlab-hosted-runners-vs-azure-pipelines-agents/