How to choose a macOS server for iOS CI/CD

Xcode, the iOS SDK and the iOS Simulator run only on macOS, and Apple's software licence allows macOS only on Apple-branded computers. A Linux server cannot build and sign an iOS app for the App Store, so every iOS pipeline needs at least one Mac, whether it sits in an office, in a hosted CI service or in a data center.

A remote Mac in a data center has practical advantages over a machine under a desk: a stable network connection, a fixed IP address for webhooks and allow lists, and no office computer that someone switches off at night.

Apple sets a minimum Xcode and SDK version for uploads to App Store Connect and raises it regularly; in recent years the new minimum has taken effect each April. Since 28 April 2026, uploads must be built with Xcode 26 or later, and Apple has announced that the 27 SDKs will be required from April 2027.

Each Xcode release in turn needs a minimum macOS version: Xcode 27, for example, needs macOS Tahoe 26.6 or later and a Mac with Apple silicon. Before you choose a server, check three things:

• the Xcode version you need today and the one you will need after the next deadline;
• the minimum macOS version of that Xcode, listed on Apple's Xcode system requirements page;
• the macOS versions the server plan offers. Our order form lists the versions you can choose for each macOS plan.

Apple has announced that macOS Tahoe 26 is the last macOS release for Intel-based Macs; macOS 27 runs on Apple silicon only, and current Xcode releases need an Apple silicon Mac. Intel Macs remain useful for testing older macOS versions or x86_64 builds of existing apps, but a new build server for App Store work should be Apple silicon.

Apple silicon also simplifies simulator setup: Xcode downloads arm64 simulator runtimes, which saves disk space, and builds run natively without Rosetta.

At HyperDC, Apple Silicon macOS VPS plans run on Apple silicon hardware. Because Apple's Virtualization framework does not offer nested virtualization for macOS guests, you cannot run further virtual machines inside them; for that, choose a VDS.

Hosted, self-hosted or Apple's own

Xcode Cloud is Apple's hosted CI service and includes a monthly allowance of compute hours with the Apple Developer Program. A self-hosted runner on your own remote Mac gives you full control of the toolchain, caches that survive between builds and no per-minute billing. GitHub Actions, GitLab Runner and Jenkins all support macOS agents, and fastlane automates the build, test and upload steps.

Keep a logged-in session

UI tests, the Simulator and some keychain operations need a graphical user session. Run the runner as a user agent in a logged-in session rather than only over SSH, enable automatic login so the session returns after a restart, and stop the Mac from sleeping.

Treat a self-hosted runner as a production server

A self-hosted runner executes whatever code a pipeline gives it. Use it only with private repositories you trust, keep macOS and Xcode updated, and limit who can change the pipeline configuration.

Apple's macOS licence allows macOS only on Apple-branded hardware and limits a Mac to two additional macOS instances in virtual machines, for purposes such as software development and testing. It also sets terms for leasing Macs for development and continuous integration work, including a minimum lease period of 24 consecutive hours. The licence text on Apple's website is binding, so read it for your own use case.