Choosing runners that run in your own cloud account
Running runners in your own cloud account keeps code, secrets and artefacts inside your boundary, gives jobs private network access, and lets you use spot instances, credits and committed spend. You can buy a bring-your-own-cloud product that handles the orchestration, use your cloud provider’s managed runner service, or deploy an open-source autoscaler. The trade-off in every case is that the infrastructure is yours to operate.
What teams that keep CI in their own cloud need from a runner
- Supported clouds: most products are built for AWS; fewer cover Azure, Google Cloud or bare metal.
- What runs where: is the control plane in your account too, or only the runners? What does the vendor’s side see?
- Ephemeral runners: one fresh VM per job, terminated afterwards, is the model to look for.
- Start-up time: a cold cloud instance takes tens of seconds to boot. Warm pools trade money for speed.
- Spot instances: large savings, with interruption handling as part of the product.
- Networking: VPC placement, static egress IPs and private access to registries and databases.
- Fee model: flat licence, per-minute fee or free and open source. Add the cloud bill to compare.
Runners that fit, by kind
26 runners document what this workload needs. They are grouped by kind and listed alphabetically; the order is not a ranking. Shortlist two or three, then try them with your own workflows.
Managed runners for GitHub Actions
Third-party runners you switch to by changing the runs-on label in a workflow.
Depot GitHub Actions Runners
Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service.
- Single-tenant EC2 instance
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
- GPU
- BYOC
Why it fits: Depot’s docs say runners can run in its cloud or in your AWS account, the latter on the Business plan.
Full profile →Depot GitHub Actions Runners alternativesWebsite ↗
WarpBuild
Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.
- Ephemeral VM
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
- BYOC
Why it fits: WarpBuild provisions and manages runners inside your own AWS, Google Cloud or Azure account.
Runners from your CI platform or cloud
The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services.
AWS CodeBuild-hosted runners
AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job.
- Fresh build environment
- Ephemeral
- arm64
- Windows
- Docker layer cache
- GPU
- BYOC
Why it fits: Runner builds execute in your AWS account, with access to IAM, Secrets Manager, CloudTrail and Amazon VPC.
Full profile →AWS CodeBuild-hosted runners alternativesWebsite ↗
Managed DevOps Pools
Azure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates.
- Azure VM
- Windows
Why it fits: Pools are Azure resources billed through your subscription and can attach agents to a subnet of your own virtual network, although the VMs run in a Microsoft-owned subscription.
Runners in your own cloud or on your hardware
Commercial products that launch runners inside your cloud account or on servers you own.
Actuated
Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI.
- Firecracker microVM
- Ephemeral
- arm64
- Docker layer cache
- GPU
- BYOC
Why it fits: Jobs run on servers you supply, from on-premises machines to Hetzner bare metal or cloud VMs with nested virtualisation.
Aspect Workflows
Bazel-focused platform whose auto-scaling CI runners register with your existing CI and can run in your own AWS account or GCP project.
- Persistent VM
- arm64
- GPU
- BYOC
- Self-hostable
Why it fits: Aspect Enterprise can be self-hosted with Terraform in your own AWS account or GCP project.
Cirun
Hosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file.
- Cloud VM
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
- GPU
- BYOC
Why it fits: Runners are created in cloud accounts you connect, or on your own hardware through cirun-agent.
enomem
Self-hosted GitHub Actions runners on Azure: an Azure Functions handler in your subscription starts one Spot VM per job.
- Azure VM
- Ephemeral
- arm64
- Docker layer cache
- BYOC
- Self-hostable
Why it fits: The webhook handler, cache and every runner VM are deployed in your own Azure subscription.
HyperEnv for GitHub Actions Runner
AWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account.
- EC2 instance
- Ephemeral
- GPU
- BYOC
- Self-hostable
Why it fits: All components and runners are deployed by CloudFormation into your own AWS account.
Full profile →HyperEnv for GitHub Actions Runner alternativesWebsite ↗
RunsOn
Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job.
- EC2 instance
- Ephemeral
- arm64
- Windows
- Docker layer cache
- GPU
- BYOC
- Self-hostable
Why it fits: The control plane and every runner run in your own AWS account, installed by CloudFormation or Terraform.
Sprinters
GitHub App that launches one ephemeral EC2 instance per GitHub Actions job in your own AWS account, charged per job rather than per minute.
- EC2 instance
- Ephemeral
- arm64
- BYOC
Why it fits: Runner instances launch in your own AWS account, VPC and subnets through a cross-account IAM role.
Open-source autoscalers for self-hosted runners
Software you deploy to run and scale self-hosted runners on Kubernetes, cloud VMs or bare metal.
Actions Runner Controller (ARC)
Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets.
- Kubernetes pod
- Ephemeral
- Windows
- Open source
- BYOC
- Self-hostable
Why it fits: Runners are pods in a Kubernetes or OpenShift cluster that you operate.
Full profile →Actions Runner Controller (ARC) alternativesWebsite ↗
ec2-github-runner
GitHub Action that starts an EC2 instance as a self-hosted runner at the start of a workflow and terminates it at the end.
- EC2 instance
- Open source
- BYOC
- Self-hostable
Why it fits: The runner is an EC2 instance in a subnet and security group that you choose.
Elastic CI Stack for AWS
CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account.
- EC2 instance
- arm64
- Windows
- Open source
- BYOC
- Self-hostable
Why it fits: The stack creates the agents, Auto Scaling group and VPC in your own AWS account.
Full profile →Elastic CI Stack for AWS alternativesWebsite ↗
Fireactions
Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts.
- Firecracker microVM
- Ephemeral
- arm64
- Open source
- BYOC
- Self-hostable
Why it fits: It runs on your own bare-metal servers or nested-virtualization VMs.
GARM (GitHub Actions Runner Manager)
Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins.
- Depends on provider
- Ephemeral
- arm64
- Windows
- Open source
- BYOC
- Self-hostable
Why it fits: Providers create runners in your own cloud accounts, OpenStack, LXD, Incus or Kubernetes.
Full profile →GARM (GitHub Actions Runner Manager) alternativesWebsite ↗
GitLab Runner
The open-source agent that runs GitLab CI/CD jobs, with executors for Docker, Kubernetes, shell and autoscaled cloud instances.
- Depends on executor
- arm64
- macOS
- Windows
- GPU
- Open source
- BYOC
- Self-hostable
Why it fits: Fleeting plugins create job instances in your own AWS, Google Cloud or Azure account.
myshoes
Daemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS.
- Depends on provider
- Open source
- BYOC
- Self-hostable
Why it fits: Providers create runners on your own LXD hosts, OpenStack cloud or AWS account.
terraform-aws-github-runner
Terraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions.
- EC2 instance
- arm64
- macOS
- Windows
- GPU
- Open source
- BYOC
- Self-hostable
Why it fits: Runners are EC2 instances in your own VPC and subnets.
Full profile →terraform-aws-github-runner alternativesWebsite ↗
terraform-aws-gitlab-runner
Terraform module that deploys GitLab Runner on AWS and autoscales its job workers on EC2 spot instances.
- EC2 instance
- Open source
- BYOC
- Self-hostable
Why it fits: All instances, the cache bucket and the Lambda functions are created in your own AWS account.
Full profile →terraform-aws-gitlab-runner alternativesWebsite ↗
TestFlows GitHub Hetzner Runners
Self-contained Python service that creates a Hetzner Cloud server for each queued GitHub Actions job, with no webhooks or GitHub App.
- Hetzner Cloud VM
- Ephemeral
- arm64
- Docker layer cache
- Open source
- BYOC
- Self-hostable
Why it fits: Servers are created in your own Hetzner Cloud project.
Full profile →TestFlows GitHub Hetzner Runners alternativesWebsite ↗
macOS runners for iOS and Mac builds
Apple-silicon runners and virtualization tools for building and testing iOS and macOS apps.
Anka Build Cloud
Commercial macOS virtualization for CI: a controller and registry manage on-demand Anka VMs on your own Macs, hosted Macs or AWS EC2 Mac.
- macOS VM
- Ephemeral
- arm64
- macOS
- GPU
- BYOC
- Self-hostable
Why it fits: The software runs on your own Mac hardware or AWS EC2 Mac instances, with an official Anka AMI on AWS Marketplace.
Cilicon
Open-source macOS app that runs ephemeral CI virtual machines on a single Apple silicon Mac using Apple’s Virtualization framework.
- macOS VM
- Ephemeral
- arm64
- macOS
- Open source
- BYOC
- Self-hostable
Why it fits: Everything runs on your own Mac hardware.
Orka
Kubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs.
- macOS VM
- arm64
- macOS
- BYOC
- Self-hostable
Why it fits: Orka can be deployed on AWS EC2 Mac instances in your own account or on Mac hardware you own.
Tart
Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs.
- Apple Virtualization VM
- Ephemeral
- arm64
- macOS
- BYOC
- Self-hostable
Why it fits: Tart and Orchard run entirely on Mac hardware you operate.
Tartelet
Open-source macOS app that runs up to two GitHub Actions runners in ephemeral Tart virtual machines on a single Mac.
- Tart VM
- Ephemeral
- arm64
- macOS
- Open source
- BYOC
- Self-hostable
Why it fits: Runners live on your own Mac; nothing is hosted by a vendor.
Side by side
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| Actuated | GitHub Actions, GitLab CI | Linux, x64, arm64 | Your cloud or hardware | Firecracker microVM | $150/mo per server + your servers | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Anka Build Cloud | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | macOS, arm64, x64 | Your cloud or hardware | macOS VM | Not documented | Set by your infrastructure | Not documented | Yes | No | United States |
| Aspect Workflows | GitHub Actions, Buildkite, GitLab CI, CircleCI | Linux, x64, arm64 | Your cloud or hardware | Persistent VM | Annual platform fee (quote) + cloud cost | Set by your infrastructure | Not documented | Yes | No | Not documented |
| AWS CodeBuild-hosted runners | GitHub Actions, GitLab CI, Buildkite | Linux, Windows, x64, arm64 | Your cloud account | Fresh build environment | $0.005/min | 72 vCPU / 144 GB | Yes | Yes | No | United States |
| Cilicon | GitHub Actions, GitLab CI, Buildkite | macOS, arm64 | Self-hosted | macOS VM | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Depot GitHub Actions Runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Single-tenant EC2 instance | $0.006/min | 64 vCPU / 256 GB | Yes | Yes | No | Not documented |
| ec2-github-runner | GitHub Actions | Linux | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| Elastic CI Stack for AWS | Buildkite | Linux, Windows, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Australia |
| enomem | GitHub Actions | Linux, x64, arm64 | Your cloud or hardware | Azure VM | $25/mo licence + Azure cost | 96 vCPU / 384 GB | Yes | Not documented | Not documented | Not documented |
| Fireactions | GitHub Actions | Linux, x64, arm64 | Self-hosted | Firecracker microVM | Free software + your infrastructure | Set by your infrastructure | Not documented | No | Yes | Lithuania |
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | Linux, Windows, x64, arm64 | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Romania |
| GitLab Runner | GitLab CI | Linux, macOS, Windows, x64, arm64 | Self-hosted | Depends on executor | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| HyperEnv for GitHub Actions Runner | GitHub Actions | Linux, x64 | Your cloud or hardware | EC2 instance | $0.002/min fee + AWS cost | 192 vCPU / 768 GB | Not documented | Yes | No | Germany |
| Managed DevOps Pools | Azure Pipelines | Linux, Windows, x64 | Platform-hosted | Azure VM | $15/month per parallel job + Azure VM cost | Not documented | Not documented | Not documented | No | United States |
| myshoes | GitHub Actions | Linux | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| Orka | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | macOS, arm64 | Your cloud or hardware | macOS VM | From $109/mo per hosted Mac mini (Orka by quote) | Set by your infrastructure | Not documented | Not documented | No | United States |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| Sprinters | GitHub Actions | Linux, x64, arm64 | Your cloud or hardware | EC2 instance | $0.01/job + AWS cost | 384 vCPU / 3072 GB | Not documented | Not documented | No | Germany |
| Tart | GitLab CI, Buildkite, GitHub Actions | macOS, Linux, arm64 | Your cloud or hardware | Apple Virtualization VM | Not documented | Set by your infrastructure | Not documented | Not documented | No | United States |
| Tartelet | GitHub Actions | macOS, arm64 | Self-hosted | Tart VM | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| terraform-aws-github-runner | GitHub Actions | Linux, Windows, macOS, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| terraform-aws-gitlab-runner | GitLab CI | Linux | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| TestFlows GitHub Hetzner Runners | GitHub Actions | Linux, x64, arm64 | Self-hosted | Hetzner Cloud VM | Free software + your infrastructure | Set by your infrastructure | Yes | Not documented | Yes | Not documented |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
Frequently asked questions
What does BYOC mean for CI runners?
Is running runners in my own AWS account cheaper?
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). Choosing runners that run in your own cloud account. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/use-cases/byoc/