CI Runnerscirunners.org
Use case · Your own cloud

Choosing runners that run in your own cloud account

Answer in brief

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.

By the CI Runners editors · Updated

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.

  • 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.

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.

  • 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.

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

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
Anka Build CloudGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCitymacOS, arm64, x64Your cloud or hardwaremacOS VMNot documentedSet by your infrastructureNot documentedYesNoUnited States
Aspect WorkflowsGitHub Actions, Buildkite, GitLab CI, CircleCILinux, x64, arm64Your cloud or hardwarePersistent VMAnnual platform fee (quote) + cloud costSet by your infrastructureNot documentedYesNoNot documented
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
CiliconGitHub Actions, GitLab CI, BuildkitemacOS, arm64Self-hostedmacOS VMFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
ec2-github-runnerGitHub ActionsLinuxSelf-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
Elastic CI Stack for AWSBuildkiteLinux, Windows, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesAustralia
enomemGitHub ActionsLinux, x64, arm64Your cloud or hardwareAzure VM$25/mo licence + Azure cost96 vCPU / 384 GBYesNot documentedNot documentedNot documented
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
GitLab RunnerGitLab CILinux, macOS, Windows, x64, arm64Self-hostedDepends on executorFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
HyperEnv for GitHub Actions RunnerGitHub ActionsLinux, x64Your cloud or hardwareEC2 instance$0.002/min fee + AWS cost192 vCPU / 768 GBNot documentedYesNoGermany
Managed DevOps PoolsAzure PipelinesLinux, Windows, x64Platform-hostedAzure VM$15/month per parallel job + Azure VM costNot documentedNot documentedNot documentedNoUnited States
myshoesGitHub ActionsLinuxSelf-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
OrkaGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCitymacOS, arm64Your cloud or hardwaremacOS VMFrom $109/mo per hosted Mac mini (Orka by quote)Set by your infrastructureNot documentedNot documentedNoUnited States
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
SprintersGitHub ActionsLinux, x64, arm64Your cloud or hardwareEC2 instance$0.01/job + AWS cost384 vCPU / 3072 GBNot documentedNot documentedNoGermany
TartGitLab CI, Buildkite, GitHub ActionsmacOS, Linux, arm64Your cloud or hardwareApple Virtualization VMNot documentedSet by your infrastructureNot documentedNot documentedNoUnited States
TarteletGitHub ActionsmacOS, arm64Self-hostedTart VMFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
terraform-aws-gitlab-runnerGitLab CILinuxSelf-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
TestFlows GitHub Hetzner RunnersGitHub ActionsLinux, x64, arm64Self-hostedHetzner Cloud VMFree software + your infrastructureSet by your infrastructureYesNot documentedYesNot documented
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented

Frequently asked questions

What does BYOC mean for CI runners?
Bring your own cloud: the runners are virtual machines in your own cloud account rather than the vendor’s. A control plane starts one for each queued job and terminates it afterwards. You pay your cloud provider for the compute and the vendor a licence or usage fee. See the glossary entry.
Is running runners in my own AWS account cheaper?
The compute usually is, especially on spot instances, because you pay the raw instance price. Add the product’s fee, storage, data transfer and NAT costs, and the engineering time to keep it running, before comparing with a managed runner’s per-minute rate.

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/