How to use a Mac mini as an iOS and Android build server
By Senthil Kumar P · Updated · 8 min read
Short answer
To use a Mac mini as a build server: connect it by Ethernet, set it to never sleep and to restart after a power failure, install Xcode, the Android SDK and your toolchain (Node, CocoaPods, JDK), sign in to your Apple developer account, and then give your team access, either with SSH, a CI self-hosted runner such as GitHub Actions, or VenelX Studio, which adds builds, store releases, tester links and simulators in a browser.
Why a Mac mini makes a good build server
iOS apps can only be built on macOS, so every iOS build pipeline ends on a Mac: yours, or one you rent by the minute. A Mac mini is the cheapest Mac that can stay on all day, it builds Android apps too, and once it's paid for there's no build meter. Your signing keys also stay on hardware you control.
The trade-off is that you look after it: power, network, macOS and Xcode updates.
What you need
- An Apple silicon Mac mini. Memory matters most: Xcode, simulators and Gradle are memory-hungry, so 16 GB or more is comfortable for one team.
- Enough SSD space for Xcode (and a second Xcode version during upgrades), simulator runtimes, the Android SDK and build caches. 512 GB is a sensible minimum.
- Wired Ethernet and a stable power supply.
- An Apple Developer Program membership and, for Android, a Google Play Console account.
Step 1: keep the Mac awake and reachable
In System Settings › Energy, turn on Prevent automatic sleeping when the display is off and Start up automatically after a power failure. Plug in Ethernet rather than relying on Wi-Fi.
If the Mac runs without a display, it still needs a user session for things like simulators and Keychain access, so set up automatic login for a dedicated build user, or stay signed in.
Step 2: install Xcode and the Android toolchain
# Xcode: install from the App Store or developer.apple.com, then
sudo xcode-select -s /Applications/Xcode.app
sudo xcodebuild -license accept
xcodebuild -runFirstLaunch
# Homebrew, then the usual mobile tools
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
brew install node cocoapods watchman
brew install --cask zulu@17 android-commandlinetools
Install the Android SDK platforms and build tools your apps target with sdkmanager, and set ANDROID_HOME in your shell profile. For Flutter, install the Flutter SDK and run flutter doctor.
Step 3: set up signing on the Mac
- iOS: create an App Store Connect API key with the App Manager role. Keep the
.p8file on the Mac, ideally in the Keychain, never in your repository. - Android: keep your upload keystore on the Mac and create a Google Play service account with release permissions for your app.
Step 4: give your team access
A build server is only useful if the team can use it. There are three common ways.
| Option | What you get | What you set up |
|---|---|---|
| SSH (plus a VPN) | A shell for engineers | Port forwarding or a VPN, user accounts, shared credentials, your own scripts |
| CI self-hosted runner (GitHub Actions, GitLab, Buildkite) | Builds on every push, inside your CI | Runner service, workflow YAML, usually fastlane for signing and uploads |
| VenelX Studio | Builds, tester links, TestFlight and Google Play releases, simulator sharing and a terminal, from a browser | Install the app, approve the Mac, add your keys |
They aren't exclusive. Many teams run a CI runner for pull-request checks and VenelX Studio for release builds and sharing on the same Mac.
To install VenelX Studio:
brew tap venelx/tap && brew trust venelx/tap && brew install --cask venelx
Then sign up at studio.venelx.com and approve the Mac. The Mac keeps one outbound connection, so you don't open ports or set up a VPN. Pricing is $79 a year for one Mac or $199 for two; see pricing.
Step 5: keep it healthy
- Update Xcode on purpose, not automatically: test a new Xcode on one Mac before switching the team.
- Clear old simulator runtimes and derived data now and then (VenelX Studio has clean-up rules for build caches and old runtimes).
- Watch free disk space; a full disk is the most common cause of mysterious build failures.