Service Level Agreement
What we commit to keeping running, how we measure it, and what you get if we miss. The numbers here are ones we believe we can hold every month, not ones chosen to look good.
1What this covers
This Service Level Agreement applies to paid MacBuildCloud services: concurrency seats, dedicated Mac machines, and builds paid for with minute packs. It does not apply to the free tier, to beta features we have labelled as such, or to the public website and documentation.
Where this agreement gives you a remedy, that remedy is a service credit. Service credits are the sole and exclusive remedy for a failure to meet the commitments in this document. Nothing here limits your rights under the Refund Policy for time wasted by our faults, which is credited automatically and separately.
2The commitment
| Service | Monthly availability |
|---|---|
| Shared build service | 99.5% |
| Dedicated machines | 99.5%, plus the hardware replacement target in section 4 |
| Artifact download | 99.5% |
| Account and billing pages | 99.5% |
99.5% of a 30-day month allows about 3 hours 39 minutes of downtime. We have set the number at a level we believe we can hold every month rather than one that reads well in a sales deck. If we consistently do better, we will raise it and say so.
3How availability is measured
Shared build service. A minute counts as unavailable if, during that minute, builds submitted by a customer with available balance could not be started or were terminated by a fault on our side. Availability for the month is .
Dedicated machines. Measured per machine. A minute counts as unavailable if you could not reach or use your machine because of a hardware, power or network fault on our side.
We measure from our monitoring in Hong Kong, and check the control plane from a second network. If your own measurements disagree with ours, send them to support@macbuildcloud.com and we will look at both. Where the evidence is genuinely ambiguous we will resolve it in your favour.
4Dedicated machines: replacement, not redundancy
A dedicated Mac mini is a single physical computer. It has one power supply, one SSD and no redundant components — that is what makes it a dedicated machine rather than a slice of a cluster. We are not going to pretend otherwise with a high availability number.
What we commit to instead is recovery time. If your dedicated machine fails and cannot be brought back remotely, we will move your lease to an equivalent machine within 4 hours during Hong Kong business hours, or within 12 hours otherwise. Your plan and paid-through date do not change. The replacement comes with a new login password and a new SSH port, both on your machine page, and we email you when it is ready.
Files do not move with you. Anything that existed only on the failed machine may be lost, which is why we tell you not to keep anything there that you have not also pushed elsewhere. If the failed machine is repaired, we erase your account on it before anyone else uses it. If we miss the times above, section 7 applies.
5Scheduled maintenance
Planned maintenance does not count as downtime, provided we give you at least 72 hours notice by email and to the status page, and it falls inside a published window. We aim for no more than 4 hours of planned maintenance in any calendar month.
Emergency maintenance to fix a security problem may happen without notice. We will tell you what we did and why within 48 hours. Emergency maintenance does count as downtime if it makes the service unavailable.
6What does not count
The commitment does not apply to time lost because of:
- your own code, tests, dependencies, credentials or configuration;
- your network, or the network between you and us, outside our control;
- an outage at a third party we depend on and cannot route around — for example a certificate authority, an upstream package registry, or Apple's notarisation or developer services;
- your account being suspended under the Acceptable Use Policy, on hold during a payment dispute, or downgraded for non-payment;
- use of the service in a way these terms do not permit;
- force majeure: events genuinely outside our control, including power grid failure, natural disaster, or government action.
We will not stretch these exclusions. If a failure is arguably ours, we will treat it as ours.
7Service credits
| Monthly availability | Credit |
|---|---|
| Below 99.5% but at or above 99.0% | 10% of that month's fee |
| Below 99.0% but at or above 95.0% | 25% of that month's fee |
| Below 95.0% | 50% of that month's fee |
| Dedicated machine not replaced within the section 4 target | A further 10%, once per incident |
"That month's fee" means what you paid for the affected service in the month the incident occurred. Credits in a single month are capped at 100% of that fee. Credits are applied to your balance or to your next invoice; they are not paid in cash and are not transferable.
Minute packs are consumed by the second, so time wasted by our faults is credited back as minutes automatically and does not need an SLA claim. Section 7 exists for subscription fees, where you paid for a period rather than for usage.
8How to claim
Email support@macbuildcloud.com within 30 days of the end of the month in question, from the address on the account. Tell us the dates and times, which builds or machines were affected, and any logs or error output you have.
We reply within two business days. If we agree, the credit appears on your next invoice. If we disagree, we will show you our monitoring data for the period so that you can see what we saw.
Where our own monitoring shows we missed the commitment, we will apply the credit without waiting for you to ask. The claim process exists for cases we did not detect, not as a hurdle.
9Chronic failure
If we miss the availability commitment in three consecutive months, you may terminate the affected subscription immediately by writing to us, and we will refund the unused portion of the current period on top of any service credits. You do not have to wait for a renewal date.
10Status and incident reports
We publish current service status and a history of incidents. For any incident that breaches this agreement we publish a written report within 5 business days covering what happened, when, what was affected, why, and what we changed so it does not happen again. We publish these whether or not anyone asks.
11Changes
We may change this agreement, but not to your detriment during a period you have already paid for. We will email account holders at least 30 days before a material change takes effect. The version that applies to a claim is the one in force when the incident happened.