# CI Runners > Independent, source-cited comparison of CI runners for GitHub Actions and GitLab CI: Blacksmith, Depot, Namespace, WarpBuild, RunsOn, GitHub-hosted and more. Pricing, hardware, caching, isolation and which runner fits your pipeline. CI Runners (cirunners.org) is an independent, source-cited reference on CI runners: the machines that execute continuous-integration jobs for GitHub Actions, GitLab CI, Buildkite and Azure Pipelines. It profiles 41 active runner services and open-source projects. No provider pays for placement. Facts are attributed to provider documentation and dated; speed and savings figures are vendor claims. Last reviewed: 2026-11-22. Quick answer: There is no single best CI runner; the right one depends on your pipeline. Start with which CI system you use (34 of the 41 runners here work with GitHub Actions). Then narrow by what your jobs run on (Linux, arm64, macOS, Windows), where the runners must run (a vendor’s cloud, your cloud account or your own hardware) and how isolated each job must be. The finder on this page scores 41 runners against those answers from their own documentation, and the 5 kinds below explain the landscape. Disclaimer: general information, provided as is and without warranty. It is not professional advice. Product details change, so confirm them with each provider. Terms: https://cirunners.org/terms/ ## Core pages - [Find the right runner for your CI pipeline](https://cirunners.org/): Independent guide to choosing a CI runner: 41 options for GitHub Actions, GitLab CI and more, compared on price, hardware, caching and isolation. - [CI runner directory](https://cirunners.org/runners/): Directory of 41 CI runner services and open-source projects in 5 kinds, from managed GitHub Actions runners to self-hosted autoscalers. - [Compare CI runners](https://cirunners.org/compare/): Compare 41 CI runners side by side: CI systems, operating systems, deployment, isolation, price, largest size, Docker caching and GPUs. - [CI runners by use case](https://cirunners.org/use-cases/): How to choose a CI runner for each goal: faster builds, lower cost, Docker builds, ARM64, macOS and iOS, Windows, GPUs, your own cloud and security. - [CI runner providers by country](https://cirunners.org/locations/): Where the companies behind 24 CI runner products are headquartered, grouped by country, with a source for each location. - [Methodology: how we evaluate CI runners](https://cirunners.org/methodology/): How cirunners.org selects, documents and organizes CI runner providers: sources, criteria, categories, use-case fit and update cadence. ## Kinds of CI runner - [Managed runners for GitHub Actions](https://cirunners.org/#managed-github-actions): Third-party runners you switch to by changing the runs-on label in a workflow. Includes Avrea, Blacksmith, BuildPulse Runners, CRACI, Depot GitHub Actions Runners, Luxor Runners, machine.dev, Namespace, RunJob, Ubicloud Runners, WarpBuild. - [Runners from your CI platform or cloud](https://cirunners.org/#platform-hosted): The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services. Includes AWS CodeBuild-hosted runners, Managed DevOps Pools, Microsoft-hosted agents, Buildkite hosted agents, GitHub-hosted runners, GitLab-hosted runners. - [Runners in your own cloud or on your hardware](https://cirunners.org/#your-cloud): Commercial products that launch runners inside your cloud account or on servers you own. Includes Actuated, Aspect Workflows, Cirun, enomem, HyperEnv for GitHub Actions Runner, RunsOn, Sprinters. - [Open-source autoscalers for self-hosted runners](https://cirunners.org/#open-source-autoscalers): Software you deploy to run and scale self-hosted runners on Kubernetes, cloud VMs or bare metal. Includes Actions Runner Controller (ARC), Elastic CI Stack for AWS, ec2-github-runner, Fireactions, GARM (GitHub Actions Runner Manager), TestFlows GitHub Hetzner Runners, GitLab Runner, myshoes, terraform-aws-github-runner, terraform-aws-gitlab-runner. - [macOS runners for iOS and Mac builds](https://cirunners.org/#macos): Apple-silicon runners and virtualization tools for building and testing iOS and macOS apps. Includes Bitrise Build Hub, Cilicon, GetMac, Orka, Tart, Tartelet, Anka Build Cloud. ## Runners by use case - [Choosing a runner to speed up GitHub Actions](https://cirunners.org/use-cases/faster-builds/): How to choose a CI runner for faster GitHub Actions builds: CPU speed, core count, cache location and Docker layer reuse, with the runners that fit. - [Choosing a runner to cut your CI bill](https://cirunners.org/use-cases/lower-cost/): How to cut GitHub Actions and CI costs: per-minute rates, faster jobs, spot instances in your own cloud and free allowances, with the runners that fit. - [Choosing a runner for Docker image builds](https://cirunners.org/use-cases/docker-builds/): How to choose a CI runner for Docker image builds: layer caching, persistent build state, multi-platform images and native arm64, with runners that fit. - [Choosing a runner for native ARM64 builds](https://cirunners.org/use-cases/arm64/): How to choose an ARM64 CI runner for GitHub Actions or GitLab: native arm64 builds, sizes, prices and Docker multi-arch support, with runners that fit. - [Choosing a macOS runner for iOS and Mac builds](https://cirunners.org/use-cases/macos-ios/): How to choose a macOS CI runner for iOS and Mac apps: Apple silicon generation, Xcode versions, per-minute vs dedicated hosts and VM isolation. - [Choosing a runner for Windows builds](https://cirunners.org/use-cases/windows/): How to choose a Windows CI runner: Windows Server images, toolchain preinstalls, per-minute price and start-up time, with the runners that fit. - [Choosing a runner for GPU jobs](https://cirunners.org/use-cases/gpu/): How to choose a GPU CI runner for model tests, training smoke tests and CUDA builds: GPU models, per-minute price, drivers and availability. - [Choosing runners that run in your own cloud account](https://cirunners.org/use-cases/byoc/): How to run GitHub Actions and GitLab runners in your own AWS, Azure or Google Cloud account: BYOC products, cloud services and open-source autoscalers. - [Choosing open-source, self-hosted runner infrastructure](https://cirunners.org/use-cases/open-source/): Open-source ways to run and autoscale self-hosted CI runners: Kubernetes controllers, cloud autoscalers and Firecracker managers, with trade-offs. - [Choosing runners for GitLab CI](https://cirunners.org/use-cases/gitlab/): How to choose GitLab CI runners: GitLab-hosted runners and compute minutes, self-managed GitLab Runner with autoscaling, and third-party options. - [Choosing a runner for untrusted code and compliance](https://cirunners.org/use-cases/security/): How to choose a CI runner when security matters: ephemeral VMs per job, public-repository risk, network egress control, static IPs and compliance. ## Provider profiles - [Orka](https://cirunners.org/runners/macstadium-orka/): Orka: Kubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs. - [Tart](https://cirunners.org/runners/tart/): Tart: Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs. - [GetMac](https://cirunners.org/runners/getmac/): GetMac: Managed macOS runners on vendor-owned Apple silicon M4 hardware in Lithuania, sold as monthly plans of included compute minutes. - [Bitrise Build Hub](https://cirunners.org/runners/bitrise-runners/): Bitrise-managed macOS and Linux runners for GitHub Actions on Bitrise-owned Apple silicon and AMD EPYC machines, sold as monthly compute budgets. - [FlyCI macOS Runners (discontinued)](https://cirunners.org/runners/flyci/): FlyCI macOS Runners: Managed Apple silicon macOS runners for GitHub Actions that FlyCI discontinued on September 30, 2024. Pricing, hardware and caching. - [Anka Build Cloud](https://cirunners.org/runners/veertu-anka/): 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. - [Cilicon](https://cirunners.org/runners/cilicon/): Cilicon: Open-source macOS app that runs ephemeral CI virtual machines on a single Apple silicon Mac using Apple’s Virtualization framework. - [Tartelet](https://cirunners.org/runners/tartelet/): Tartelet: Open-source macOS app that runs up to two GitHub Actions runners in ephemeral Tart virtual machines on a single Mac. Features, setup and limits. - [Blacksmith](https://cirunners.org/runners/blacksmith/): Blacksmith: Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners. - [Depot GitHub Actions Runners](https://cirunners.org/runners/depot/): Depot GitHub Actions Runners: Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service. - [Namespace](https://cirunners.org/runners/namespace/): Namespace: Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. - [WarpBuild](https://cirunners.org/runners/warpbuild/): WarpBuild: Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account. - [BuildJet for GitHub Actions (discontinued)](https://cirunners.org/runners/buildjet/): BuildJet for GitHub Actions: Managed GitHub Actions runners on dedicated bare metal; shut down in 2026 and no longer running jobs. - [Ubicloud Runners](https://cirunners.org/runners/ubicloud/): Ubicloud Runners: Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal. - [Luxor Runners](https://cirunners.org/runners/luxor-runners/): Luxor Runners: GitHub Actions runners on bare-metal Linux x64 and Apple Silicon macOS, one single-use VM per job; called Tenki until November 2026. - [Cirrus Runners (closed to new customers)](https://cirunners.org/runners/cirrus-runners/): Cirrus Runners: Flat-rate GitHub Actions runners for macOS and Linux, priced per concurrent runner; closed to new customers since April 2026. - [machine.dev](https://cirunners.org/runners/machine/): machine.dev: GPU, x64 and arm64 runners for GitHub Actions on dedicated AWS instances, with spot or on-demand tenancy chosen in the runs-on label. - [RunJob](https://cirunners.org/runners/runjob/): RunJob: EU-based managed runners for GitHub Actions and GitLab CI that run each job in a fresh KVM virtual machine and bill only CPU and memory used. - [BuildPulse Runners](https://cirunners.org/runners/buildpulse-runners/): BuildPulse Runners: Managed Linux runners for GitHub Actions, CircleCI and Semaphore with included cache storage and flaky-test detection on every run. - [Avrea](https://cirunners.org/runners/avrea/): Avrea: Managed GitHub Actions runners for Linux, macOS and Windows on dedicated hardware, with colocated caches and SSH into running jobs. - [CRACI](https://cirunners.org/runners/craci/): CRACI: Managed Linux runners for GitHub Actions on European bare metal that record a build-time SBOM and apply an egress policy to each job. - [Actions Runner Controller (ARC)](https://cirunners.org/runners/actions-runner-controller/): Actions Runner Controller (ARC): Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets. - [terraform-aws-github-runner](https://cirunners.org/runners/terraform-aws-github-runner/): terraform-aws-github-runner: Terraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions. - [GARM (GitHub Actions Runner Manager)](https://cirunners.org/runners/garm/): Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins. - [GitLab Runner](https://cirunners.org/runners/gitlab-runner/): GitLab Runner: The open-source agent that runs GitLab CI/CD jobs, with executors for Docker, Kubernetes, shell and autoscaled cloud instances. - [Fireactions](https://cirunners.org/runners/fireactions/): Fireactions: Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts. - [myshoes](https://cirunners.org/runners/myshoes/): myshoes: Daemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS. - [TestFlows GitHub Hetzner Runners](https://cirunners.org/runners/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. - [Elastic CI Stack for AWS](https://cirunners.org/runners/buildkite-elastic-ci-stack/): CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account. - [ec2-github-runner](https://cirunners.org/runners/ec2-github-runner/): 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. - [terraform-aws-gitlab-runner](https://cirunners.org/runners/terraform-aws-gitlab-runner/): terraform-aws-gitlab-runner: Terraform module that deploys GitLab Runner on AWS and autoscales its job workers on EC2 spot instances. - [GitHub-hosted runners](https://cirunners.org/runners/github-hosted-runners/): GitHub-hosted runners: GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute. - [GitLab-hosted runners](https://cirunners.org/runners/gitlab-hosted-runners/): GitLab-hosted runners: GitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size. - [Buildkite hosted agents](https://cirunners.org/runners/buildkite-hosted-agents/): Buildkite hosted agents: Buildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute. - [Microsoft-hosted agents](https://cirunners.org/runners/azure-pipelines-agents/): Azure Pipelines’ built-in agents: a fresh 2-core VM per job on Windows, Linux or macOS, sold per parallel job rather than per minute. - [AWS CodeBuild-hosted runners](https://cirunners.org/runners/aws-codebuild-runners/): 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. - [Managed DevOps Pools](https://cirunners.org/runners/azure-managed-devops-pools/): Managed DevOps Pools: Azure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates. - [RunsOn](https://cirunners.org/runners/runs-on/): RunsOn: Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job. - [Cirun](https://cirunners.org/runners/cirun/): 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. - [Actuated](https://cirunners.org/runners/actuated/): Actuated: Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI. - [Sprinters](https://cirunners.org/runners/sprinters/): 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. - [HyperEnv for GitHub Actions Runner](https://cirunners.org/runners/hyperenv/): AWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account. - [Aspect Workflows](https://cirunners.org/runners/aspect-workflows/): 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. - [enomem](https://cirunners.org/runners/enomem/): enomem: Self-hosted GitHub Actions runners on Azure: an Azure Functions handler in your subscription starts one Spot VM per job. ## Head-to-head comparisons - [Actions Runner Controller (ARC) vs Actuated](https://cirunners.org/compare/actions-runner-controller-vs-actuated/) - [Actions Runner Controller (ARC) vs AWS CodeBuild-hosted runners](https://cirunners.org/compare/actions-runner-controller-vs-aws-codebuild-runners/) - [Actions Runner Controller (ARC) vs Fireactions](https://cirunners.org/compare/actions-runner-controller-vs-fireactions/) - [Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager)](https://cirunners.org/compare/actions-runner-controller-vs-garm/) - [Actions Runner Controller (ARC) vs GitHub-hosted runners](https://cirunners.org/compare/actions-runner-controller-vs-github-hosted-runners/) - [Actions Runner Controller (ARC) vs RunsOn](https://cirunners.org/compare/actions-runner-controller-vs-runs-on/) - [Actions Runner Controller (ARC) vs terraform-aws-github-runner](https://cirunners.org/compare/actions-runner-controller-vs-terraform-aws-github-runner/) - [Actuated vs Cirun](https://cirunners.org/compare/actuated-vs-cirun/) - [Actuated vs Fireactions](https://cirunners.org/compare/actuated-vs-fireactions/) - [Actuated vs RunsOn](https://cirunners.org/compare/actuated-vs-runs-on/) - [AWS CodeBuild-hosted runners vs Elastic CI Stack for AWS](https://cirunners.org/compare/aws-codebuild-runners-vs-buildkite-elastic-ci-stack/) - [AWS CodeBuild-hosted runners vs GitLab-hosted runners](https://cirunners.org/compare/aws-codebuild-runners-vs-gitlab-hosted-runners/) - [AWS CodeBuild-hosted runners vs Managed DevOps Pools](https://cirunners.org/compare/aws-codebuild-runners-vs-azure-managed-devops-pools/) - [AWS CodeBuild-hosted runners vs RunsOn](https://cirunners.org/compare/aws-codebuild-runners-vs-runs-on/) - [AWS CodeBuild-hosted runners vs terraform-aws-github-runner](https://cirunners.org/compare/aws-codebuild-runners-vs-terraform-aws-github-runner/) - [Bitrise Build Hub vs GetMac](https://cirunners.org/compare/bitrise-runners-vs-getmac/) - [Bitrise Build Hub vs Orka](https://cirunners.org/compare/bitrise-runners-vs-macstadium-orka/) - [Blacksmith vs Depot GitHub Actions Runners](https://cirunners.org/compare/blacksmith-vs-depot/) - [Blacksmith vs GitHub-hosted runners](https://cirunners.org/compare/blacksmith-vs-github-hosted-runners/) - [Blacksmith vs Luxor Runners](https://cirunners.org/compare/blacksmith-vs-luxor-runners/) - [Blacksmith vs Namespace](https://cirunners.org/compare/blacksmith-vs-namespace/) - [Blacksmith vs Ubicloud Runners](https://cirunners.org/compare/blacksmith-vs-ubicloud/) - [Blacksmith vs WarpBuild](https://cirunners.org/compare/blacksmith-vs-warpbuild/) - [Buildkite hosted agents vs Elastic CI Stack for AWS](https://cirunners.org/compare/buildkite-hosted-agents-vs-buildkite-elastic-ci-stack/) - [Buildkite hosted agents vs GitLab-hosted runners](https://cirunners.org/compare/buildkite-hosted-agents-vs-gitlab-hosted-runners/) - [Buildkite hosted agents vs Microsoft-hosted agents](https://cirunners.org/compare/buildkite-hosted-agents-vs-azure-pipelines-agents/) - [Buildkite hosted agents vs Orka](https://cirunners.org/compare/buildkite-hosted-agents-vs-macstadium-orka/) - [Cirun vs GARM (GitHub Actions Runner Manager)](https://cirunners.org/compare/cirun-vs-garm/) - [Cirun vs HyperEnv for GitHub Actions Runner](https://cirunners.org/compare/cirun-vs-hyperenv/) - [Cirun vs RunsOn](https://cirunners.org/compare/cirun-vs-runs-on/) - [Cirun vs Sprinters](https://cirunners.org/compare/cirun-vs-sprinters/) - [Cirun vs terraform-aws-github-runner](https://cirunners.org/compare/cirun-vs-terraform-aws-github-runner/) - [Cirun vs WarpBuild](https://cirunners.org/compare/cirun-vs-warpbuild/) - [Depot GitHub Actions Runners vs GitHub-hosted runners](https://cirunners.org/compare/depot-vs-github-hosted-runners/) - [Depot GitHub Actions Runners vs Namespace](https://cirunners.org/compare/depot-vs-namespace/) - [Depot GitHub Actions Runners vs Ubicloud Runners](https://cirunners.org/compare/depot-vs-ubicloud/) - [Depot GitHub Actions Runners vs WarpBuild](https://cirunners.org/compare/depot-vs-warpbuild/) - [Elastic CI Stack for AWS vs GitLab Runner](https://cirunners.org/compare/buildkite-elastic-ci-stack-vs-gitlab-runner/) - [Fireactions vs GARM (GitHub Actions Runner Manager)](https://cirunners.org/compare/fireactions-vs-garm/) - [Fireactions vs myshoes](https://cirunners.org/compare/fireactions-vs-myshoes/) - [Fireactions vs TestFlows GitHub Hetzner Runners](https://cirunners.org/compare/fireactions-vs-github-hetzner-runners/) - [GARM (GitHub Actions Runner Manager) vs myshoes](https://cirunners.org/compare/garm-vs-myshoes/) - [GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner](https://cirunners.org/compare/garm-vs-terraform-aws-github-runner/) - [GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners](https://cirunners.org/compare/garm-vs-github-hetzner-runners/) - [GetMac vs Orka](https://cirunners.org/compare/getmac-vs-macstadium-orka/) - [GitHub-hosted runners vs GitLab-hosted runners](https://cirunners.org/compare/github-hosted-runners-vs-gitlab-hosted-runners/) - [GitHub-hosted runners vs Namespace](https://cirunners.org/compare/github-hosted-runners-vs-namespace/) - [GitHub-hosted runners vs Ubicloud Runners](https://cirunners.org/compare/github-hosted-runners-vs-ubicloud/) - [GitHub-hosted runners vs WarpBuild](https://cirunners.org/compare/github-hosted-runners-vs-warpbuild/) - [GitLab Runner vs GitLab-hosted runners](https://cirunners.org/compare/gitlab-runner-vs-gitlab-hosted-runners/) - [GitLab-hosted runners vs Microsoft-hosted agents](https://cirunners.org/compare/gitlab-hosted-runners-vs-azure-pipelines-agents/) - [HyperEnv for GitHub Actions Runner vs RunsOn](https://cirunners.org/compare/hyperenv-vs-runs-on/) - [HyperEnv for GitHub Actions Runner vs Sprinters](https://cirunners.org/compare/hyperenv-vs-sprinters/) - [HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner](https://cirunners.org/compare/hyperenv-vs-terraform-aws-github-runner/) - [Managed DevOps Pools vs Microsoft-hosted agents](https://cirunners.org/compare/azure-managed-devops-pools-vs-azure-pipelines-agents/) - [Namespace vs Ubicloud Runners](https://cirunners.org/compare/namespace-vs-ubicloud/) - [Namespace vs WarpBuild](https://cirunners.org/compare/namespace-vs-warpbuild/) - [Orka vs Tart](https://cirunners.org/compare/macstadium-orka-vs-tart/) - [RunsOn vs Sprinters](https://cirunners.org/compare/runs-on-vs-sprinters/) - [RunsOn vs terraform-aws-github-runner](https://cirunners.org/compare/runs-on-vs-terraform-aws-github-runner/) - [RunsOn vs WarpBuild](https://cirunners.org/compare/runs-on-vs-warpbuild/) - [terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners](https://cirunners.org/compare/terraform-aws-github-runner-vs-github-hetzner-runners/) - [TestFlows GitHub Hetzner Runners vs Ubicloud Runners](https://cirunners.org/compare/github-hetzner-runners-vs-ubicloud/) - [Ubicloud Runners vs WarpBuild](https://cirunners.org/compare/ubicloud-vs-warpbuild/) - [Anka Build Cloud vs Orka](https://cirunners.org/compare/veertu-anka-vs-macstadium-orka/) - [Aspect Workflows vs Elastic CI Stack for AWS](https://cirunners.org/compare/aspect-workflows-vs-buildkite-elastic-ci-stack/) - [Avrea vs Blacksmith](https://cirunners.org/compare/avrea-vs-blacksmith/) - [Blacksmith vs BuildPulse Runners](https://cirunners.org/compare/blacksmith-vs-buildpulse-runners/) - [Cilicon vs Tart](https://cirunners.org/compare/cilicon-vs-tart/) - [Blacksmith vs CRACI](https://cirunners.org/compare/blacksmith-vs-craci/) - [ec2-github-runner vs terraform-aws-github-runner](https://cirunners.org/compare/ec2-github-runner-vs-terraform-aws-github-runner/) - [enomem vs Managed DevOps Pools](https://cirunners.org/compare/enomem-vs-azure-managed-devops-pools/) - [Cirun vs machine.dev](https://cirunners.org/compare/cirun-vs-machine/) - [GitLab-hosted runners vs RunJob](https://cirunners.org/compare/gitlab-hosted-runners-vs-runjob/) - [Tart vs Tartelet](https://cirunners.org/compare/tart-vs-tartelet/) - [GitLab Runner vs terraform-aws-gitlab-runner](https://cirunners.org/compare/gitlab-runner-vs-terraform-aws-gitlab-runner/) ## Alternatives - [Actions Runner Controller (ARC) alternatives](https://cirunners.org/alternatives/actions-runner-controller/): 7 alternatives to Actions Runner Controller (ARC): Actuated, AWS CodeBuild-hosted runners and more, compared on pricing, hardware, caching and deployment. - [Actuated alternatives](https://cirunners.org/alternatives/actuated/): 8 alternatives to Actuated: Actions Runner Controller (ARC), Blacksmith, Cirun and more, compared on pricing, hardware, caching and deployment. - [Anka Build Cloud alternatives](https://cirunners.org/alternatives/veertu-anka/): 6 alternatives to Anka Build Cloud: Bitrise Build Hub, GetMac, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [Aspect Workflows alternatives](https://cirunners.org/alternatives/aspect-workflows/): 8 alternatives to Aspect Workflows: Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [Avrea alternatives](https://cirunners.org/alternatives/avrea/): 7 alternatives to Avrea: Blacksmith, Depot GitHub Actions Runners, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [AWS CodeBuild-hosted runners alternatives](https://cirunners.org/alternatives/aws-codebuild-runners/): 7 alternatives to AWS CodeBuild-hosted runners: Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [Bitrise Build Hub alternatives](https://cirunners.org/alternatives/bitrise-runners/): 7 alternatives to Bitrise Build Hub: Blacksmith, Depot GitHub Actions Runners, GetMac and more, compared on pricing, hardware, caching and deployment. - [Blacksmith alternatives](https://cirunners.org/alternatives/blacksmith/): 6 alternatives to Blacksmith: Depot GitHub Actions Runners, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [Buildkite hosted agents alternatives](https://cirunners.org/alternatives/buildkite-hosted-agents/): 6 alternatives to Buildkite hosted agents: AWS CodeBuild-hosted runners and more, compared on pricing, hardware, caching and deployment. - [BuildPulse Runners alternatives](https://cirunners.org/alternatives/buildpulse-runners/): 6 alternatives to BuildPulse Runners: Blacksmith, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [Cilicon alternatives](https://cirunners.org/alternatives/cilicon/): 6 alternatives to Cilicon: Actions Runner Controller (ARC), GetMac, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [Cirun alternatives](https://cirunners.org/alternatives/cirun/): 8 alternatives to Cirun: Actions Runner Controller (ARC), Actuated and more, compared on pricing, hardware, caching and deployment. - [CRACI alternatives](https://cirunners.org/alternatives/craci/): 8 alternatives to CRACI: Actuated, Blacksmith, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [Depot GitHub Actions Runners alternatives](https://cirunners.org/alternatives/depot/): 6 alternatives to Depot GitHub Actions Runners: Blacksmith, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [ec2-github-runner alternatives](https://cirunners.org/alternatives/ec2-github-runner/): 6 alternatives to ec2-github-runner: Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [Elastic CI Stack for AWS alternatives](https://cirunners.org/alternatives/buildkite-elastic-ci-stack/): 6 alternatives to Elastic CI Stack for AWS: Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [enomem alternatives](https://cirunners.org/alternatives/enomem/): 8 alternatives to enomem: Actions Runner Controller (ARC), Cirun and more, compared on pricing, hardware, caching and deployment. - [Fireactions alternatives](https://cirunners.org/alternatives/fireactions/): 6 alternatives to Fireactions: Actions Runner Controller (ARC), Actuated and more, compared on pricing, hardware, caching and deployment. - [GARM (GitHub Actions Runner Manager) alternatives](https://cirunners.org/alternatives/garm/): 7 alternatives to GARM (GitHub Actions Runner Manager): Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [GetMac alternatives](https://cirunners.org/alternatives/getmac/): 7 alternatives to GetMac: Bitrise Build Hub, Blacksmith, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [GitHub-hosted runners alternatives](https://cirunners.org/alternatives/github-hosted-runners/): 8 alternatives to GitHub-hosted runners: Actions Runner Controller (ARC), Blacksmith and more, compared on pricing, hardware, caching and deployment. - [GitLab Runner alternatives](https://cirunners.org/alternatives/gitlab-runner/): 6 alternatives to GitLab Runner: Actions Runner Controller (ARC), Elastic CI Stack for AWS and more, compared on pricing, hardware, caching and deployment. - [GitLab-hosted runners alternatives](https://cirunners.org/alternatives/gitlab-hosted-runners/): 6 alternatives to GitLab-hosted runners: AWS CodeBuild-hosted runners and more, compared on pricing, hardware, caching and deployment. - [HyperEnv for GitHub Actions Runner alternatives](https://cirunners.org/alternatives/hyperenv/): 7 alternatives to HyperEnv for GitHub Actions Runner: Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [Luxor Runners alternatives](https://cirunners.org/alternatives/luxor-runners/): 6 alternatives to Luxor Runners: Blacksmith, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [machine.dev alternatives](https://cirunners.org/alternatives/machine/): 7 alternatives to machine.dev: Blacksmith, Cirun, GitHub-hosted runners, Namespace, RunsOn and more, compared on pricing, hardware, caching and deployment. - [Managed DevOps Pools alternatives](https://cirunners.org/alternatives/azure-managed-devops-pools/): 5 alternatives to Managed DevOps Pools: AWS CodeBuild-hosted runners and more, compared on pricing, hardware, caching and deployment. - [Microsoft-hosted agents alternatives](https://cirunners.org/alternatives/azure-pipelines-agents/): 5 alternatives to Microsoft-hosted agents: AWS CodeBuild-hosted runners and more, compared on pricing, hardware, caching and deployment. - [myshoes alternatives](https://cirunners.org/alternatives/myshoes/): 6 alternatives to myshoes: Actions Runner Controller (ARC), Cirun, Fireactions and more, compared on pricing, hardware, caching and deployment. - [Namespace alternatives](https://cirunners.org/alternatives/namespace/): 6 alternatives to Namespace: Blacksmith, Buildkite hosted agents and more, compared on pricing, hardware, caching and deployment. - [Orka alternatives](https://cirunners.org/alternatives/macstadium-orka/): 7 alternatives to Orka: Bitrise Build Hub, Buildkite hosted agents, GetMac and more, compared on pricing, hardware, caching and deployment. - [RunJob alternatives](https://cirunners.org/alternatives/runjob/): 7 alternatives to RunJob: Blacksmith, Cirun, GitHub-hosted runners, GitLab Runner and more, compared on pricing, hardware, caching and deployment. - [RunsOn alternatives](https://cirunners.org/alternatives/runs-on/): 8 alternatives to RunsOn: Actions Runner Controller (ARC), Actuated and more, compared on pricing, hardware, caching and deployment. - [Sprinters alternatives](https://cirunners.org/alternatives/sprinters/): 8 alternatives to Sprinters: AWS CodeBuild-hosted runners, Cirun, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [Tart alternatives](https://cirunners.org/alternatives/tart/): 6 alternatives to Tart: Actions Runner Controller (ARC), Elastic CI Stack for AWS, GetMac and more, compared on pricing, hardware, caching and deployment. - [Tartelet alternatives](https://cirunners.org/alternatives/tartelet/): 5 alternatives to Tartelet: Actions Runner Controller (ARC), GetMac, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. - [terraform-aws-github-runner alternatives](https://cirunners.org/alternatives/terraform-aws-github-runner/): 7 alternatives to terraform-aws-github-runner: Actions Runner Controller (ARC) and more, compared on pricing, hardware, caching and deployment. - [terraform-aws-gitlab-runner alternatives](https://cirunners.org/alternatives/terraform-aws-gitlab-runner/): 5 alternatives to terraform-aws-gitlab-runner: AWS CodeBuild-hosted runners and more, compared on pricing, hardware, caching and deployment. - [TestFlows GitHub Hetzner Runners alternatives](https://cirunners.org/alternatives/github-hetzner-runners/): 7 alternatives to TestFlows GitHub Hetzner Runners: Actions Runner Controller (ARC), Cirun and more, compared on pricing, hardware, caching and deployment. - [Ubicloud Runners alternatives](https://cirunners.org/alternatives/ubicloud/): 7 alternatives to Ubicloud Runners: Blacksmith, Cirun, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [WarpBuild alternatives](https://cirunners.org/alternatives/warpbuild/): 7 alternatives to WarpBuild: Blacksmith, Cirun, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [BuildJet for GitHub Actions alternatives](https://cirunners.org/alternatives/buildjet/): 6 alternatives to BuildJet for GitHub Actions: Blacksmith, Depot GitHub Actions Runners and more, compared on pricing, hardware, caching and deployment. - [Cirrus Runners alternatives](https://cirunners.org/alternatives/cirrus-runners/): 8 alternatives to Cirrus Runners: Blacksmith, Depot GitHub Actions Runners, GetMac and more, compared on pricing, hardware, caching and deployment. - [FlyCI macOS Runners alternatives](https://cirunners.org/alternatives/flyci/): 5 alternatives to FlyCI macOS Runners: Bitrise Build Hub, GetMac, GitHub-hosted runners and more, compared on pricing, hardware, caching and deployment. ## Guides - [What is a CI runner?](https://cirunners.org/guides/what-is-a-ci-runner/): A plain-English explanation of CI runners: what they do, how they connect to GitHub Actions or GitLab CI, and the kinds you can choose from. - [How third-party GitHub Actions runners work](https://cirunners.org/guides/how-third-party-github-actions-runners-work/): How drop-in GitHub Actions runners work: the GitHub App, the runs-on label, just-in-time ephemeral runners, caching, and what the vendor can see. - [How to choose a CI runner: a buyer’s checklist](https://cirunners.org/guides/how-to-choose-a-ci-runner/): A step-by-step checklist for choosing a CI runner: CI system, platforms, deployment, isolation, caching, price, limits and how to run a fair trial. - [CI runner pricing explained](https://cirunners.org/guides/ci-runner-pricing/): How CI runners are priced: per-minute rates by size and OS, free allowances, rounding, cache and storage charges, and the real cost of your own cloud. - [CI runner security: a practical guide](https://cirunners.org/guides/ci-runner-security/): How to secure CI runners: ephemeral runners, isolation boundaries, public-repository risk, secrets and OIDC, cache poisoning and network egress control. - [Docker layer caching in CI, explained](https://cirunners.org/guides/docker-layer-caching-in-ci/): Why Docker builds are slow on ephemeral CI runners and how to fix it: registry and GitHub cache backends, persistent layer caches and native multi-arch. - [Self-hosting GitHub Actions runners: the options](https://cirunners.org/guides/self-hosting-github-actions-runners/): How to run your own GitHub Actions runners: Actions Runner Controller on Kubernetes, cloud VM autoscalers, Firecracker managers and BYOC products. - [macOS CI runners explained](https://cirunners.org/guides/macos-ci-runners-explained/): How macOS CI runners work and why they cost more: Apple hardware and licence rules, hosted versus dedicated Macs, virtualization and image upkeep. ## Optional - [Full text for LLMs](https://cirunners.org/llms-full.txt): every provider record and guide in one plain-text file - [Open data (JSON)](https://cirunners.org/data/providers.json): structured provider records, CC BY 4.0 - [CI runner](https://cirunners.org/glossary/ci-runner/): The machine that executes the jobs of a continuous-integration pipeline: it checks out code, runs build and test steps and reports the result. - [GitHub-hosted runner](https://cirunners.org/glossary/github-hosted-runner/): A virtual machine that GitHub provisions for one GitHub Actions job, with a maintained image of preinstalled tools, and destroys afterwards. - [Larger runner](https://cirunners.org/glossary/larger-runner/): A GitHub-hosted runner with more cores, memory or disk than the standard size, or with a GPU, billed per minute at a higher rate. - [Self-hosted runner](https://cirunners.org/glossary/self-hosted-runner/): A runner on a machine you (or a vendor acting for you) operate, registered with the CI system to pick up jobs in place of the platform’s hosted runners. - [Ephemeral runner](https://cirunners.org/glossary/ephemeral-runner/): A runner that takes exactly one job and is then destroyed, so every job starts from a clean machine and nothing carries over. - [Just-in-time runner](https://cirunners.org/glossary/just-in-time-runner/): A self-hosted GitHub Actions runner created from a one-off configuration issued by the API, valid for a single job. - [runs-on label](https://cirunners.org/glossary/runs-on/): The line in a GitHub Actions job that names the kind of runner the job needs; changing it is how a workflow moves to another runner provider. - [Actions Runner Controller (ARC)](https://cirunners.org/glossary/actions-runner-controller/): GitHub’s open-source Kubernetes operator that creates and scales self-hosted GitHub Actions runners as pods. - [Runner scale set](https://cirunners.org/glossary/runner-scale-set/): A named group of identical, autoscaled self-hosted GitHub Actions runners that a workflow targets by the scale set’s name. - [BYOC (bring your own cloud)](https://cirunners.org/glossary/byoc/): A deployment model where the runners are virtual machines in the customer’s own cloud account while a vendor’s software orchestrates them. - [Docker layer caching](https://cirunners.org/glossary/docker-layer-caching/): Reusing the unchanged layers of a container image from an earlier build so a CI job rebuilds only what changed. - [Dependency cache](https://cirunners.org/glossary/dependency-cache/): A store that saves downloaded packages and build outputs between CI jobs, keyed by a hash, so later jobs can restore them instead of redoing the work. - [MicroVM](https://cirunners.org/glossary/microvm/): A minimal virtual machine with a stripped-down device model that boots in a fraction of a second and gives each workload its own guest kernel. - [Firecracker](https://cirunners.org/glossary/firecracker/): An open-source virtual machine monitor from AWS that runs microVMs on KVM, built for short-lived, multi-tenant workloads. - [Bare metal](https://cirunners.org/glossary/bare-metal/): Physical servers used directly rather than rented as cloud virtual machines; runner vendors use them to pick faster CPUs and run their own virtualization. - [arm64 runner](https://cirunners.org/glossary/arm64/): A runner with a 64-bit Arm processor, used to build and test software for Arm servers and devices natively instead of under emulation. - [Spot instance](https://cirunners.org/glossary/spot-instance/): Spare cloud capacity sold at a large discount on the condition that the provider can reclaim the machine at short notice. - [Warm pool](https://cirunners.org/glossary/warm-pool/): A set of runners started ahead of demand and kept idle so that a queued job begins immediately instead of waiting for a machine to boot. - [Queue time](https://cirunners.org/glossary/queue-time/): The delay between a CI job being requested and a runner starting to execute it. - [Concurrency limit](https://cirunners.org/glossary/concurrency-limit/): The maximum number of CI jobs, or total vCPUs, that can run at the same time on a plan or account. - [Static egress IP](https://cirunners.org/glossary/static-egress-ip/): A fixed, published set of IP addresses that a runner’s outbound traffic comes from, so it can be added to firewall allow-lists. - [OIDC in CI](https://cirunners.org/glossary/oidc/): OpenID Connect lets a CI job prove its identity to a cloud provider and receive short-lived credentials, instead of storing long-lived secrets. - [Compute minutes](https://cirunners.org/glossary/compute-minutes/): GitLab’s billing unit for jobs on GitLab-hosted runners: job duration multiplied by a cost factor that depends on the runner type and size. - [GitLab Runner executor](https://cirunners.org/glossary/gitlab-runner-executor/): The mechanism a GitLab Runner uses to run a job: a shell, a Docker container, a Kubernetes pod, or an autoscaled virtual machine. - [macOS virtualization](https://cirunners.org/glossary/macos-virtualization/): Running macOS as a virtual machine on Apple hardware, which lets a Mac give every CI job a clean, disposable macOS environment.