Solution

macOS build machines for iOS, without a Mac in the office

iOS and macOS builds require macOS hardware. Often a Mac mini under a desk takes that on, needing updates and blocking everything when it fails. The platform provides macOS machines for the pipeline. Interactive macOS workspaces you start yourself come next.

macOS machines in the pipeline for iOS and macOS builds
Connected directly to the GitLab CI pipeline
Signing credentials managed, releases to the App Store and Mac App Store

Start for free. No credit card required.

Work locally or in the cloud?

Entirely your call—we give you the ideal setup for both paths.

Local Setup app

Git & repos
Flutter SDK
Node.js
Docker

The setup app detects tools and starts everything with one click.

Cloud Remote workspace

Ubuntu VM
VS Code in browser
From anywhere

Ready-made dev environment—no local setup required.

macOS machines in the pipeline for iOS and macOS builds.

In short

The need for macOS does not go away, but the hardware does not have to sit in your office.

macOS in the pipeline: iOS and macOS builds run on the platform’s machines. Interactive macOS workspaces come next.
Wired into the pipeline: builds run on GitLab CI, with configuration readable in the repository.

Your own Mac hardware next to pipeline macOS machines

This describes the usual day-to-day with a dedicated build Mac compared with macOS machines from the platform.

Criterion	With the Application Platform	Your own Mac hardware
Availability for builds	Fully covered: Pipeline macOS machines are available for builds	Partly covered: One device, available while it happens to be running
Hardware failure	Fully covered: Another pipeline build machine takes over and the process stays the same	Not offered: Releases stop until somebody repairs the machine
Xcode and system maintenance	Fully covered: The environment is provided, no device to administer	Not offered: Updates, disk space and reboots handled by someone on the side
CI/CD integration	Fully covered: A fixed part of the project’s GitLab CI pipeline	Partly covered: Install, secure and update a runner yourself
Interactive access	Partly covered: Ubuntu workspaces over RDP and VNC. Interactive macOS workspaces come next	Partly covered: Physical access or remote control you set up yourself
Signing credentials	Fully covered: Apple credentials and other signing material managed centrally	Not offered: Certificates in the keychain of one particular machine
Parallel builds	Fully covered: Several pipeline build machines when multiple projects build at once	Not offered: Builds queue up one behind the other
Publishing to the stores	Fully covered: App Store and Mac App Store from the pipeline, with metadata and screenshots	Partly covered: Manual uploads or a Fastlane setup of your own
Developer ID and notarisation	Fully covered: Signing and notarisation for macOS applications are part of the flow	Partly covered: Rebuilt by hand and revalidated with every change
Access control	Fully covered: Roles and project membership decide who may trigger a pipeline build	Not offered: Effectively anyone who can reach the device

Green means covered, amber partly, grey not available. The right column describes no vendor but the usual situation with your own hardware.

As of 10 August 2026. This comparison describes typical workflows and can differ from project to project. Logos are trademarks of their owners and are used only to identify the product.

What cloud macOS changes day to day

Six things you notice from the first iOS release onwards.

No single point of failure

The release process no longer depends on one device someone has to leave switched on in the office.

Pipeline Macs instead of an office Mac

iOS builds run on the pipeline’s macOS machines. Ubuntu workspaces are reachable over RDP, VNC or VS Code in the browser; interactive macOS workspaces come next.

Anchored in the pipeline

Builds run on GitLab CI. The configuration is readable in the repository and can be adapted.

Signing managed centrally

Apple credentials, Android keystore and Azure Artifact Signing live in the platform rather than in a laptop keychain.

Store releases included

Releases go through Fastlane to the App Store and Mac App Store, with Developer ID signing and notarisation for macOS.

Ubuntu workspaces for daily work

For daily work you start Ubuntu workspaces with VS Code, JetBrains, RDP or VNC. Interactive macOS workspaces with Xcode come next.

Getting a macOS build machine

Four steps from project to signed build.

Create the project

Pick a Flutter, Expo or native iOS template. Repository, structure and pipeline are created with it.
Store your Apple credentials

Apple credentials and the matching store access are kept in the platform and released through roles.
Trigger the pipeline build

The pipeline builds and signs on the platform’s macOS machines. Interactive macOS workspaces over RDP or VNC come next.
Trigger build and release

The pipeline builds, signs and uploads. For macOS applications that includes Developer ID signing and notarisation.

Frequently asked questions

Do I still need my own Mac for iOS builds?

Not for pipeline builds. The platform provides macOS machines where the pipeline builds and signs. Interactive macOS workspaces you start yourself over RDP or VNC come next. Owning a Mac still helps for local work, but it is not required for the store upload.

Can I create a macOS workspace already?

Not yet. Under Workspaces you currently pick Ubuntu (Windows and macOS come next). iOS builds still run through the project pipeline on the platform's macOS machines.

Can macOS applications be published as well?

Yes. Alongside the Apple App Store, the Mac App Store can be served from the same project. For apps distributed outside the store, Developer ID signing and notarisation are part of the flow. Metadata lives in the editor, published through Fastlane.

Create an iOS project

Register for free, create an iOS project and run your first build on one of the platform's macOS machines. Interactive macOS workspaces come next.