Using a hosted Mac mini as an iOS CI build server
Xcode only runs on macOS, so every iOS team needs a Mac somewhere in its pipeline. This guide looks at running that Mac as a dedicated build machine in an Australian data centre: how it connects to your CI, how to size it, and when it is cheaper than paying by the minute.
Why a dedicated build Mac
- Warm caches. A machine that persists between jobs keeps derived data, Swift package checkouts and simulator runtimes on disk. Hosted runners usually start clean and spend minutes rebuilding that state.
- Your Xcode, your schedule. You decide which Xcode versions are installed and when to move to a new one.
- A flat cost. Hosted macOS runners are billed per minute. A dedicated machine costs the same whether it builds once a day or all day.
- It is not someone's laptop. Release builds stop depending on who is in the office.
How it connects to your CI
Install your CI system's agent on the Mac: a GitHub Actions self-hosted runner, a GitLab Runner, a Bitbucket macOS runner, a Buildkite agent or a Jenkins agent. These agents connect outward to the CI service and wait for jobs, so you do not need to open inbound ports for CI. Jobs then target the machine by label, for example runs-on: [self-hosted, macOS, ARM64] in GitHub Actions.
The fixed IPv4 address is useful in the other direction: you can add it to the allow-list of a private Git server, package registry or artifact store.
Sizing
- Memory: 16 GB handles one build-and-test job at a time for most apps. Run one runner per machine and let jobs queue.
- Storage is the constraint. On a 256 GB disk, keep one or two Xcode versions, install only the simulator runtimes you test against, and clean up on a schedule:
xcrun simctl delete unavailableand a periodic purge of~/Library/Developer/Xcode/DerivedData. - Need more? Our rental is a single configuration (M6, 16 GB, 256 GB). Teams with large apps or many Xcode versions can buy a Mac mini with more storage and use the hosting plan for A$89 a month.
Code signing on a headless Mac
- Use an App Store Connect API key for uploads and provisioning instead of a person's Apple Account and password.
- Put signing certificates in a dedicated keychain that the build unlocks, and keep the source of truth somewhere else, such as an encrypted repository managed with fastlane match.
- Run the runner as a standard user created for CI, and store secrets in your CI system, not in files on the machine.
Security
A self-hosted runner executes whatever a workflow tells it to, and it does not reset between jobs. Use it for private repositories only; GitHub itself advises against attaching self-hosted runners to public repositories, where a pull request from a stranger could run code on your machine. Clean the workspace at the start of each job, and keep SSH on keys only.
Flat fee or per-minute?
The comparison is simple once you know your own usage:
Break-even minutes per month = monthly cost of the dedicated Mac ÷ per-minute price of your hosted macOS runner.
Take the minutes from your CI provider's billing page and the per-minute rate from its current price list, in the same currency. If you use more minutes than the break-even figure, a dedicated machine is cheaper. Warm caches also shorten each build, which the formula does not capture.
Hosted runners remain the better choice when you build rarely, when you need many jobs in parallel for short bursts, or when nobody on the team wants to look after a Mac.
What you take on
- One machine is one queue. There is no burst capacity unless you add machines.
- macOS and Xcode updates are yours to schedule and install.
- We keep the machine powered and connected and can reboot it on request. We have not opened yet, so we do not publish an uptime figure.
Why Australia
For an Australian team, a build machine in Melbourne or Sydney means your source code is checked out and your signing keys are used on hardware inside the country, and remote sessions into the machine respond quickly. The address is a data-centre address; we do not offer residential IP addresses and do not provide or help with getting around the regional restrictions of any service.
Rent a dedicated M6 build machine for A$199 a month, or host your own Mac mini for A$89 a month, ex GST, in Melbourne or Sydney. Reserve with a A$50 deposit that is refundable at any time.
See plans and reserveLast updated 21 November 2026