CI Runnerscirunners.org
Guide

macOS CI runners explained

Answer in brief

iOS and macOS apps must be built on macOS, and macOS may only run on Apple hardware. So macOS runners are physical Macs, usually Apple silicon Mac minis or Mac Studios, each running at most two macOS virtual machines. You can rent hosted runners by the minute, rent dedicated Macs by the month, or run your own Macs with a virtualization tool that clones a clean VM for each job. The right choice follows from how many hours a day the machines would be busy.

By the CI Runners editors · Updated

Why macOS is different

Linux runners are commodity cloud servers sliced into as many VMs as the hardware allows. macOS breaks both assumptions:

  • Apple’s software licence allows macOS to run only on Apple-branded computers.
  • The same licence permits two additional macOS instances in virtual machines per Mac.

A provider therefore buys and racks Macs and gets at most two concurrent jobs from each. That is the root of the price gap with Linux, and why macOS capacity cannot be scaled instantly.

Three ways to get macOS runners

OptionBillingSuitsWatch for
Hosted runnersPer minute of job timeLow or bursty volume; no operationsThe highest unit price; which chip a label maps to; queue time at peaks
Dedicated Macs in a data centrePer Mac per monthSteady volume; custom images; fixed capacityYou pay for idle time; you manage images and orchestration unless it is included
Your own Macs with a virtualization toolHardware cost plus your timeTeams with office or colo space and a platform engineerHardware refresh, power, remote management and macOS upgrades

Clean builds through virtualization

A long-lived Mac build machine drifts: stale simulators, leftover keychains, cached derived data. macOS virtualization fixes that. A tool built on Apple’s Virtualization framework clones a prepared macOS image, boots it for one job and deletes it afterwards, so each job starts from the same state. Images are distributed like container images, which makes “Xcode 16 on macOS 15” something you pull by name.

What to compare

  • Chip and cores. Apple silicon generations differ noticeably in Xcode build time. Find out what hardware a runner label actually is.
  • Xcode availability. How soon after release new Xcode versions and betas appear, and how long old ones stay.
  • Image control. Whether you can add tools or bring a whole image.
  • Caching. Derived data, Swift Package Manager and CocoaPods caches are large; proximity matters.
  • Signing. How certificates and profiles are provided, and whether the VM is destroyed afterwards.
  • Break-even. Monthly macOS minutes multiplied by the per-minute rate, against the monthly price of the dedicated Macs that would carry the same load.

The macOS and iOS use case lists the runners that document macOS support.

Frequently asked questions

Can I run macOS CI on Linux servers or in any cloud VM?
No. Apple’s licence allows macOS only on Apple hardware. Cloud macOS offerings are real Macs in a data centre.
How many macOS VMs can one Mac run?
Apple’s macOS licence permits two additional macOS instances in virtual machines on each Apple-branded computer, so a Mac runs at most two concurrent macOS build VMs.

Sources

  1. apple.com/legal/sla/
  2. developer.apple.com/documentation/virtualization
  3. docs.github.com/en/actions/concepts/runners/github-hosted-runners

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). macOS CI runners explained. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/guides/macos-ci-runners-explained/