Aspect Workflows vs Elastic CI Stack for AWS
Aspect Workflows suits Bazel monorepo teams that want warm, persistent CI runners in their own AWS or GCP account alongside remote cache and remote execution. 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. Aspect Workflows is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, Buildkite, GitLab CI and CircleCI, priced at Annual platform fee (quote) + cloud cost; Elastic CI Stack for AWS is an open-source project you run yourself for Buildkite.
Key differences between Aspect Workflows and Elastic CI Stack for AWS
- Type: Aspect Workflows is a product that runs runners in your own cloud account or on your own hardware; Elastic CI Stack for AWS is an open-source project you run yourself.
- CI systems: Only Aspect Workflows documents GitHub Actions, GitLab CI and CircleCI.
- Operating systems: Only Elastic CI Stack for AWS documents Windows.
- Isolation: Aspect Workflows: Persistent VM. Elastic CI Stack for AWS: EC2 instance.
- Open source: Elastic CI Stack for AWS is open source (MIT); Aspect Workflows is not.
What they have in common
- Both run Buildkite jobs.
- Both document Linux runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Both can be self-hosted.
Aspect Workflows vs Elastic CI Stack for AWS at a glance
| Attribute | Aspect Workflows | Elastic CI Stack for AWS |
|---|---|---|
| What it is | Bazel-focused platform whose auto-scaling CI runners register with your existing CI and can run in your own AWS account or GCP project. | CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account. |
| Type | Runs in your cloud or on your hardware | Open-source project |
| CI systems | GitHub Actions, Buildkite, GitLab CI, CircleCI | Buildkite |
| Operating systems | Linux | Linux, Windows |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Persistent Linux VMs in runner groups take jobs one after another so Bazel state stays warm; isolation between jobs is not documented | 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 |
| Fresh environment per job | No | Not documented |
| Hardware | Any AWS or GCP instance type per runner group, with local NVMe for the Bazel output base. | EC2 instance types set with the InstanceTypes parameter (default t3.large); local NVMe instance storage can be enabled on Linux |
| Performance (vendor claim) | Aspect says cached builds routinely finish in under a minute on its runners (vendor claim) | Not documented |
| Runner sizes | Any AWS or GCP instance type, configured per runner group | Not documented |
| Caching | Runners keep the Bazel output base on NVMe between jobs and restore a warming archive on boot. The deployment includes a remote cache backed by S3 Express One Zone on AWS or Cloud Storage on GCP. | 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 caching | Not documented | Not documented |
| GPU | GPU runner groups can use GPU instance types offered by AWS or GCP; no GPU models or prices are published. | Not documented |
| Concurrency | Set per runner group through minimum size, maximum size and idle runners; the Enterprise fee is priced by a vCPU ceiling | Template defaults are MinSize 0 and MaxSize 10 instances with one agent per instance; all three are configurable |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Not documented | Yes |
| Pricing | CI runners are part of Aspect Enterprise, which has an annual platform fee based on the vCPU ceiling set for remote execution and CI runners, the deployment shape and the support level; no amount is published. When self-hosted, compute is billed by your cloud provider. | 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 tier | 30-day trial of Aspect Enterprise | Not documented |
| Open source | No | Yes (MIT) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | SOC 2 Type 2 | Not documented |
| Regions | Your own AWS account or GCP project, including AWS GovCloud and GCP Assured Workloads | All AWS Regions except China and US GovCloud |
| Company headquarters | Not documented | Melbourne, Victoria, Australia |
| Good fit for | Bazel monorepo teams that want warm, persistent CI runners in their own AWS or GCP account alongside remote cache and remote execution | Buildkite 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 Aspect Workflows
- You build with Bazel and want runners that keep the output base and analysis cache warm between jobs
- You want the runners, remote cache and remote execution on one private network in your own AWS account or GCP project
- You use Buildkite, GitLab or CircleCI rather than only GitHub Actions
- You need air-gapped, AWS GovCloud or GCP Assured Workloads deployments
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
- Aspect Workflows: Runners are persistent and take jobs one after another rather than being single-use
- Aspect Workflows: CI runners are available only on Aspect Enterprise, not on Aspect Cloud
- 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 Aspect Workflows profile and Elastic CI Stack for AWS profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Aspect Workflows or Elastic CI Stack for AWS better?
What is the difference between Aspect Workflows and Elastic CI Stack for AWS?
Which is open source, Aspect Workflows or Elastic CI Stack for AWS?
How do Aspect Workflows and Elastic CI Stack for AWS isolate jobs?
How does Aspect Workflows pricing compare with Elastic CI Stack for AWS?
Is Aspect Workflows or Elastic CI Stack for AWS faster?
Do Aspect Workflows and Elastic CI Stack for AWS offer GPU runners?
Where do Aspect Workflows and Elastic CI Stack for AWS runners run?
Sources
- aspect.build/ci-runners
- aspect.build/pricing
- aspect.build/docs/aspect-workflows/get-started/overview
- aspect.build/docs/aspect-workflows/features/ci-runners
- github.com/buildkite/elastic-ci-stack-for-aws
- github.com/buildkite/elastic-ci-stack-for-aws/releases
- github.com/buildkite/elastic-ci-stack-for-aws/blob/main/Licence.md
- 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). Aspect Workflows vs Elastic CI Stack for AWS. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/aspect-workflows-vs-buildkite-elastic-ci-stack/