Every iOS app has to be built on a Mac at some point. For a studio of three to fifteen people, that creates a surprisingly tricky business decision. Do you keep a Mac on a shelf in the office, buy a few for the team, pay per minute for a hosted build service or rent dedicated machines in a data centre?
There is no universally right answer, and the decision often gets made by accident when someone’s old laptop becomes the release machine. A better approach is to treat build capacity as a small business decision, with the same questions you would ask about any other equipment. This framework can help you work through it.
Map What You Actually Use
Start by measuring demand. Most studios guess at this and usually guess wrong. Look at your last two or three months and write down:
- How many builds you run per week, including test runs on pull requests.
- How long a typical build and test cycle takes.
- When builds cluster, such as release days or just before client demos.
- How many projects need different versions of Xcode at the same time.
- Who is waiting when the build machine is busy, and what their time costs.
Those figures let you calculate utilisation, which is the hours per week the machine is really working. A studio running a few builds a day on one app has very different needs from one that runs every pull request across six client projects. The waiting time matters as much as the machine itself. Developers who wait forty minutes for a test run lose focus, and that cost rarely shows up in the budget.
Compare the Four Options
Each option suits a different stage of a business, and studios often move between them as they grow.
|
Option |
Upfront cost |
Best for |
Main drawback |
|
Developer’s own laptop |
None |
Solo developers and very early projects |
Blocks the developer’s work and creates a single point of failure |
|
Hosted CI by the minute |
None |
Low or irregular build volume |
Costs climb with volume, and queues can appear at busy times |
|
Bought Macs in the office |
High |
Steady use over several years, with someone to look after them |
Hardware ageing, power and internet outages, remote access |
|
Rented dedicated Macs |
Low |
Steady use without wanting to own or manage hardware |
Monthly commitment, and less physical control |
Before comparing prices, make sure you compare like with like. A hosted service’s price per minute should be multiplied by your real monthly minutes, and owning a Mac should include depreciation, replacement and staff time, not just the purchase price. Apple’s own Xcode Cloud is also worth including, as it is tightly integrated and may suit studios with simple pipelines.
Questions That Decide It
Once the numbers are on the table, these questions usually settle the matter.
How predictable is your work? Client studios often have lumpy demand, with busy periods around releases. If you might not need the capacity in six months, avoid locking cash into hardware. If your product roadmap is steady, ownership looks better.
What does cash flow allow? Buying a few well-specified Macs is a significant purchase for a small company, and memory cannot be upgraded later on current models. Renting turns this into an operating expense, which many small businesses find easier to plan around. Talk to your accountant about how each option is treated where you are based.
Who will look after the machines? Someone has to install updates, renew certificates, clear disk space and restart a stuck runner. In a small studio, that person is usually a senior developer whose time is expensive. Count that time honestly.
Where is your team? A Mac in one office is awkward for a distributed team. Remote access over a home or office connection can be unreliable, and a power cut can stop a release. A data centre machine removes these issues but adds a monthly bill.
How sensitive is the code and signing material? Some clients have rules about where their source code and certificates can be stored. Check this before choosing, since a dedicated machine you control is often easier to explain than a shared pool.
A Middle Path
You do not need to commit everything at once. Many studios do well with a staged approach. Start with hosted CI while volume is low. When monthly minutes grow, try one dedicated machine for a single project for a month or two and compare build times and costs. If it works out, move other projects across. Check the licensing terms too: Apple’s macOS licence has specific rules on leasing, including a minimum lease period, so short-term rental has its limits.
For a good overview of the use cases, this article on who needs mac mini server capacity describes the scenarios where a dedicated remote Mac makes sense and where it does not. It is useful reading before you commit to either path.
Make a Decision You Can Revisit
Write down your decision with the numbers behind it, then set a date to review it, perhaps every six months. Your utilisation will change as projects begin and end. Hardware also moves quickly, and a machine that was a good buy two years ago may now be slow enough to cost more in waiting time than a newer one costs in fees.
Keep the review short. Compare actual build hours with the plan, ask the team whether waiting has become a problem, and check what the current option costs at today’s volume. Three signs suggest it is time to reconsider:
Build infrastructure is not glamorous, and few clients will ever ask about it. But it directly affects how quickly you can ship and how much of your team’s expensive time goes into waiting. For a small studio, getting this decision roughly right and reviewing it regularly matters far more than getting it perfect the first time.