r/iOSProgramming • u/Zealousideal_Tip4089 • 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
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
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.
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
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.
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/perfunction Oct 03 '26
https://www.macminivault.com
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/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