A dedicated Mac mini as your GitHub Actions runner

Who it is for

• >iOS teams whose GitHub-hosted macOS minutes are a noticeable line item
• >Projects with long test suites or large dependency caches that suffer from cold starts
• >Teams that need specific Xcode versions, certificates, or tools pinned on the runner
• >Solo developers who want nightly builds and TestFlight uploads without a Mac at home

Why a dedicated runner beats hosted minutes for steady use

How the setup works

1. STEP 1

   Get the Mac

   Request a Mac mini; it is ready within 24 hours with SSH access.

2. STEP 2

   Install Xcode and tools

   Over SSH or remote desktop, install Xcode from Apple, select it with xcode-select, and add fastlane or other tools.

3. STEP 3

   Register the runner

   In your repository or organization settings, add a self-hosted runner for macOS and run the configuration commands GitHub gives you. Install it as a launchd service so it survives reboots.

4. STEP 4

   Point workflows at it

   Use runs-on: self-hosted with your labels. Keep secrets in GitHub, not on disk.

Security notes for a shared repository runner

• [x]Register at the repository or organization level you trust; GitHub recommends against self-hosted runners for public repositories because forks can run arbitrary code
• [x]Use short-lived tokens and GitHub secrets; do not store signing certificates in plain files longer than needed
• [x]The machine is dedicated to you, so no other MacMiniNode customer can see your jobs; you are responsible for what runs on it
• [x]Keep macOS, Xcode, and the runner agent updated

Real limitations and requirements

• [x]Machines are prepared by a person, not an automated pool. We commit to having your Mac ready within 24 hours of your request; your dashboard shows each stage.
• [x]One customer per computer. Sharing a machine among several end users, reselling access, or sublicensing is not permitted.
• [x]Administrator access is included but subject to security and licensing requirements: you cannot disable the management controls we rely on, and macOS use must follow Apple’s software license terms.
• [x]Permitted use is developer and business computing: software development, testing, CI, automation, and AI coding agents. See the Acceptable Use Policy.
• [x]No physical access to the hardware, and no hardware changes (memory and storage are fixed at the configuration you rent).
• [x]Third-party subscriptions are not included: Claude Code, OpenAI Codex, the Apple Developer Program, and any licensed software are yours to bring.
• [x]You are responsible for your own backups. When a rental ends, the storage is securely erased before the hardware is reassigned.

How remote access works

Your Mac mini stays powered on in our facility. You connect to it over the internet from a Mac, Windows PC, Linux machine, or tablet using two supported methods: SSH for the terminal, and remote desktop for the full macOS interface.

Connection details and step-by-step instructions appear inside your signed-in dashboard once the machine is ready; we never send credentials by plain email. Your files, tools, and sessions persist between connections, so you can disconnect and pick up where you left off.

Questions about this