Start with your use case
Each goal stresses different things. Pick the closest one to see what matters and which runners document support for it.
- Faster buildsCPU speed, colocated caches, more cores, higher concurrency11 runners fit →
- Lower CI costPer-minute rates, fewer minutes, spot instances, free tiers17 runners fit →
- Docker buildsLayer caching, persistent build state, native multi-arch12 runners fit →
- ARM64 buildsNative arm64 hardware, sizes, multi-arch images24 runners fit →
- macOS and iOS buildsApple silicon, Xcode versions, per-minute vs dedicated Macs18 runners fit →
- Windows buildsWindows Server images, MSVC toolchains, price per minute13 runners fit →
- GPU jobsGPU model and memory, price per minute, drivers, availability10 runners fit →
- Your own cloudData stays in your account, private networking, spot pricing26 runners fit →
- Open source and self-hostedNo licence fee, full control, you operate it14 runners fit →
- GitLab CI runnersCompute minutes, GitLab Runner executors, autoscaling12 runners fit →
- Security and complianceEphemeral VMs, isolation boundary, egress control, SOC 215 runners fit →
The 5 kinds of CI runner
Runners differ less in what they do (every one runs your jobs) than in who operates the machines and where those machines sit. Knowing which kind you need cuts the list quickly.
Managed runners for GitHub Actions
Vendors that host runners on their own hardware and register them with your GitHub organisation through a GitHub App. You keep your workflows and change one line, runs-on. They compete with GitHub-hosted runners on price per minute, CPU speed and caching: most add a faster cache backend, Docker layer caching and build analytics.
Choose this kind when
- Your workflows already run on GitHub Actions and you want faster or cheaper minutes without running infrastructure.
- Docker builds or dependency installs dominate your pipeline and a cache close to the runner would help.
- You want larger machines, arm64 or more concurrency than your GitHub plan gives you.
Trade-offs
- Your source code and secrets run on a third party’s machines, so check its isolation model and compliance reports.
- A second vendor sits in your delivery path: an outage there stops your builds even when GitHub is up.
- macOS, Windows and GPU coverage varies a lot between vendors.
- GitHub Actions · $0.004/minAvreaManaged GitHub Actions runners for Linux, macOS and Windows on dedicated hardware, with colocated caches and SSH into running jobs.
- GitHub Actions · $0.004/minBlacksmithManaged GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners.
- GitHub Actions, CircleCI · $0.004/minBuildPulse RunnersManaged Linux runners for GitHub Actions, CircleCI and Semaphore with included cache storage and flaky-test detection on every run.
- GitHub Actions · €0.004/minCRACIManaged Linux runners for GitHub Actions on European bare metal that record a build-time SBOM and apply an egress policy to each job.
- GitHub Actions · $0.006/minDepot GitHub Actions RunnersManaged GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service.
- GitHub Actions · $0.004/minLuxor RunnersGitHub Actions runners on bare-metal Linux x64 and Apple Silicon macOS, one single-use VM per job; called Tenki until November 2026.
- GitHub Actions · $0.00297/min on-demandmachine.devGPU, x64 and arm64 runners for GitHub Actions on dedicated AWS instances, with spot or on-demand tenancy chosen in the runs-on label.
- GitHub Actions, Buildkite · $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)NamespaceManaged runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes.
- GitHub Actions, GitLab CI · €0.00002 per vCPU-second usedRunJobEU-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.
- GitHub Actions · $0.00125/minUbicloud RunnersManaged Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal.
- GitHub Actions · $0.004/minWarpBuildManaged GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.
Runners from your CI platform or cloud
The default choice: runners operated by the CI platform itself, or a managed runner service from the cloud provider you already use. Nothing extra to install or procure, billing goes through an account you already have, and images are maintained for you. They are the baseline every other option on this site is compared against.
Choose this kind when
- You want the fewest vendors and no extra procurement or security review.
- Your usage fits inside the free allowance of your plan, or your repositories are public.
- You need the widest OS coverage (Linux, Windows and macOS) from one supplier.
Trade-offs
- List prices per minute are usually higher than third-party runners for the same core count.
- Hardware choices, cache sizes and concurrency are set by the platform’s plan limits.
- Cloud-provider services tie your runners to that cloud’s IAM, networking and billing.
- GitHub Actions, GitLab CI · $0.005/minAWS CodeBuild-hosted runnersAWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job.
- Buildkite · $0.008/minBuildkite hosted agentsBuildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute.
- GitHub Actions · $0.006/minGitHub-hosted runnersGitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute.
- GitLab CI · $10 per 1,000 compute minutesGitLab-hosted runnersGitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size.
- Azure Pipelines · $15/month per parallel job + Azure VM costManaged DevOps PoolsAzure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates.
- Azure Pipelines · $40/month per parallel jobMicrosoft-hosted agentsAzure Pipelines’ built-in agents: a fresh 2-core VM per job on Windows, Linux or macOS, sold per parallel job rather than per minute.
Runners in your own cloud or on your hardware
Products that keep the convenience of managed runners but run the machines in infrastructure you control. A control plane (hosted by the vendor or deployed into your account) listens for queued jobs and starts an ephemeral VM in your cloud account or on your servers for each one. You pay the cloud bill directly, often with spot instances, plus a licence or a small per-minute fee.
Choose this kind when
- Code, secrets and build artefacts must stay inside your own cloud account or network.
- Jobs need private access to databases, registries or internal services in your VPC.
- You have cloud credits or committed spend, or want spot pricing on large machines.
Trade-offs
- You own the cloud account: quotas, networking, images and cost controls are your job.
- Start-up time depends on how quickly your cloud can boot an instance, unless you pay for warm pools.
- Most are built for one cloud, usually AWS.
- GitHub Actions, GitLab CI · $150/mo per server + your serversActuatedManaged control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI.
- GitHub Actions, Buildkite · Annual platform fee (quote) + cloud costAspect WorkflowsBazel-focused platform whose auto-scaling CI runners register with your existing CI and can run in your own AWS account or GCP project.
- GitHub Actions · $29/mo (3 private repos) + cloud costCirunHosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file.
- GitHub Actions · $25/mo licence + Azure costenomemSelf-hosted GitHub Actions runners on Azure: an Azure Functions handler in your subscription starts one Spot VM per job.
- GitHub Actions · $0.002/min fee + AWS costHyperEnv for GitHub Actions RunnerAWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account.
- GitHub Actions · €300/yr licence + AWS costRunsOnSelf-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job.
- GitHub Actions · $0.01/job + AWS costSprintersGitHub App that launches one ephemeral EC2 instance per GitHub Actions job in your own AWS account, charged per job rather than per minute.
Open-source autoscalers for self-hosted runners
Open-source controllers that register runners with your CI system and scale them with the job queue: on Kubernetes, on cloud instances or on Firecracker microVMs on your own servers. There is no licence fee and no vendor in the path, but you operate everything: the controller, the runner images, the caches and the upgrades.
Choose this kind when
- You have a platform team and want full control with no per-minute or licence fee.
- You already run Kubernetes or a cloud landing zone and want runners to live there.
- You need to customise images, networking or hardware beyond what a vendor offers.
Trade-offs
- Engineering time replaces the vendor bill: upgrades, image builds and on-call are yours.
- Security depends on your configuration, especially whether every job gets a fresh machine.
- Caching, Docker builds and observability have to be assembled from separate parts.
- GitHub ActionsActions Runner Controller (ARC)Kubernetes operator that scales self-hosted GitHub Actions runners as ephemeral pods through runner scale sets.
- GitHub Actionsec2-github-runnerGitHub Action that starts an EC2 instance as a self-hosted runner at the start of a workflow and terminates it at the end.
- BuildkiteElastic CI Stack for AWSCloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account.
- GitHub ActionsFireactionsOrchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts.
- GitHub Actions, Forgejo/Gitea ActionsGARM (GitHub Actions Runner Manager)Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins.
- GitLab CIGitLab RunnerThe open-source agent that runs GitLab CI/CD jobs, with executors for Docker, Kubernetes, shell and autoscaled cloud instances.
- GitHub ActionsmyshoesDaemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS.
- GitHub Actionsterraform-aws-github-runnerTerraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions.
- GitLab CIterraform-aws-gitlab-runnerTerraform module that deploys GitLab Runner on AWS and autoscales its job workers on EC2 spot instances.
- GitHub ActionsTestFlows GitHub Hetzner RunnersSelf-contained Python service that creates a Hetzner Cloud server for each queued GitHub Actions job, with no webhooks or GitHub App.
macOS runners for iOS and Mac builds
Building for Apple platforms needs macOS, which legally runs only on Apple hardware, so macOS runners are a market of their own. The options are hosted Mac runners billed per minute, dedicated Mac hosts rented by the month, and virtualization tools that turn Macs you own or rent into clean, single-use build machines.
Choose this kind when
- You build, test or sign iOS, macOS, watchOS or visionOS apps in CI.
- macOS minutes are the largest line on your CI bill.
- You need a specific Xcode or macOS version, or newer Apple silicon than your CI platform offers.
Trade-offs
- macOS minutes cost several times more than Linux minutes everywhere.
- Apple’s licence limits macOS virtualization to two virtual machines per Mac, which caps density.
- Capacity is physical hardware: large bursts of concurrency can take time to arrange.
- GitHub Actions, GitLab CIAnka Build CloudCommercial macOS virtualization for CI: a controller and registry manage on-demand Anka VMs on your own Macs, hosted Macs or AWS EC2 Mac.
- GitHub Actions · $0.00625/minBitrise Build HubBitrise-managed macOS and Linux runners for GitHub Actions on Bitrise-owned Apple silicon and AMD EPYC machines, sold as monthly compute budgets.
- GitHub Actions, GitLab CICiliconOpen-source macOS app that runs ephemeral CI virtual machines on a single Apple silicon Mac using Apple’s Virtualization framework.
- GitHub Actions, GitLab CI · $0.012/min (macOS M4, Developer plan)GetMacManaged macOS runners on vendor-owned Apple silicon M4 hardware in Lithuania, sold as monthly plans of included compute minutes.
- GitHub Actions, GitLab CI · From $109/mo per hosted Mac mini (Orka by quote)OrkaKubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs.
- GitLab CI, BuildkiteTartVirtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs.
- GitHub ActionsTarteletOpen-source macOS app that runs up to two GitHub Actions runners in ephemeral Tart virtual machines on a single Mac.
How the finder decides
Behind the finder is a matrix: each answer scores every runner from its own documentation, and a runner that cannot meet an answer is ruled out. The four questions below do most of the narrowing. Each lists the runners whose documentation supports that answer.
Which CI system runs your pipelines?
A runner has to speak your CI system’s protocol, so this removes most of the field at once. Most third-party runners are built for GitHub Actions.
Where must the runners run?
Data residency, private network access and procurement often decide this before price does. See runners in your own cloud.
What do your jobs run on?
Linux x64 is offered by nearly everything. Other platforms narrow the list quickly.
How isolated must each job be?
A runner executes your code with your secrets. Pull requests from forks and shared infrastructure raise the bar. See the runner security guide.
Compare every runner
All 41 runners, alphabetically. Filter by name, CI system or operating system, or tick a box to narrow the list.
| 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 |
| Avrea | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Per-job VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Finland |
| 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 |
| Bitrise Build Hub | GitHub Actions | macOS, Linux, arm64, x64 | Vendor-hosted | Virtual machine | $0.00625/min | 16 vCPU / 64 GB | Not documented | Not documented | No | Not documented |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
| Buildkite hosted agents | Buildkite | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral virtualized environment | $0.008/min | 64 vCPU / 256 GB | Yes | Not documented | No | Not documented |
| BuildPulse Runners | GitHub Actions, CircleCI, Semaphore | Linux, x64, arm64 | Vendor-hosted | Fresh per-job runner | $0.004/min | 64 vCPU / 256 GB | Yes | Not documented | No | Not documented |
| 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 |
| CRACI | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | Per-job VM | €0.004/min | 32 vCPU / 96 GB | Not documented | Not documented | No | Finland |
| 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 |
| GetMac | GitHub Actions, GitLab CI, Buildkite | macOS, arm64 | Vendor-hosted | macOS VM | $0.012/min (macOS M4, Developer plan) | Not documented | Not documented | Not documented | No | Lithuania |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| 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 |
| GitLab-hosted runners | GitLab CI | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral VM | $10 per 1,000 compute minutes | 32 vCPU / 128 GB | Not documented | Yes | No | 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 |
| Luxor Runners | GitHub Actions | Linux, macOS, x64, arm64 | Vendor-hosted | Single-use VM | $0.004/min | 16 vCPU / 32 GB | Not documented | Not documented | No | United States |
| machine.dev | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | Dedicated AWS instance | $0.00297/min on-demand | 64 vCPU / 128 GB | Not documented | Yes | No | Australia |
| 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 |
| Microsoft-hosted agents | Azure Pipelines | Linux, macOS, Windows, x64 | Platform-hosted | Fresh VM | $40/month per parallel job | 2 vCPU / 7 GB | 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 |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | 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 |
| RunJob | GitHub Actions, GitLab CI | Linux, x64 | Vendor-hosted | KVM virtual machine | €0.00002 per vCPU-second used | 48 vCPU / 96 GB | No | Yes | No | Estonia |
| 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 |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| 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 |
What is a CI runner?
A CI runner is the machine that executes the jobs in a continuous-integration pipeline: it checks out your code, runs the build and test steps and reports the result to the CI system. GitHub Actions and GitLab CI call it a runner; Buildkite and Azure Pipelines call it an agent. Every CI platform offers hosted runners of its own, and lets you attach others: from a third-party vendor, in your own cloud account or on your own hardware. Read the full explainer: What is a CI runner?
How this guide works
Every fact on this site comes from providers’ own documentation and is dated. Speed and savings figures are vendor claims, not our measurements. We do not rank providers against each other: runners are grouped by kind and use case and listed alphabetically, and each entry explains what it fits. No provider pays for inclusion or placement. Read the methodology.
Frequently asked questions
What is the best CI runner?
What is a CI runner?
How do third-party GitHub Actions runners work?
runs-on label in a workflow. When a job is queued, the vendor starts a machine, registers it with GitHub as a self-hosted runner for that one job and destroys it afterwards. Your workflows, actions and secrets stay in GitHub. See how drop-in runners work.Which CI runners are open source?
Which runners can run in my own cloud account?
Which CI runners support macOS?
How much do CI runners cost?
Is FlyCI macOS Runners still available?
Is BuildJet for GitHub Actions still available?
Is Cirrus Runners still available?
How many CI runners does this site track?
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). Find the right runner for your CI pipeline. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/