Legal

Software Licensing

Version 1.1 · Effective 6 November 2026

Who licenses what to whom. The important part is the first line: you are buying a managed service, not a licence to software, and your code stays entirely yours.

1Why this document exists

When you use our managed build service, a reasonable question is: who is licensing what to whom? Apple licenses macOS. We own the hardware. You run your build on it. Getting this wrong is how Mac hosting companies end up in trouble, so we would rather set it out than leave it to be inferred.

The short answer: we are selling you a managed service, not a licence to software. We do not sublicense macOS or Xcode to you, and you do not receive a copy of either.

2What you are buying

We sell two things, and Apple's licence applies to them differently. This section covers the build service; section 4 covers dedicated machines.

With the build service you are buying access to a service that we operate. Concretely, we:

You never take possession of the hardware, you do not receive a copy of macOS or Xcode, and nothing is installed on any computer of yours. If you stop paying, nothing needs to be uninstalled or returned, because you were never given anything to keep.

3Apple's software licence

macOS on our machines is licensed by Apple to us as the owner of the Apple-branded hardware it runs on. Apple's macOS Software Licence Agreement permits a limited number of additional macOS virtual machines to run on Apple-branded hardware. We run at most two virtual machines per physical Mac and we do not oversubscribe.

That number is not the whole picture. Apple's licence also restricts using macOS to provide services to others, such as service bureau and time-sharing services, except as its section 3 allows. We run the build service on this reading: you submit a build, we keep control of the machine and you never log in to it, so you are not leasing a Mac. Apple has not confirmed this reading. It is ours, not legal advice, and section 9 says what happens if it turns out to be wrong.

We do not modify macOS, we do not run it on non-Apple hardware, and we do not provide you with a copy of it to run anywhere else. Xcode and the Apple developer tools are installed on our machines under Apple's terms for those tools.

If Apple changes its licence terms in a way that affects how we can operate, we will change how we operate rather than continue and hope. Where that materially changes the service you are paying for, section 9 applies.

4Dedicated machines

A dedicated Mac mini is a different arrangement from the build service, and we describe it plainly because the licensing position depends on the description being true.

What it is. We reserve one physical Mac that we own for one customer at a time. We create a standard macOS user account on it for you and give you the credentials. You install and run what you like inside that account. For the term of the lease that machine is taken out of our shared build capacity and nobody else has an account on it.

How it is licensed. We lease the machine to you under section 3 of Apple's macOS licence, which allows a Mac to be leased for developer services: continuous integration, software development, building from source, automated testing and the tools that support them. You do not take possession of the hardware, it does not leave our office, and you do not receive a copy of macOS to use elsewhere.

What you agree to. Before you use the machine you must review and agree to Apple's macOS licence and the terms of the preinstalled software, including Xcode. We ask for this at checkout. During the lease you have sole use of the machine, apart from the administrative support described below. If you breach Apple's terms, your right to use the software ends and we must end your access.

The 24-hour minimum term. Apple's licence requires each lease to run for at least 24 consecutive hours. For that reason dedicated machines are sold by the day, week, month, quarter or year and never by the hour. That is a condition of the licence rather than a commercial choice on our part. Refunds are set out in the Refund Policy.

What we keep the ability to do. We hold an administrator account on the machine, used to create and remove your tenant account, to restart the machine when you ask, and to reclaim it when the lease ends. We do not enrol the machine in any device management system and install no configuration profiles on it — see Terms section 9. When a lease ends we delete your account, erase its home directory, and remove files that account left in shared locations on the machine.

What we do not know. The two-virtual-machine limit in section 3 does not apply here, because a dedicated machine runs no virtual machines for you unless you create them yourself — and if you do, the same Apple limit applies to you as the person running them. We have set out our reading of Apple's terms in good faith; it is our reading, not legal advice, and section 9 says what happens if it turns out to be wrong.

5Your Apple developer credentials

Signing an iOS or macOS application requires your own Apple Developer Program membership and your own certificates. We do not sign on your behalf under our identity and we will not offer to. When you give us a signing certificate and provisioning profile, you are authorising us to use them for your builds, and you remain the party bound by your agreement with Apple.

We store those credentials encrypted, inject them into the build virtual machine at run time, and never write them to build logs. They are destroyed with the virtual machine along with everything else. You can revoke them at any time from your Apple developer account, and we would rather you did that than not, if you have any doubt.

6Your code stays yours

You keep all intellectual property rights in the source code you send us, the artifacts we produce from it, and anything else you upload. We claim nothing. We acquire no licence to your code beyond the narrow, temporary permission needed to do the one thing you asked: check it out, compile it, sign it, package it, and give you the result.

That permission ends when the build ends. We do not keep a copy of your source, we do not read it, we do not index it, and we do not use it to train or improve anything — ours or anyone else's.

7Our software stays ours

The MacBuildCloud website, API, control plane, build images and documentation are ours or our licensors'. Using the service does not give you a licence to copy, modify or redistribute them, or to reverse engineer them except where the law says you may regardless of what a contract states.

You may use our API and write scripts against it. That is what it is for.

8Third-party and open-source software

Our build images contain a large amount of third-party and open-source software — compilers, package managers, SDKs, command-line tools. Each remains under its own licence, and those licences govern your use of it, not this document. We do not represent that any particular third-party component is fit for your purpose or free of third-party claims.

You are responsible for the licences of the dependencies your own build pulls in. We do not audit your dependency tree and we are not in a position to.

Where we distribute open-source software as part of a build image, we comply with its licence terms, including making source available where that is required. Ask legal@macbuildcloud.com and we will point you at it.

9If the licensing position changes

This is a real risk in Mac hosting and we would rather name it. Apple could change its licence terms, its hardware, or its position on virtualisation in a way that makes part of this service impossible to offer lawfully. If that happens we will:

We will not keep taking money for something we have become unable to provide lawfully.

Version 1.1, 6 November 2026: sections 3 and 4 now describe the restrictions in Apple's licence, that dedicated machines are leased under its section 3, and what you agree to before using one.

10No agency, no resale

We are an independent contractor providing a service. Nothing here makes either of us the other's agent, partner or employee, and neither of us can bind the other.

You may use the service to build software for your own clients — that is ordinary agency work and it is fine. You may not resell access to our capacity as a compute service of your own, which is covered in the Acceptable Use Policy. If you want a partner arrangement, ask us; it needs to be agreed in writing.

This document forms part of our Terms of Service. English is the authoritative language.