iOS and macOS build agents for Unity and Unreal projects
For game studios that develop on Windows and ship to iPhone, iPad or Mac. Engine projects are large, imports take time and every Apple build ends in Xcode. Dedicated Mac minis act as build agents in your own pipeline, keep their caches between builds and produce signed builds, notarised where needed.
- release/1.4UnityiOS
- mainUnitymacOS
- feature/new-hudUnrealiOS
- mainUnrealmacOS
What this solves
Large projects and long imports
A persistent build agent keeps the workspace, imported assets and shader caches on its SSD, so the next build does not start from zero.
Apple-only final steps
Compiling the generated Xcode project, code signing, archiving and notarising Mac builds all need macOS and Xcode.
Parallel agents instead of one queue
Add a Mac per platform or branch, so an iOS build does not wait for a macOS build to finish.
Example workflow
Nightly iOS build of a Unity project
- 1
Your build system starts the nightly job on a Mac build agent.
- 2
The agent syncs changes from Perforce or Git LFS into its existing workspace.
- 3
Unity runs in batch mode, reuses the Library folder and exports the Xcode project.
- 4
xcodebuild compiles, signs and archives the app.
- 5
The build is uploaded to TestFlight and the logs go back to your build system.
What runs where in an Apple game build
Engine work can stay on your Windows workstations. The Mac agent handles everything that depends on Xcode and Apple's signing tools.
| Build step | Runs on | Note |
|---|---|---|
| Asset import and content cooking for iOS or macOS | Runs onWindows or Mac | NoteOn the Mac agent the results stay cached for the next build. |
| Exporting the Xcode project (Unity) | Runs onWindows or Mac | NoteRunning it on the Mac avoids copying the project between machines. |
| Xcode compile, code signing and archive | Runs onMac | NoteNeeds Xcode and the signing keychain. |
| Notarising Mac builds for distribution outside the App Store | Runs onMac | Notenotarytool is part of Xcode. |
| Unreal remote iOS build from Windows | Runs onMac over SSH | NoteUnreal sends the build to the Mac and gets the result back. |
| Gameplay performance testing | Runs onTarget devices | NoteMeasure on the iPhones, iPads and Macs your players use. |
How to set it up and run it
- 1
Choose storage first. An engine project, its cache folders and Xcode output add up quickly; 1 TB is the safer default for larger projects.
- 2
Install Xcode, then the engine: Unity Hub with the matching editor version and iOS or Mac build support, or the Unreal Engine version your project uses.
- 3
Install your build agent, for example Jenkins, TeamCity, GitLab Runner or Buildkite, as a dedicated macOS user that starts again after a reboot.
- 4
For Unreal on Windows, point the iOS remote build settings at the Mac over SSH, or run your BuildGraph scripts directly on the Mac agent.
- 5
Keep caches on the Mac: the Unity Library folder, a Unity Accelerator if you use one, and Unreal derived data. Clean them on a schedule you control.
- 6
For Mac builds distributed outside the App Store, sign with a Developer ID certificate and notarise with notarytool before release.
Which configuration fits
Mac mini M6
- 12-core CPU · 12-core GPU
- Memory: 32 GB
- Storage: 1 TB SSD
Good fit for
Smaller projects or a single platform, with room for the workspace and caches.
€206/moBilled yearly, excl. VAT
Who does what
vBoxx provides
- Dedicated Mac mini M6 or M5 Pro build agents, with M5 Pro options up to 18 CPU cores or 64 GB memory
- Persistent SSD storage up to 1 TB per Mac, so workspaces and caches survive between builds
- Network: 10 Gigabit Ethernet port · 1 Gbit/s unmetered · public IPv4 + IPv6, for fast syncs from Perforce or Git
- Remote APC power control to hard-reboot a stuck agent, included
- Optional JetKVM console and remote hands for physical tasks
You manage
- Engine installs, versions and licences
- Build agent, build scripts and version control credentials
- Signing certificates, notarisation credentials and App Store Connect keys
- Cache clean-up and storage planning
- Backups of anything that is not in version control
Before you choose this setup
- Storage per Mac is up to 1 TB. For very large workspaces, contact us before ordering; attaching external storage is a remote-hands request and depends on the situation.
- A hosted Mac mini is a build machine, not a playtest device. Measure gameplay performance on the iPhones, iPads and Macs your players use.
- There is no managed build service included. vBoxx runs the hardware, power and network; your team runs the pipeline.
Questions about game builds for Unity and Unreal
It can be. Unity Build Automation is a hosted service; here you run your own build agents on dedicated Macs. You manage the pipeline, and in return you control Xcode versions, caches and the build machine.
Yes. Unreal Engine supports remote iOS builds from Windows to a Mac over SSH. You can also run the whole build on the Mac agent with BuildGraph or your build system.
Start with one agent per Apple platform that builds regularly. Add Macs when builds start to queue, and measure build times on your own project before scaling.
Yes. The Mac is persistent and dedicated to you, so the workspace, the Unity Library folder and Unreal derived data stay on the SSD until you remove them.
Yes. The Mac connects to your Perforce, Git or Unity Version Control server like any other client. Use a VPN or an IP allowlist if your server is not public.