CI runner FAQ
Answer in brief
Short answers to the questions engineering teams ask most when choosing where their CI jobs run. Each links to deeper coverage.
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”.
How do I make GitHub Actions faster?
Find where the time goes first: queueing, cache restore, dependency install, compile, tests or Docker builds. Then fix the largest part. Faster CPUs help compiles and tests, a cache close to the runner helps installs, Docker layer caching helps image builds, and more concurrency helps queues. Third-party runners change all four with a one-line
runs-on change; see how drop-in runners work.Are third-party GitHub Actions runners really faster?
Vendors publish speed-ups, and those are vendor claims. The mechanism is real: many use newer or higher-clocked CPUs than the standard GitHub-hosted runner and keep caches on the same network. How much you gain depends on your workload, so test with your own slowest workflow.
What is the cheapest way to run GitHub Actions?
For public repositories, GitHub’s standard hosted runners are free. For private repositories the lowest unit cost usually comes from running runners in your own cloud account on spot instances, using an open-source autoscaler or a bring-your-own-cloud product, but you take on the operations. Third-party managed runners sit in between: lower published rates than GitHub with nothing to operate. See CI runner pricing.
Does a cheaper per-minute rate always mean a lower bill?
No. The bill is minutes times rate, so a slower runner at a lower rate can cost more. Rounding to whole minutes, storage for caches and artefacts, and egress charges also change the total. Compare the cost of your real workflows over a week.
Why are Docker builds slow in GitHub Actions?
Each job runs on a fresh machine with an empty Docker layer cache, so every layer is rebuilt or pulled. Registry-based and Actions-cache-based layer caching help but transfer the cache over the network each time. Runners with a persistent layer cache keep the layers on a disk attached to the builder. See Docker layer caching in CI.
Should I build ARM64 images with QEMU or native runners?
Native runners. QEMU emulation lets an x64 runner build arm64 images, but compilation under emulation is many times slower. With arm64 runners you build each architecture natively and combine the results into one multi-platform image.
Why are macOS runners so expensive?
macOS may only run on Apple hardware, so providers buy and rack Macs instead of renting commodity cloud servers, and Apple’s licence limits each Mac to two macOS virtual machines. Capacity per rack is lower and the hardware is dearer per core, and the per-minute price reflects that.
Should I rent macOS runners by the minute or by the month?
Per-minute billing suits teams with a few builds a day or bursty demand. A dedicated Mac billed monthly costs the same whether idle or busy, so it wins once it is in use for a large part of the working day. Multiply your monthly macOS minutes by the per-minute rate and compare with the monthly price of the hosts you would need.
Which third-party runners support Windows?
Fewer than support Linux. The list on this page shows the runners whose documentation covers Windows; the first-party runners of GitHub, GitLab and Azure Pipelines all do, and bring-your-own-cloud products can launch Windows instances in your cloud account.
Can GitHub Actions run jobs on a GPU?
Yes. GitHub offers GPU-powered larger runners, some third-party vendors offer GPU runners, and self-hosted or bring-your-own-cloud runners can use any GPU instance in your cloud account. The list on this page shows the runners that document GPU support.
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.
What is the official way to autoscale self-hosted GitHub Actions runners?
GitHub maintains Actions Runner Controller (ARC), a Kubernetes operator, and its runner scale sets. Other open-source projects scale runners on cloud VMs or microVMs instead of Kubernetes. See self-hosting GitHub Actions runners.
Can I use my own runners with GitLab.com?
Yes. Install the open-source GitLab Runner on your own machines or cloud instances and register it with a project, group or instance. Jobs that run on your own runners do not consume GitLab compute minutes.
Are self-hosted runners safe for public repositories?
Not persistent ones. Anyone who can open a pull request can run code on the runner, and a persistent machine keeps whatever that code leaves behind. GitHub’s documentation says self-hosted runners should almost never be used for public repositories. If you must, use ephemeral runners that give every job a fresh VM and require approval for workflows from outside contributors. See the runner security guide.
What should I check before sending my code to a third-party runner?
How jobs are isolated from other customers (ideally a dedicated VM or microVM per job), whether runners are single-use, where the machines are located, which compliance reports the vendor can share, how caches are scoped, and what the GitHub App’s permissions allow.
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.