CI Runnerscirunners.org
Independent guide · 41 runners · 5 kinds

Find the right runner for your CI pipeline

Answer a few questions and the finder narrows 41 CI runners for GitHub Actions, GitLab CI and more to the ones whose documentation fits your pipeline, with the reason for every match. No rankings, no sponsors.

By the CI Runners editors · Updated · How it decides

1Which CI system runs your pipelines?A runner only helps if it speaks your CI system’s protocol.
2What do your jobs run on?Pick the platform that carries most of your minutes.
3Where must the runners run?Data residency, network access and procurement usually decide this first.
4How isolated must each job be?Pull requests from forks and shared runners raise the bar.
5Must haveTick to rule out runners that do not document it.
Leave a question blank if it does not matter to you.

Loading the 41 runners…

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.

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.

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.

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.

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.

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.

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.

What do your jobs run on?

Linux x64 is offered by nearly everything. Other platforms narrow the list quickly.

If your answer is…Look at
Linux arm64Native builds for Graviton, Ampere and multi-architecture images. See ARM64 builds.Actuated, Aspect Workflows, Avrea, AWS CodeBuild-hosted runners, Bitrise Build Hub, Blacksmith, Buildkite hosted agents, BuildPulse Runners, Cirun, CRACI, Depot GitHub Actions Runners, Elastic CI Stack for AWS, enomem, Fireactions, GARM (GitHub Actions Runner Manager), GitHub-hosted runners, GitLab Runner, GitLab-hosted runners, Luxor Runners, machine.dev, Namespace, RunsOn, Sprinters, Tart, terraform-aws-github-runner, TestFlows GitHub Hetzner Runners, Ubicloud Runners, WarpBuild
macOSiOS and Mac apps need Apple hardware. See macOS and iOS builds.Anka Build Cloud, Avrea, Bitrise Build Hub, Blacksmith, Buildkite hosted agents, Cilicon, Cirun, Depot GitHub Actions Runners, GetMac, GitHub-hosted runners, GitLab Runner, GitLab-hosted runners, Luxor Runners, Microsoft-hosted agents, Namespace, Orka, Tart, Tartelet, terraform-aws-github-runner, WarpBuild
Windows.NET Framework, MSVC and desktop apps. See Windows builds.Actions Runner Controller (ARC), Avrea, AWS CodeBuild-hosted runners, Blacksmith, Buildkite hosted agents, Cirun, Depot GitHub Actions Runners, Elastic CI Stack for AWS, GARM (GitHub Actions Runner Manager), GitHub-hosted runners, GitLab Runner, GitLab-hosted runners, Managed DevOps Pools, Microsoft-hosted agents, Namespace, RunsOn, terraform-aws-github-runner, WarpBuild
A GPUModel tests and CUDA builds. See GPU jobs.Actuated, Anka Build Cloud, Aspect Workflows, AWS CodeBuild-hosted runners, Cirun, Depot GitHub Actions Runners, GitHub-hosted runners, GitLab Runner, GitLab-hosted runners, HyperEnv for GitHub Actions Runner, machine.dev, RunJob, RunsOn, terraform-aws-github-runner

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.

If your answer is…Look at
A fresh VM or microVM for every jobA hardware-virtualised boundary that is destroyed after the job. The model to prefer for public repositories and untrusted code.Actuated, Anka Build Cloud, Avrea, Bitrise Build Hub, Blacksmith, Buildkite hosted agents, Cilicon, Cirun, Depot GitHub Actions Runners, enomem, Fireactions, GetMac, GitHub-hosted runners, GitLab-hosted runners, HyperEnv for GitHub Actions Runner, Luxor Runners, machine.dev, Microsoft-hosted agents, Namespace, RunJob, RunsOn, Sprinters, Tart, Tartelet, TestFlows GitHub Hetzner Runners, Ubicloud Runners, WarpBuild
A clean environment per job, any boundarySingle-use runners in containers, pods or dedicated machines.Actions Runner Controller (ARC), AWS CodeBuild-hosted runners, BuildPulse Runners, GARM (GitHub Actions Runner Manager)
Depends on how you configure itSelf-hosted software and some services leave single-use runners to your configuration, or do not document the boundary.Aspect Workflows, CRACI, ec2-github-runner, Elastic CI Stack for AWS, GitLab Runner, Managed DevOps Pools, myshoes, Orka, terraform-aws-github-runner, terraform-aws-gitlab-runner

Compare every runner

