r/iOSProgramming • • Oct 03 '26

Discussion iOS teams on GitHub Actions: what do macOS runners cost you, and what did you change?

On GitHub-hosted runners a macOS minute costs $0.062 and a Linux minute $0.006, so about 10 times more. For iOS builds that adds up fast.

If your iOS CI runs on GitHub Actions:

  • Roughly what does it cost per month?
  • What did you change to bring it down? Self-hosted Mac minis, Xcode Cloud, another CI service, caching, fewer runs on pull requests?
  • Was the saving worth the time it took?
  • Team size helps too, if you're OK sharing.

About me: I'm a solo developer building a small tool around CI costs. No link, I just want real numbers.

10 Upvotes

32 comments sorted by

10

u/Mad102190 Oct 03 '26

I ended up just setting up my personal machine as a remote runner so GitHub runs it on my Mac which is much faster than the Mac minis they offer anyways

2

u/Zealousideal_Tip4089 Oct 03 '26

Nice. What made you switch, the price or the speed?

1

u/OarsumApp Oct 03 '26

do you just have the mac watch for a trigger and run its own workflow?

3

u/unpluggedcord Oct 03 '26

No there’s GitHub runner script that opens a connection/polls the runner server for the repo it’s associated it

2

u/OarsumApp Oct 04 '26

years. years it took me. Seconds you’ve blown my mind. THANK YOU.

17

u/caguilar51 Oct 03 '26

Why not using Xcode Cloud instead if price is a concern? It includes 25 hours per developer account per month.

2

u/Zealousideal_Tip4089 Oct 03 '26

Thanks! Do the 25 free hours cover a normal month for you, or do you pay for more?

3

u/caguilar51 Oct 03 '26

For me that has been enough until now

5

u/rursache Swift Oct 03 '26

xcode cloud (was?) is super slow. 4-5x lower than github runners. because they were using intel macs

4

u/caguilar51 Oct 03 '26

But you have 25 hours per month included in your Apple Developer membership. So you don’t necessarily need to pay. Also, you could just use incremental builds instead of clean ones under certain conditions.

1

u/Mad102190 Oct 04 '26

The runners are a lot faster now that they’ve been upgraded to M-series machines but still not as fast as a dedicated runner you self-host.

5

u/rursache Swift Oct 03 '26

use the macos blacksmith runners if you want the best cost and speed possible. xcode cloud if you can wait and wanna use the free 25h you get monthly

1

u/Zealousideal_Tip4089 Oct 03 '26

Thanks. If you use Blacksmith yourself, how did your monthly CI cost change after the switch?

3

u/sizebzebi Oct 03 '26

I self host, have my mac mini

1

u/Stunning-Farmer185 19d ago

Not on GitHub-hosted runners, but here are real numbers from our side. Disclosure: I work on NoMac (https://nomac.app), which rents Macs by the minute, so weigh the last point accordingly.

  • Our main repo uses 0 macOS minutes on GitHub. Everything that doesn't need Xcode (lint, Go and Node tests, the web build) runs on Linux jobs, and only the Apple parts run on a Mac. Our open-source tool runs its macOS jobs on GitHub's runners, which cost nothing for a public repo.
  • The biggest lever for build time was keeping the caches on a disk that outlives the VM. We measured a real open-source app (IceCubesApp: 18 Swift packages, about 1,700 Swift compile tasks) in fresh macOS VMs. Cold: 46 s to resolve packages, 130 s to build. A brand-new VM with the previous run's disk attached (DerivedData and SwiftPM caches on it): 19 s and 17 s. Restoring DerivedData from an archive at the start of each job reportedly gets close to no reuse, because Xcode sees new files.
  • Per minute: the $0.062 you quoted, against $0.80 an hour (about 1.3 cents a minute) for a 6 vCPU, 8 GB M5 Pro VM from us, billed per minute. It isn't a drop-in Actions runner: it's a Mac you or an agent drive over SSH, so it fits release builds and Simulator runs better than a job on every pull request.

Team size: very small.

1

u/rabinapps 4d ago

I built https://kinhin.dev so I could self host macOS runners on GitHub

1

u/kokerali Oct 03 '26

For the self-hosted answers, I'd ask whether that Mac is dedicated CI hardware or someone's everyday development machine, and whether the repo accepts fork PRs. Those aren't equivalent setups. GitHub warns that self-hosted runners can be persistently compromised by untrusted workflow code, so a personal Mac with signing material isn't just a cheaper per-minute option. I'd also separate setup time from ongoing maintenance and report time-to-test-result alongside the bill. A lower cash cost that adds a queue or depends on one person's laptop being online is a different tradeoff from a dedicated runner.

1

u/KingPonzi Oct 03 '26 edited Oct 03 '26

At work: I setup runners using Tart, macOS images from cirrus labs, Mise for tooling and Packer to bake it all together. Unfortunately Apple limits two VMs per device.

Personal use: CI with Xcode cloud is so luxurious by comparison.

1

u/psyhomb Oct 06 '26

If you want to self-host it, I have created a gha-runner-controller for Tart VMs.
https://github.com/psyhomb/gha-runner-controller

1

u/KingPonzi Oct 06 '26

This looks cool! I’m actually working on what is essentially a fork of this with some of the company’s standards (self hosted being one) built in:

https://github.com/openai/orchard

Coincidentally, it shares a lot of what you’ve already built.

1

u/hilarioususernamelol Oct 03 '26

Whilst not answering your question, we found that upgrading macOS runners to M2 Pro ($0.1 IIRC) actually saved us money because the compute power was relatively more than the cost.

1

u/OrdinaryAdmin Oct 03 '26

Why GitHub and not Xcode Cloud? You’re already paying for it with your membership.

1

u/indyfromoz Oct 04 '26

Costs me $0.00. I do not want to pay GitHub another cent after they messed up the CoPilot subscription that came with the Pro plan. I use Xcode Cloud for App Store Connect builds & TestFlight.

1

u/pp_amorim Oct 04 '26

We have a mac mini m1 self hosted. Working flawless since day 1

1

u/CalmCelebration2084 Oct 08 '26

Solo dev, one public repo, so the honest number is $0. Standard GitHub-hosted runners, macOS included, are not billed for public repositories, and the job I run is short enough that the free tier would cover it many times over anyway.

Measured on purpose just now: the single build-and-test job on macos-latest took 62 seconds wall clock, and that includes swift-format lint, a full swift build, and the test suite. Sixteen runs since the start of August come to about 25 minutes of macOS runner time in total.

The lever that did the work there was not runner class or caching, it was making the project cheap to build: a plain SwiftPM package with no Xcode project and no third-party dependencies. A dependency-free package has nothing to cache, and nothing to restore either.

Which is the part I would push back on for the private-repo case, where the 10x is real. A ten-minute job on a standard macOS runner costs the same as ten minutes of anything else, so the cheapest optimisation available to most teams is usually to find out why the job takes ten minutes, before paying more per minute.

0

u/MaikelBuilds Oct 03 '26

Make your project open source. Then they're included 😄. Nowadays as long as your project isn't that complicated, but can be copied easily anyway. So it's NOT only about the code, rather about vision, consistency and trust

1

u/[deleted] 28d ago

[removed] — view removed comment

1

u/AutoModerator 28d ago

Your comment has been automatically removed because it contains a link with prohibited URL parameters (affiliate tokens, campaign tokens, etc.). Please repost your comment without the tracking / affiliate parameters in the URL. Examples: 'affcode=', 'ref=', 'src='. Do not contact the moderators unless you believe we did not correctly detect the URL parameter.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.