Build minutes cost in 2026: every vendor's pricing model

A build minute looks like a unit. It is not. Each CI vendor counts, rounds, and surcharges differently, and those small rules compound into bills that surprise teams every quarter. This page breaks down what one minute actually costs in 2026 across the seven CI platforms most teams evaluate, with vendor pricing pages cited for each.

What a build minute actually means

A build minute is the wall-clock duration a job runs on a hosted runner, rounded up by rules that differ per vendor and per plan. The runner clock starts when the job is dispatched to a runner (after queue time), not when you push the commit. Setup steps count: cloning your repo, restoring caches, pulling Docker images. Tear-down counts too. Anything inside the job container before the explicit `run` step is your minutes.

The first surprise is rounding. GitHub Actions and GitLab round each job up to the nearest whole minute. A 30-second job costs the same as a 59-second job. Pipelines that fan out into many short jobs (which is great for parallelism) pay the rounding tax on every one of them. A 20-job matrix where each takes 35 seconds bills as 20 minutes, not 12. CircleCI bills in credits at one-second granularity on Linux, so the rounding penalty does not apply there. AWS CodeBuild bills per second after a one-minute minimum: same 35-second job bills as 60 seconds.

The second surprise is the OS multiplier. GitHub Actions applies a 1x factor for Linux, 2x for Windows, and 10x for macOS. So a 10-minute Windows job consumes 20 minutes of your free tier and bills at the Windows rate. A 10-minute macOS job consumes 100 minutes of free tier and bills at $0.48. The multiplier exists because the underlying hardware cost is genuinely different. Linux runs as a container slot on shared compute. Windows requires a full VM with a paid Microsoft licence. macOS, per Apple licensing, must run on physical Mac hardware leased on 24-hour minimums. GitLab notably does not apply OS surcharges on its shared runners as of 2026, which makes it structurally cheaper for Windows-heavy or macOS-heavy CI: see the GitLab CI minutes documentation for the live multiplier table.

The third surprise is concurrency caps. Free tiers and lower paid tiers cap the number of concurrent jobs your account can run. GitHub Actions Free allows 20 concurrent jobs across the account. CircleCI Free allows one. Hitting the cap means jobs queue, which extends pipeline wall-clock without lowering the bill. Worse, the queue time pressures teams to upgrade to a higher tier purely to unblock parallelism, which is often the largest single jump in their CI bill.

Per-vendor build-minute rates (2026)

The table below is the headline rate for the lowest-tier paid plan on each platform, with the default Linux runner class. All figures verified against vendor pricing pages, which are linked in the source column. Always re-verify before procurement: pricing is a moving target and we have seen multiple platforms re-price more than once a year.

Worked example: a 25-developer team in 2026

Consider a 25-developer team shipping a Node service plus an iOS client. Each developer pushes 5 times per workday on average. Every push triggers a CI run that takes 8 minutes on Linux for lint, unit tests, and integration tests, plus a 12-minute macOS build on the iOS side for the engineers who touch the mobile app (assume 6 of the 25 do). Twenty working days per month.

Linux usage: 25 devs x 5 pushes/day x 20 days x 8 min = 20,000 min/month. iOS macOS usage: 6 devs x 5 pushes/day x 20 days x 12 min = 7,200 min/month. On GitHub Actions Team plan that is 17,000 billable Linux min after the 3,000 free allowance, plus 7,200 macOS min that consumes 72,000 free-tier units (well past the cap). Net bill: 17,000 x $0.006 + 7,200 x $0.048 = $102 + $345.60 = roughly $448/month for compute, plus the per-seat licence at $4 x 25 = $100. Total about $548/month.

Same team on GitLab Premium (no OS surcharge): 27,200 total min, less the included 10,000 GitLab minutes on Premium, leaves 17,200 billable minutes at the flat $0.010 rate, totalling $172 in compute. Plus per-seat at $29/user x 25 = $725. Total about $897/month. GitLab is cheaper on compute but more expensive overall because the per-seat is steep.

Same team on self-hosted GitHub Actions runners on a pair of c5.2xlarge spot instances ($0.10/hr each): 1,440 hours/month x $0.20 = $288/month for compute, plus the $0.002/min platform fee on private repos (added March 2026): 27,200 x $0.002 = $54.40. Total compute $342, plus the per-seat at $4 x 25 = $100. Total about $442/month, but you now own the runners and the on-call burden. The savings are real but conditional on having an engineer who can keep the runner controller healthy.

The hidden minute multipliers

Headline rates only describe what one minute on the runner costs. They do not describe what your bill becomes once you account for retries, queue time, and tier upgrades that exist solely to lift concurrency caps.

Retries are the largest hidden multiplier. A flake rate of 10% (typical for medium-maturity teams per published industry research from Snyk and others) means roughly one in ten builds is re-run, doubling the minute spend on that branch. Quarterly bills typically come in 8-15% over the un-retried estimate purely because of flake. The fix is structural (deflake, quarantine, retry-only-the-failed-test) not financial, but the cost line is real. We dig into this on the failed-build rerun cost page.

Queue time is not billed but it costs developer time. The economic value of cutting queue time often exceeds the savings of optimising minute spend. We quantify that on the developer wait time cost page using DORA and Stack Overflow Developer Survey salary anchors.

Tier-upgrade cost is the most sneaky. A team on GitHub Actions Team can hit the 60 concurrent job cap once it scales past about 30 active developers. The path to lift the cap is GitHub Enterprise, which jumps the per-seat from $4/user to $21/user. The CI bill effectively quintuples for reasons unrelated to minute consumption. Plan ahead by knowing your concurrent-job ceiling now and the next-tier price.

Reading vendor pricing tables correctly

Three rules. First, ignore the "included minutes" in marketing copy until you compare them across vendors at the same plan tier. Free-tier numbers are not equivalents (GitHub Free includes 2,000, GitLab Free includes 400, but GitLab does not apply OS multipliers). Second, find the per-OS rate. Many marketing pages bury Windows and macOS pricing two clicks deep. Third, find the concurrent-job cap and the price of lifting it. The minute rate is rarely the binding constraint at scale; the concurrency cap is.

Good vendor pricing pages to bookmark: the live GitHub plans page with the "Compare plans" expand, the GitLab pricing with the CI minutes line item, the CircleCI pricing with its credits calculator, and the AWS CodeBuild pricing page with the compute-type matrix. We re-verify our table against these monthly.

Frequently Asked Questions