All 41 runners, alphabetically. Filter by name, CI system or operating system, or tick a box to narrow the list.

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
AvreaGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedPer-job VM$0.004/min32 vCPU / 128 GBYesNot documentedNoFinland
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
Bitrise Build HubGitHub ActionsmacOS, Linux, arm64, x64Vendor-hostedVirtual machine$0.00625/min16 vCPU / 64 GBNot documentedNot documentedNoNot documented
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Buildkite hosted agentsBuildkiteLinux, macOS, Windows, x64, arm64Platform-hostedEphemeral virtualized environment$0.008/min64 vCPU / 256 GBYesNot documentedNoNot documented
BuildPulse RunnersGitHub Actions, CircleCI, SemaphoreLinux, x64, arm64Vendor-hostedFresh per-job runner$0.004/min64 vCPU / 256 GBYesNot documentedNoNot documented
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
CRACIGitHub ActionsLinux, x64, arm64Vendor-hostedPer-job VM€0.004/min32 vCPU / 96 GBNot documentedNot documentedNoFinland
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
GetMacGitHub Actions, GitLab CI, BuildkitemacOS, arm64Vendor-hostedmacOS VM$0.012/min (macOS M4, Developer plan)Not documentedNot documentedNot documentedNoLithuania
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
GitLab RunnerGitLab CILinux, macOS, Windows, x64, arm64Self-hostedDepends on executorFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
GitLab-hosted runnersGitLab CILinux, macOS, Windows, x64, arm64Platform-hostedEphemeral VM$10 per 1,000 compute minutes32 vCPU / 128 GBNot documentedYesNoNot documented
HyperEnv for GitHub Actions RunnerGitHub ActionsLinux, x64Your cloud or hardwareEC2 instance$0.002/min fee + AWS cost192 vCPU / 768 GBNot documentedYesNoGermany
Luxor RunnersGitHub ActionsLinux, macOS, x64, arm64Vendor-hostedSingle-use VM$0.004/min16 vCPU / 32 GBNot documentedNot documentedNoUnited States
machine.devGitHub ActionsLinux, x64, arm64Vendor-hostedDedicated AWS instance$0.00297/min on-demand64 vCPU / 128 GBNot documentedYesNoAustralia
Managed DevOps PoolsAzure PipelinesLinux, Windows, x64Platform-hostedAzure VM$15/month per parallel job + Azure VM costNot documentedNot documentedNot documentedNoUnited States
Microsoft-hosted agentsAzure PipelinesLinux, macOS, Windows, x64Platform-hostedFresh VM$40/month per parallel job2 vCPU / 7 GBNot documentedNot documentedNoUnited States
myshoesGitHub ActionsLinuxSelf-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
NamespaceGitHub Actions, BuildkiteLinux, macOS, Windows, x64, arm64Vendor-hostedVirtual machine$0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)64 vCPU / 512 GBYesNot documentedNoNot 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
RunJobGitHub Actions, GitLab CILinux, x64Vendor-hostedKVM virtual machine€0.00002 per vCPU-second used48 vCPU / 96 GBNoYesNoEstonia
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
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented

Open the full comparison and head-to-head pages →

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?
There is no single best one; it depends on your pipeline. Four questions narrow the field quickly: which CI system you use, which operating systems and architectures you build for, where the runners have to run (a vendor’s cloud, your cloud account or your own hardware), and whether every job needs a fresh VM. Start from the finder, your use case or the kinds of runner.
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. GitHub Actions and GitLab call it a runner; Buildkite and Azure Pipelines call it an agent. See What is a CI runner?
How do third-party GitHub Actions runners work?
You install the vendor’s GitHub App on your organisation and change the 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?
13 of the 41 runners tracked here are open source, including Actions Runner Controller (ARC), Cilicon, ec2-github-runner, Elastic CI Stack for AWS, Fireactions, GARM (GitHub Actions Runner Manager), GitLab Runner, myshoes and 5 more. 20 can be self-hosted. See open-source and self-hosted runners.
Which runners can run in my own cloud account?
25 of the 41 runners tracked here document running in the customer’s own cloud account or on the customer’s hardware, including Actions Runner Controller (ARC), Actuated, Anka Build Cloud, Aspect Workflows, AWS CodeBuild-hosted runners, Cilicon, Cirun, Depot GitHub Actions Runners and 17 more. See runners in your own cloud.
Which CI runners support macOS?
20 of the 41 runners tracked here document macOS runners: Anka Build Cloud, Avrea, Bitrise Build Hub, Blacksmith, Buildkite hosted agents, Cilicon, Cirun, Depot GitHub Actions Runners, GetMac, GitHub-hosted runners and 10 more. See macOS and iOS builds.
How much do CI runners cost?
Hosted runners bill per minute, with the rate scaling with cores and costing more for Windows and macOS than for Linux. Third-party managed runners publish lower Linux rates than the CI platforms, and runners in your own cloud account cost the instance price plus a licence or fee. See CI runner pricing for published rates side by side.
Is FlyCI macOS Runners still available?
FlyCI announced on August 14, 2024 that it would discontinue FlyCI macOS runners effective September 30, 2024, after which they would no longer be available or supported, and that it would focus on FlyCI Wingman. See the FlyCI macOS Runners profile.
Is BuildJet for GitHub Actions still available?
BuildJet announced on 6 February 2026 that BuildJet for GitHub Actions was shutting down: new signups stopped that day and the service stopped running jobs after 31 March 2026. Its website now states that the service has been shut down. See the BuildJet for GitHub Actions profile.
Is Cirrus Runners still available?
On April 7, 2026 Cirrus Labs announced it had entered into an agreement to join OpenAI as part of the Agent Infrastructure team. The announcement says Cirrus Labs is no longer accepting new customers for Cirrus Runners but will continue supporting the service for existing customers through their existing contract periods. See the Cirrus Runners profile.
How many CI runners does this site track?
41 active runner products and projects with full profiles in the directory, each with sourced facts and a verification date, plus others listed as “also tracked”.

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/