Home › Blog › GitHub Actions: macOS runners bill 10x Linux

GitHub Actions: macOS Runners Bill 10x the Linux Rate, Windows 1.7x

19 November 2026 · CI/CD & DevOps & Infrastructure · 4 min read

Same pipeline. Same job. Same 1,000 minutes a month. Run it on GitHub's Linux runner and it's $6.00. Run the identical minute count on macOS and it's $62.00. That's not a typo and it's not a teaser rate — it's the standing per-minute price on GitHub's own Actions runner pricing page, checked today.

The three numbers nobody compares side by side

GitHub prices its standard hosted runners per minute, by OS, for private repositories past any included free allowance:

RunnerPrice per minuteMultiplier vs Linux
Linux 2-core$0.0061x
Windows 2-core$0.0101.67x
macOS 3-core/4-core$0.06210.33x

Windows at 1.67x makes sense if you've ever waited on a Windows VM to boot. macOS at 10.33x is the number that catches people — it's not double, it's not triple, it's an order of magnitude. Apple doesn't license macOS for third-party virtualization at the same density as Linux or Windows, so GitHub (and every other CI vendor running real Mac hardware under the hood) passes that constraint straight into the per-minute rate.

What that does at real volume

Here's the same monthly minute budget run through all three rates — no other costs, no seat fees, just the runner-minute line:

Minutes/monthLinuxFinestremacOS
500$3.00$5.00$31.00
1,000$6.00$10.00$62.00
5,000$30.00$50.00$310.00
10,000$60.00$100.00$620.00

At 10,000 minutes a month — a realistic number for a team running full test suites on every PR across a handful of active repos — the gap between an all-Linux pipeline and an all-macOS one is $560/month. That's before anyone's touched provider choice or runner size. It's purely the cost of the OS the job happened to run on.

Where macOS minutes actually come from

Nobody runs a full CI matrix on macOS by choice — it shows up because an iOS, macOS, or cross-platform build step needs real Apple hardware to sign and build against, and there's no Linux substitute for that step. The practical fix isn't "stop using macOS," it's isolating exactly which jobs need it. A lint step, a unit test suite, a Docker build — none of that needs macOS, and routing only the Xcode-dependent steps to a Mac runner while everything else stays on Linux is the difference between paying the 10.33x rate on 200 minutes and paying it on 2,000.

What I'd check before the next invoice

If a CI bill jumped and nobody changed the pipeline logic, the runner OS mix is the first thing I'd pull up — a workflow matrix that silently grew a macOS leg, or a job that got moved to Windows for a "quick fix" and never got moved back, shows up here before it shows up anywhere else. The fix is almost always a workflow file, not a vendor switch.

Run your own minute count through the GitHub Actions cost calculator (rates for all three runner OSes, plus CircleCI, GitLab CI, and Buildkite side by side), or compare full CI vendors on the GitHub Actions vs CircleCI vs Buildkite page. New to usage-based infra billing in general? Start with the guide gratuite sui costi API.

Per-minute rates verified against GitHub's own Actions runner pricing documentation, 2026-11-19. Rates apply to standard hosted runners on private repositories past any included free-minute allowance; public repositories on standard runners remain free. Prices change — confirm current rates on GitHub's pricing page before budgeting a CI-heavy pipeline.