CI Runnerscirunners.org
Head-to-head

Buildkite hosted agents vs Microsoft-hosted agents

Answer in brief

Buildkite hosted agents suits teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. Microsoft-hosted agents suits teams on Azure DevOps Services that want pipelines to run on standard images without managing agents. Buildkite hosted agents is the CI platform’s own hosted runners for Buildkite, priced at $0.008/min; Microsoft-hosted agents is the CI platform’s own hosted runners for Azure Pipelines, priced at $40/month per parallel job.

By the CI Runners editors · Updated

Key differences between Buildkite hosted agents and Microsoft-hosted agents

  • CI systems: Only Buildkite hosted agents documents Buildkite. Only Microsoft-hosted agents documents Azure Pipelines.
  • Architectures: Only Buildkite hosted agents documents arm64.
  • Isolation: Buildkite hosted agents: Ephemeral virtualized environment. Microsoft-hosted agents: Fresh VM.
  • Published price: $0.008/min (Buildkite hosted agents) versus $40/month per parallel job (Microsoft-hosted agents).
  • Largest runner: 64 vCPU / 256 GB (Buildkite hosted agents) versus 2 vCPU / 7 GB (Microsoft-hosted agents).
  • Static IPs: Buildkite hosted agents documents static egress IPs; Microsoft-hosted agents does not.
  • SSH access: Buildkite hosted agents documents SSH access to running jobs; Microsoft-hosted agents does not.

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.

Buildkite hosted agents vs Microsoft-hosted agents at a glance

AttributeBuildkite hosted agentsMicrosoft-hosted agents
What it isBuildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute.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.
TypeFirst-party hosted runnersFirst-party hosted runners
CI systemsBuildkiteAzure Pipelines
Operating systemsLinux, macOS, WindowsLinux, macOS, Windows
Architecturesx64, arm64x64
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 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 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 disksWindows 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)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 GBOne 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
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.Not documented
Docker layer cachingYesNot documented
GPUNot documentedNot documented
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 EnterpriseOne job at a time per Microsoft-hosted parallel job; the free tier provides one parallel job
Static IPsYesNo
SSH into running jobsYesNo
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.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 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 cardOne free Microsoft-hosted parallel job with 1,800 minutes per month for private projects, limited to 60 minutes per job
Open sourceNoNo
Self-host / your cloudNo / NoNo / No
ComplianceSOC 2 Type IINot documented
RegionsUS East Coast data centers onlyWindows 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 headquartersNot documentedRedmond, Washington, United States
Good fit forTeams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machinesTeams 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 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 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

  • Buildkite hosted agents: Hosted exclusively in US East Coast data centers
  • Buildkite hosted agents: Signed pipeline validation is not supported for hosted agents
  • 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 Buildkite hosted agents profile and Microsoft-hosted agents profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Buildkite hosted agents or Microsoft-hosted agents 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. Microsoft-hosted agents suits teams on Azure DevOps Services that want pipelines to run on standard images without managing agents.
What is the difference between Buildkite hosted agents and Microsoft-hosted agents?
Only Buildkite hosted agents documents Buildkite. Only Microsoft-hosted agents documents Azure Pipelines. Only Buildkite hosted agents documents arm64. Isolation is Ephemeral virtualized environment on Buildkite hosted agents and Fresh VM on Microsoft-hosted agents. Published price: $0.008/min (Buildkite hosted agents) versus $40/month per parallel job (Microsoft-hosted agents). Largest runner: 64 vCPU / 256 GB (Buildkite hosted agents) versus 2 vCPU / 7 GB (Microsoft-hosted agents).
Which is open source, Buildkite hosted agents or Microsoft-hosted agents?
Neither is open source.
How do Buildkite hosted agents and Microsoft-hosted agents 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. Microsoft-hosted agents: 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.
How does Buildkite hosted agents pricing compare with Microsoft-hosted agents?
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. Microsoft-hosted agents: 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. Rates change, so check the Buildkite hosted agents and Microsoft-hosted agents pricing pages before deciding.
Is Buildkite hosted agents or Microsoft-hosted agents 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). Microsoft-hosted agents: Not documented.
Do Buildkite hosted agents and Microsoft-hosted agents 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. Microsoft-hosted agents: Docker layer caching is not documented.
Where do Buildkite hosted agents and Microsoft-hosted agents runners run?
Buildkite hosted agents is the CI platform’s own hosted runners. Microsoft-hosted agents 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. learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops
  6. learn.microsoft.com/en-us/azure/devops/pipelines/agents/github-hosted?view=azure-devops
  7. learn.microsoft.com/en-us/azure/devops/pipelines/licensing/concurrent-jobs?view=azure-devops
  8. 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). Buildkite hosted agents vs Microsoft-hosted agents. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/buildkite-hosted-agents-vs-azure-pipelines-agents/