Reference

FAQ

Last updated 6 November 2026

Questions we have actually been asked, answered without marketing language. Billing questions live on the pricing page; this is everything else.

01The machines

What am I actually building on?
An Apple M6 Mac mini with 24 GB of memory, in our rack. Your build runs in a macOS virtual machine on it, created from a standard image seconds before your build starts and destroyed when it ends.

Why a virtual machine and not the bare Mac?
Because nothing should survive between two customers' builds. A fresh machine per build means a build cannot be poisoned by the one before it, and your credentials cannot outlive your build. If you want the bare Mac anyway, that is what a dedicated machine is.

Is this allowed under Apple's licence?
We run at most two virtual machines per physical Mac and lease dedicated machines under section 3 of Apple's licence. Our reading of how the licence applies to the build service is on the software licensing page. It has not been confirmed by Apple, and we will change how we operate if Apple tells us otherwise.

I develop on Windows (or Linux). Can I use this?
Yes, and it is what we were built for. Everything you touch is a web page and your Git repository: you never need a Mac of your own. Your iOS app is compiled on ours, the signed .ipa is produced there, and the upload to TestFlight happens there too. Even the terminal you get on a failed build runs in your browser, so there is nothing to install. Signing certificates can be created with OpenSSL on Windows — see the signing guide. The one thing a Mac still does better is trying the build on a simulator before you push; for that, TestFlight on a real iPhone is the usual answer.

What is installed?
Xcode 27.2 on macOS 26.6.2, with Flutter, Node 24, CocoaPods, Ruby via rbenv, JDK 17 and the Android SDK all on the path. Homebrew is there for anything else. See the guide for your stack for exact versions.

Can I choose a different Xcode version?
Yes, from the images we offer: Xcode 27.2 (the default) and Xcode 26.6. One line in your build config picks one — see image. If you need an Xcode we do not offer, write to us; it is a question of demand, not of difficulty.

02Code and data

Do you keep my source code?
No. It is cloned onto the build machine and destroyed with it. We keep the build log, the artifacts you asked us to keep, and the metadata about the run — repository name, ref, commit, timings.

How long do artifacts live?
30 days, then they are deleted. You can shorten that to as little as a day under Activity & data in your account; you cannot make it longer, because 30 days is also what our privacy policy promises everyone. Share links last 24 hours, and are shortenable the same way.

Can I see who did what on my account?
Yes. Activity & data lists every build trigger, artifact download, share link, secret change and sign-in-related event, with the time and the address it came from, and exports it as CSV. It is append-only: neither you nor we can edit or remove an entry.

Are artifacts encrypted?
Yes, each with its own key, at rest on our disks. An artifact is decrypted only while it is being streamed to someone entitled to download it.

What about my signing certificate?
Encrypted at rest, decrypted onto a read-only mount that the build machine can read but not modify, imported into a temporary keychain that exists for that build alone, and gone when the machine is destroyed. It is never written to the machine's disk and never appears in your build script, so it cannot leak into a log or an artifact. The signing guide sets out the whole sequence.

Will a build ever change something in my Apple Developer account?
No. We never pass Xcode's -allowProvisioningUpdates, so no build can create a certificate, register a device, or edit a profile. You create them; we use them.

Can you read my build logs?
Yes, and we do when you ask for support — that is usually the fastest way to answer. Nobody reads them otherwise. Values you save as secrets (six characters or longer) are redacted from the log. Anything else you print stays in it, so do not print credentials you have not saved as secrets.

03How builds run

What triggers a build?
A push, a pull request, a tag, a schedule, a click in the dashboard, or the API. Push, pull-request and tag builds arrive through our GitHub app, so a repository has to be connected that way for them; a public repository you add by name builds on demand, on a schedule or through the API.

Can builds reach the internet?
Yes, directly, and dependencies come from the public package registries. Mail, scanning and common mining ports are blocked. Builds cannot reach anything on your network, and cannot reach each other.

Can I get a shell on the machine?
If the build failed and you had turned on Debug on failure for that repository (on the Repositories page) or pressed Keep this machine if the build fails while it ran, yes — the machine is held open and you get a terminal in your browser, on the same machine, in the state it failed in. Not on a machine that is still running, and not on someone else's.

Can two builds run at once?
One at a time on the free and pack tiers. A concurrency seat is one slot; add seats for more. A dedicated plan includes two build cloud slots.

What is the longest a build can run?
30 minutes on the free tier, 2 hours on paid. A build that hits the limit is stopped and billed for the time it used.

04Accounts and access

Why do you want a card before my first free build?
Because free compute is a standing target for crypto-mining abuse, and a working card is the one thing that is expensive to fake at scale. We do not charge it, and there is no post-paid overage — when your balance runs out, builds are refused rather than billed.

Do you run other checks on new accounts?
Yes, and deliberately quiet ones: disposable email domains, a burst of signups from one address. If we get it wrong you will see a clear message rather than a silent failure, and a person reads every appeal.

Can my whole team use one account?
Every plan includes two team members, and more are $15 each. There are three roles, each including the one before it: Trigger builds (start builds, read history, download artifacts), Manage secrets (plus secrets and team API tokens) and Billing and people (plus payment, invoices and who is on the team).

How do I delete my account?
Email support@macbuildcloud.com from the address on the account. Today a person does it, not a button — we would rather tell you that than pretend otherwise. We do it within 30 days: your sign-in details, artifacts and logs are deleted. Billing records are kept for seven years because Hong Kong law requires it, with card details and addresses removed.

05Where things stand

We would rather you know these before you depend on us:

The full list, including our subprocessors and what each one sees, is on the trust page. It has a section about what we have not done, which is the part worth reading.

06Something not answered here

support@macbuildcloud.com. A person replies. If the answer turns out to be useful to more than one customer it ends up on this page.


Something here wrong or missing? Tell us — we read every message, and documentation fixes go out the same day.