AWS CodeBuild-hosted runners vs Managed DevOps Pools
AWS CodeBuild-hosted runners suits teams on AWS that want GitHub Actions, GitLab or Buildkite jobs to run inside their own account with IAM and VPC access. Managed DevOps Pools suits Azure DevOps teams that need bigger or custom-image agents and private network access without operating scale sets. AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account for GitHub Actions, GitLab CI and Buildkite, priced at $0.005/min; Managed DevOps Pools is the CI platform’s own hosted runners for Azure Pipelines, priced at $15/month per parallel job + Azure VM cost.
Key differences between AWS CodeBuild-hosted runners and Managed DevOps Pools
- Type: AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account; Managed DevOps Pools is the CI platform’s own hosted runners.
- CI systems: Only AWS CodeBuild-hosted runners documents GitHub Actions, GitLab CI and Buildkite. Only Managed DevOps Pools documents Azure Pipelines.
- Architectures: Only AWS CodeBuild-hosted runners documents arm64.
- Isolation: AWS CodeBuild-hosted runners: Fresh build environment. Managed DevOps Pools: Azure VM.
- Published price: $0.005/min (AWS CodeBuild-hosted runners) versus $15/month per parallel job + Azure VM cost (Managed DevOps Pools).
- Your own cloud account: AWS CodeBuild-hosted runners documents running in your own cloud account; Managed DevOps Pools does not.
What they have in common
- Both companies are based in the United States.
- Both document Linux and Windows runners.
- Neither is open source.
AWS CodeBuild-hosted runners vs Managed DevOps Pools at a glance
| Attribute | AWS CodeBuild-hosted runners | Managed DevOps Pools |
|---|---|---|
| What it is | AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job. | Azure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates. |
| Type | Cloud provider service | First-party hosted runners |
| CI systems | GitHub Actions, GitLab CI, Buildkite | Azure Pipelines |
| Operating systems | Linux, Windows | Linux, Windows |
| Architectures | x64, arm64 | x64 |
| Isolation | Each job starts a CodeBuild build in a fresh environment that is discarded when it finishes; runner builds use CodeBuild containers or instances on Amazon EC2, or AWS Lambda compute | Agents are Azure VMs in a Microsoft-owned subscription, with each pool isolated in a dedicated virtual network; stateless pools give every job a new agent, stateful pools reuse agents for up to seven days |
| Fresh environment per job | Yes | Not documented |
| Hardware | On-demand Amazon EC2 or AWS Lambda compute, or reserved capacity fleets, on x86-64 and Arm; AWS says runners can use its latest instance types, including ARM-based instances | Azure virtual machine sizes that you select for the pool, up to five sizes per pool with Instance Mix, with an optional attached data disk |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | On-demand EC2: 2 vCPU / 4 GiB to 72 vCPU / 144 GiB on Linux x86-64, 2 vCPU / 4 GiB to 48 vCPU / 96 GiB on Arm, 4 vCPU / 8 GiB to 72 vCPU / 144 GiB on Windows. Lambda: 1 to 10 GiB of memory | Azure VM sizes of your choice, subject to Managed DevOps Pools quota for the VM family |
| Caching | CodeBuild projects can cache to Amazon S3 or use a local cache with source, Docker layer and custom modes. A Docker image server with a shared layer cache is billed separately per second. | Stateful pools keep agent state for up to seven days so later jobs can reuse packages and files from earlier runs. Standby agents can be kept online on a manual or automatic schedule. |
| Docker layer caching | Yes | Not documented |
| GPU | Linux GPU compute types gpu_small (4 vCPU, 16 GiB) at $0.05 and gpu_large (32 vCPU, 255 GiB) at $0.30 per build minute in US East (N. Virginia); GPU models are not stated on the pages checked. | Not documented |
| Concurrency | Concurrently running builds are capped by per-Region service quotas for each environment type, which AWS lists as adjustable | Limited by the pool’s Maximum agents setting, the Managed DevOps Pools quota for the VM family, and the number of self-hosted parallel jobs in the Azure DevOps organization |
| Static IPs | Not documented | Yes |
| SSH into running jobs | Not documented | No |
| Pricing | Standard CodeBuild rates per build minute in US East (N. Virginia): Linux x86-64 small (2 vCPU) $0.005, medium $0.01, large $0.02; Arm small $0.0034, medium $0.007, large $0.015; Windows medium $0.018, large $0.036. EC2 builds are rounded up to the minute; Lambda compute is billed per second. Rates vary by Region. | No per-minute price. You pay standard Azure rates for the compute, storage and data egress the pool uses, plus Azure DevOps self-hosted parallel jobs: one is free and each extra one costs $15 per month. Azure Hybrid Benefit cannot be used. |
| Free tier | 100 build minutes per month on general1.small or arm1.small on-demand EC2, or 6,000 build seconds per month on 1 GB Lambda compute | One free self-hosted parallel job with unlimited minutes per Azure DevOps organization; Azure compute is still charged |
| Open source | No | No |
| Self-host / your cloud | No / Yes | No / No |
| Compliance | Not documented | Not documented |
| Regions | All AWS Regions where CodeBuild is available | Azure public cloud regions listed for the Microsoft.DevOpsInfrastructure resource provider in your subscription |
| Company headquarters | Seattle, Washington, United States | Redmond, Washington, United States |
| Good fit for | Teams on AWS that want GitHub Actions, GitLab or Buildkite jobs to run inside their own account with IAM and VPC access | Azure DevOps teams that need bigger or custom-image agents and private network access without operating scale sets |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose AWS CodeBuild-hosted runners
- You want CI jobs to run inside your own AWS account with IAM roles and VPC access
- You use GitHub Actions, GitLab or Buildkite and want one runner service for all of them
- You want single-use runners without operating an autoscaler
- You need Arm, GPU or Windows compute billed at standard CodeBuild rates
Reasons to choose Managed DevOps Pools
- You need Azure Pipelines agents more powerful than Microsoft-hosted agents
- You want agents attached to your own virtual network to reach private resources
- You want to use your own VM images or the same images as Microsoft-hosted agents
- You need jobs that run longer than six hours, up to two days
Trade-offs to check first
- AWS CodeBuild-hosted runners: macOS is not listed among the supported runner platforms, and on-demand fleets do not support macOS
- AWS CodeBuild-hosted runners: Build duration on EC2 compute is rounded up to the nearest minute
- Managed DevOps Pools: Agent VMs run in a Microsoft-owned subscription and cannot currently be accessed directly
- Managed DevOps Pools: Azure Hybrid Benefit cannot be used with Managed DevOps Pools
Run your slowest workflow on both before deciding. See the full AWS CodeBuild-hosted runners profile and Managed DevOps Pools profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs AWS CodeBuild-hosted runners
- AWS CodeBuild-hosted runners vs Elastic CI Stack for AWS
- AWS CodeBuild-hosted runners vs GitLab-hosted runners
- AWS CodeBuild-hosted runners vs RunsOn
- AWS CodeBuild-hosted runners vs terraform-aws-github-runner
- Managed DevOps Pools vs Microsoft-hosted agents
- enomem vs Managed DevOps Pools
Frequently asked questions
Is AWS CodeBuild-hosted runners or Managed DevOps Pools better?
What is the difference between AWS CodeBuild-hosted runners and Managed DevOps Pools?
Which is open source, AWS CodeBuild-hosted runners or Managed DevOps Pools?
How do AWS CodeBuild-hosted runners and Managed DevOps Pools isolate jobs?
How does AWS CodeBuild-hosted runners pricing compare with Managed DevOps Pools?
Do AWS CodeBuild-hosted runners and Managed DevOps Pools cache Docker layers?
Do AWS CodeBuild-hosted runners and Managed DevOps Pools offer GPU runners?
Where do AWS CodeBuild-hosted runners and Managed DevOps Pools runners run?
Sources
- docs.aws.amazon.com/codebuild/latest/userguide/runners.html
- docs.aws.amazon.com/codebuild/latest/userguide/action-runner-overview.html
- docs.aws.amazon.com/codebuild/latest/userguide/action-runner-questions.html
- docs.aws.amazon.com/codebuild/latest/userguide/sample-github-action-runners-update-labels.html
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/overview?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/architecture-overview?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/pricing?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/features-timeline?view=azure-devops
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). AWS CodeBuild-hosted runners vs Managed DevOps Pools. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/aws-codebuild-runners-vs-azure-managed-devops-pools/