Home › Blog › GitHub Actions: los «runners» de macOS cuestan 10 veces más que los de Linux

GitHub Actions: los «runners» de macOS cuestan 10 veces más que los de Linux y 1,7 veces más que los de Windows

19 de noviembre de 2026 · CI/CD, DevOps e infraestructura · Lectura de 4 minutos

El mismo pipeline. El mismo job. Los mismos 1000 minutos al mes. Ejecutadla en el runner Linux de GitHub y costará 6,00 $. Ejecutad el mismo número de minutos en macOS y serán 62,00 $. No es un error tipográfico ni una tarifa promocional: es el precio por minuto vigente en la propia página de precios de los runners de Actions de GitHub, consultada hoy.

Los tres números que nadie compara uno al lado del otro

GitHub cobra por sus «runners» alojados estándar por minuto, por sistema operativo, para los repositorios privados que superen cualquier límite gratuito incluido:

RunnerPrecio por minutoMultiplier frente a Linux
Linux de 2 núcleos$0.0061x
Windows de 2 núcleos$0.0101.67x
macOS 3 núcleos/4 núcleos$0.06210.33x

Windows, con un factor de 1,67x, tiene sentido si alguna vez ha esperado a que se inicie una máquina virtual de Windows. macOS, con un factor de 10,33x, es la cifra que llama la atención: no es el doble, no es el triple, es un orden de magnitud. Apple no concede licencias de macOS para la virtualización de terceros con la misma densidad que Linux o Windows, por lo que GitHub (y cualquier otro proveedor de CI que ejecute hardware Mac real de forma interna) traslada esa limitación directamente a la tarifa por minuto.

Qué efecto tiene a volumen real

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

Minutes/monthLinuxventanasmacos
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 guías gratuitas de costos de 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.