Your own M4 runner. Unlimited macOS builds. $119/mo flat.

GitHub bills macOS runners at roughly $0.08 to $0.16 per minute depending on runner size, which is about 10 times the Linux rate. At the low end, a flat $119/mo dedicated runner breaks even at about 1,488 minutes per month. Past that point every extra minute on MacRun is free.

Two lines. You register the runner once with your repository or organization, then swap the runs-on label to point at your self-hosted macOS runner. Everything else in your pipeline stays exactly the same.

Yes. Apple's macOS Software License Agreement permits leasing a whole Mac for permitted developer services on monthly terms. Every MacRun lease is one customer per machine, billed monthly, restricted to developer services. We never put two customers on one unit.

We provision your machine within 1 to 4 hours of payment and email you when it is ready. Registering the runner and updating your workflow takes about 10 minutes after that.

We pin recent Xcode releases using xcodes and add new versions on request, usually the same day. You can select a version inside your job or request one from the customer portal.

For repeat builds, yes, and the gap is mostly cache. In our benchmark an incremental build ran 74 percent faster and a warm pod install ran 93 percent faster, because DerivedData and dependency caches stay on local SSD between runs instead of being rebuilt each time.

Access ends at the end of the paid period, then the machine is wiped automatically. Your account and data are deleted, the volume is securely erased, and the box is restored to a clean golden image before anyone else uses it.

Jobs serialize on your machine, which is the tradeoff for unlimited minutes on dedicated hardware. Teams that need heavy parallelism usually lease a second unit rather than paying per minute.

No SLA theater. It is one fast dedicated machine and an operator who answers email directly, usually within the hour. Live per-unit uptime is published on the status page so you can judge it yourself rather than take our word for it.

For shell access, yes. Your machine sits on a private network rather than the public internet, so there is no exposed SSH port for anyone to find. Tailscale is free at the sizes most teams need, runs on macOS, Linux and Windows, and the invite we send reaches that one machine and nothing else. Your CI jobs do not need it: GitHub Actions connects outbound from the runner itself, so your builds run whether or not anyone on your team can reach the machine directly.

Usually not. Most corporate blocking is UDP egress filtering, and Tailscale falls back to relays over TCP 443, which is slower but works. It genuinely fails where a proxy filters traffic to tailscale.com by name, or where you cannot install software on a managed laptop. Either way your builds are unaffected, because the runner dials out to GitHub from our network, not yours. The only thing you would lose is the occasional interactive shell or screen session, and those work from any other network, including a phone hotspot.

The machine is a normal Mac with SSH access, so you can point any CI system at it. Our setup docs and tooling are written for GitHub Actions, which is what we support first-hand.