Documentation
MacBuildCloud runs your iOS and macOS builds on real Mac minis, billed by the minute. These pages tell you how to get a build running, how to sign it, and what to do when something breaks.
If you have ten minutes and a repository, start with the quick start. It ends with a real build on a real Mac.
01Getting started
- Quick start — connect a repository and get your first build running. About five minutes.
- Build configuration — the .macbuildcloud.yml file: every section, every limit, and what happens when you leave it out.
02Guides by stack
- Native iOS & macOS — Xcode projects and workspaces, schemes, simulators, test reports.
- Flutter — pub get, building an IPA, the CocoaPods cache.
- React Native — npm and CocoaPods, Hermes, release builds.
- Code signing & TestFlight — uploading a certificate and profile, and shipping a build to App Store Connect without keeping secrets in your repository.
03Reference
- API reference — trigger, list and cancel builds and read their status from your own scripts.
- Troubleshooting — the errors people actually hit, and what each one means.
- FAQ — billing, limits, privacy, and what we do with your code.
04What a build costs
Every account gets 200 free minutes a month. After that, minutes come in packs, or you can rent a whole machine. Queue time is never billed — the clock starts when your first command runs and stops when the last one finishes. See pricing.
A note on what we can see. Your source code is checked out inside a virtual machine that is destroyed when the build ends. Build artifacts are encrypted on our disks and deleted after 30 days. Secrets you upload are encrypted and never shown again — not to you, not to us. More in the FAQ.