Skip to content

Use case · iOS & macOS CI

Dedicated CI runners for iOS and macOS

Register a self-hosted runner on a Mac mini that only your team uses. Caches stay warm between builds, you choose the Xcode versions, and the price is the same every month no matter how many minutes you build.

Why a dedicated Mac

Built for this, not borrowed for it

Warm caches, faster builds

DerivedData, Swift Package Manager, CocoaPods and Homebrew caches stay on disk between jobs instead of being rebuilt on a fresh VM every time.

Your toolchain, your versions

Install exactly the Xcode releases and simulator runtimes your projects need, side by side, and upgrade on your schedule rather than a hosted image's.

Signing material stays private

Certificates and provisioning profiles live in a keychain on hardware no other customer touches, on a network segment no one else can reach.

Predictable cost

One flat monthly price per machine in EUR. Long test suites, nightly builds and release crunches do not change the bill.

Setup

From order to first job

  1. 1

    Rent and connect

    Order a plan, then add the machine to your tailnet with a Tailscale auth key or connect through WireGuard.

  2. 2

    Install your toolchain

    SSH in with the admin credentials from the console and install Xcode, command line tools, simulators and your package managers.

  3. 3

    Register the runner

    Install the runner for your CI system and run it as a service so it survives reboots.

  4. 4

    Operate it like a fleet

    Watch CPU, memory, disk and temperature in the console, reboot from the console or the API, and add machines when the queue grows.

Register a GitHub Actions runner (on the Mac mini)
mkdir -p ~/actions-runner && cd ~/actions-runner
# Download the latest osx-arm64 runner from github.com/actions/runner/releases
curl -fsSL -o runner.tar.gz <runner-download-url>
tar xzf runner.tar.gz
./config.sh --url https://github.com/<org>/<repo> --token <registration-token> --labels macos,arm64
./svc.sh install && ./svc.sh start
.github/workflows/test.yml
jobs:
  test:
    runs-on: [self-hosted, macos, arm64]
    steps:
      - uses: actions/checkout@v4
      - run: xcodebuild test -scheme App -destination 'platform=iOS Simulator,name=<simulator>'

Values in angle brackets are placeholders for your own details.

Good to know

  • Use self-hosted runners with private repositories, so untrusted pull requests cannot run code on your machine.
  • The same pattern works for GitLab Runner, Buildkite and Jenkins agents; Fastlane runs on the machine like any other tool.
  • You stay responsible for agreeing to the Xcode and SDK license terms when you install them.

Choosing a plan

Pick more memory if you run several simulators or parallel test destinations at once.

Compare plans and live availability →

Your own Mac mini in Spain, ready in minutes.

Monthly plans, billed in EUR. Cancel any time, effective at the end of the billing period.