CI Runnerscirunners.org
Head-to-head

Buildkite hosted agents vs Elastic CI Stack for AWS

Answer in brief

Buildkite hosted agents suits teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. Elastic CI Stack for AWS suits Buildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template. Buildkite hosted agents is the CI platform’s own hosted runners for Buildkite, priced at $0.008/min; Elastic CI Stack for AWS is an open-source project you run yourself for Buildkite.

By the CI Runners editors · Updated

Key differences between Buildkite hosted agents and Elastic CI Stack for AWS

  • Type: Buildkite hosted agents is the CI platform’s own hosted runners; Elastic CI Stack for AWS is an open-source project you run yourself.
  • Operating systems: Only Buildkite hosted agents documents macOS.
  • Isolation: Buildkite hosted agents: Ephemeral virtualized environment. Elastic CI Stack for AWS: EC2 instance.
  • Open source: Elastic CI Stack for AWS is open source (MIT); Buildkite hosted agents is not.
  • Self-hosting: Elastic CI Stack for AWS documents a self-hosted option; Buildkite hosted agents does not.
  • Your own cloud account: Elastic CI Stack for AWS documents running in your own cloud account; Buildkite hosted agents does not.

What they have in common

  • Both are from Buildkite Pty Ltd.
  • Both run Buildkite jobs.
  • Both document Linux and Windows runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.

Buildkite hosted agents vs Elastic CI Stack for AWS at a glance

AttributeBuildkite hosted agentsElastic CI Stack for AWS
What it isBuildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute.CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account.
TypeFirst-party hosted runnersOpen-source project
CI systemsBuildkiteBuildkite
Operating systemsLinux, macOS, WindowsLinux, 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 customersAgents run on EC2 instances in an Auto Scaling group inside your VPC; instances are reused between jobs by default, and a template parameter can terminate the instance after each job
Fresh environment per jobYesNot documented
HardwareBuildkite says it uses latest-generation Mac (M4) and AMD Zen-based hardware in a private cloud, with cache volumes on local NVMe-attached disksEC2 instance types set with the InstanceTypes parameter (default t3.large); local NVMe instance storage can be enabled on Linux
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 GBNot documented
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.Git mirrors can be enabled as an agent experiment, and on Linux the builds directory can be placed on local NVMe instance storage.
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 EnterpriseTemplate defaults are MinSize 0 and MaxSize 10 instances with one agent per instance; all three are configurable
Static IPsYesNot documented
SSH into running jobsYesYes
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.Free and open source; you pay for the infrastructure it runs on. Buildkite notes that the AWS services are pay-as-you-go and that Buildkite services are billed according to your plan.
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 cardNot documented
Open sourceNoYes (MIT)
Self-host / your cloudNo / NoYes / Yes
ComplianceSOC 2 Type IINot documented
RegionsUS East Coast data centers onlyAll AWS Regions except China and US GovCloud
Company headquartersNot documentedMelbourne, Victoria, Australia
Good fit forTeams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machinesBuildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template

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 Elastic CI Stack for AWS

  • You use Buildkite and want agents inside your own AWS account and VPC
  • You want a template maintained by Buildkite, with prebuilt Linux and Windows AMIs
  • You want the fleet to scale with build activity and down to a minimum of zero instances
  • You need Linux on x86 and Arm as well as Windows Server agents

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
  • Elastic CI Stack for AWS: The README states that the repository has not been reviewed by security researchers
  • Elastic CI Stack for AWS: Builds can reach the EC2 metadata server and act with the IAM permissions of the instance

Run your slowest workflow on both before deciding. See the full Buildkite hosted agents profile and Elastic CI Stack for AWS profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Buildkite hosted agents or Elastic CI Stack for AWS 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. Elastic CI Stack for AWS suits Buildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template.
What is the difference between Buildkite hosted agents and Elastic CI Stack for AWS?
Buildkite hosted agents is the CI platform’s own hosted runners; Elastic CI Stack for AWS is an open-source project you run yourself. Only Buildkite hosted agents documents macOS. Isolation is Ephemeral virtualized environment on Buildkite hosted agents and EC2 instance on Elastic CI Stack for AWS. Elastic CI Stack for AWS is open source (MIT); Buildkite hosted agents is not. Elastic CI Stack for AWS documents a self-hosted option; Buildkite hosted agents does not.
Which is open source, Buildkite hosted agents or Elastic CI Stack for AWS?
Buildkite hosted agents is not open source; Elastic CI Stack for AWS is open source (MIT).
How do Buildkite hosted agents and Elastic CI Stack for AWS 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. Elastic CI Stack for AWS: Agents run on EC2 instances in an Auto Scaling group inside your VPC; instances are reused between jobs by default, and a template parameter can terminate the instance after each job.
How does Buildkite hosted agents pricing compare with Elastic CI Stack for AWS?
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. Elastic CI Stack for AWS: Free and open source; you pay for the infrastructure it runs on. Buildkite notes that the AWS services are pay-as-you-go and that Buildkite services are billed according to your plan. Rates change, so check the Buildkite hosted agents and Elastic CI Stack for AWS pricing pages before deciding.
Is Buildkite hosted agents or Elastic CI Stack for AWS 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). Elastic CI Stack for AWS: Not documented.
Do Buildkite hosted agents and Elastic CI Stack for AWS 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. Elastic CI Stack for AWS: Docker layer caching is not documented.
Where do Buildkite hosted agents and Elastic CI Stack for AWS runners run?
Buildkite hosted agents is the CI platform’s own hosted runners. Elastic CI Stack for AWS is an open-source project you run yourself (AWS).

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. github.com/buildkite/elastic-ci-stack-for-aws
  6. github.com/buildkite/elastic-ci-stack-for-aws/releases
  7. github.com/buildkite/elastic-ci-stack-for-aws/blob/main/Licence.md
  8. github.com/buildkite/elastic-ci-stack-for-aws/blob/main/templates/aws-stack.yml

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 Elastic CI Stack for AWS. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/buildkite-hosted-agents-vs-buildkite-elastic-ci-stack/