AWS CodeBuild-hosted runners vs GitLab-hosted runners
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. 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. 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; GitLab-hosted runners is the CI platform’s own hosted runners for GitLab CI, priced at $10 per 1,000 compute minutes.
Key differences between AWS CodeBuild-hosted runners and GitLab-hosted runners
- Type: AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account; GitLab-hosted runners is the CI platform’s own hosted runners.
- CI systems: Only AWS CodeBuild-hosted runners documents GitHub Actions and Buildkite.
- Operating systems: Only GitLab-hosted runners documents macOS.
- Isolation: AWS CodeBuild-hosted runners: Fresh build environment. GitLab-hosted runners: Ephemeral VM.
- Published price: $0.005/min (AWS CodeBuild-hosted runners) versus $10 per 1,000 compute minutes (GitLab-hosted runners).
- Largest runner: 72 vCPU / 144 GB (AWS CodeBuild-hosted runners) versus 32 vCPU / 128 GB (GitLab-hosted runners).
- Your own cloud account: AWS CodeBuild-hosted runners documents running in your own cloud account; GitLab-hosted runners does not.
What they have in common
- Both run GitLab CI jobs.
- Both document Linux and Windows runners.
- Both document arm64 runners.
- Both give every job a fresh environment.
- Neither is open source.
- Both document GPU runners.
AWS CodeBuild-hosted runners vs GitLab-hosted runners at a glance
| Attribute | AWS CodeBuild-hosted runners | GitLab-hosted runners |
|---|---|---|
| What it is | AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job. | GitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size. |
| Type | Cloud provider service | First-party hosted runners |
| CI systems | GitHub Actions, GitLab CI, Buildkite | GitLab CI |
| Operating systems | Linux, Windows | Linux, macOS, Windows |
| Architectures | x64, arm64 | x64, arm64 |
| 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 | 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 |
| Fresh environment per job | Yes | Yes |
| 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 | 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 |
| 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 | 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 |
| 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. | 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 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. | 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. |
| Concurrency | Concurrently running builds are capped by per-Region service quotas for each environment type, which AWS lists as adjustable | Maximum jobs in active pipelines on GitLab.com: 500 on Free, 20,000 on Premium and 60,000 on Ultimate |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Not documented | Not documented |
| 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 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 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 | 400 compute minutes per month on the Free tier; Premium includes 10,000 and Ultimate 50,000 per month |
| 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 | Linux x86-64 VMs run in Google Cloud us-east1 and us-east5; Linux Arm64 VMs run in us-central1 |
| Company headquarters | Seattle, Washington, United States | Not documented |
| 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 | Teams 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 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 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
- 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
- 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 AWS CodeBuild-hosted runners profile and GitLab-hosted runners 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 Managed DevOps Pools
- AWS CodeBuild-hosted runners vs RunsOn
- AWS CodeBuild-hosted runners vs terraform-aws-github-runner
- Buildkite hosted agents vs GitLab-hosted runners
- GitHub-hosted runners vs GitLab-hosted runners
- GitLab Runner vs GitLab-hosted runners
- GitLab-hosted runners vs Microsoft-hosted agents
- GitLab-hosted runners vs RunJob
Frequently asked questions
Is AWS CodeBuild-hosted runners or GitLab-hosted runners better?
What is the difference between AWS CodeBuild-hosted runners and GitLab-hosted runners?
Which is open source, AWS CodeBuild-hosted runners or GitLab-hosted runners?
How do AWS CodeBuild-hosted runners and GitLab-hosted runners isolate jobs?
How does AWS CodeBuild-hosted runners pricing compare with GitLab-hosted runners?
Do AWS CodeBuild-hosted runners and GitLab-hosted runners cache Docker layers?
Do AWS CodeBuild-hosted runners and GitLab-hosted runners offer GPU runners?
Where do AWS CodeBuild-hosted runners and GitLab-hosted runners 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
- 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/
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 GitLab-hosted runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/aws-codebuild-runners-vs-gitlab-hosted-runners/