A dedicated physical Mac, not a virtual machine. 5 locations, with daily, weekly, monthly, or quarterly billing. From $21.1/day.
Start with one machine and connect it to your build pipeline the same day. Check the dashboard for current availability and delivery details.
Sample workflow, not live dataBuild times vary by project, dependencies, and cache
An iOS build machine should be reliable, reproducible, and ready when you need it. After signing in, check the hardware, access, and toolchain, then connect your first pipeline.
The entire Mac mini is yours. CPU, unified memory, and SSD are not shared with other tenants, split, or oversold. Your build cache stays on your machine, so there’s no need to set up the environment again for every job.
1 machine = 1 tenant
Xcode, Simulator, and Metal run natively on macOS. Use the graphical interface or command line, without working around virtualized-device restrictions. Check the hardware details yourself to confirm the Mac mini model.
system_profiler SPHardwareDataType
Rent for a day to check dependencies and signing; choose a week for a release push, or a month or quarter for a long-running runner. Each period has its own price—monthly rates aren’t converted into a misleading daily entry price.
M4 Base: $21.1/day · $57.1/week · $105.7/month
Every model is an Apple Silicon Mac mini. All three are available at all 5 locations, with memory and SSD fixed by model. Add extra workspace separately if you need it.
ID m4-16-256
Dedicated physical Mac mini
ID m4-24-512
Dedicated physical Mac mini
ID m4pro-64-2tb
Dedicated physical Mac mini
Add +1TB / +2TB SSD storage and Thunderbolt 5 daisy-chaining. Confirm network details, toolchain versions, and delivery configuration when placing and activating your order.
Full specs and add-onsAll prices are in USD. Switch each card independently between daily, weekly, monthly, and quarterly billing. The price shown is the full base charge for that period, not a daily equivalent.
M4 · 16GB · 256GB
$21.1/day
Best for a single-scheme project or a short-term trial. Track full build time, cache use, and peak memory before deciding whether to scale up.
M4 · 24GB · 512GB
$41.4/day
For teams building up dependency caches and switching between multiple schemes. When you need to build several apps at once, spread jobs across multiple machines rather than treating a serial queue as parallel.
M4 Pro · 64GB · 2TB
$59.5/day
Built for full builds of large projects, Simulator testing, and local model inference. 64GB of unified memory and a 2TB SSD leave room for multiple dependency sets and build artifacts.
From $21.1/day; +1TB SSD from $3/day. Add-ons are billed separately. Check the model, billing period, location, and total before checkout.
Rates and add-onsRegister 1 to N Cloud Macs as self-hosted runners for GitLab or GitHub Actions. Get one pipeline running, then distribute multiple schemes across different machines.
Use the same commit to record clean and incremental build times. Check certificates, dependency downloads, and DerivedData usage. Start with one job at a time per runner.
Choose labels based on macOS version, Xcode version, and project use. Matrix jobs can run across hosts only when multiple runners with matching labels are available.
Choose and retain the Xcode version your project requires. Set it with DEVELOPER_DIR, and give archives and caches separate paths to prevent jobs from overwriting one another.
Pinning the Xcode version alone doesn’t make a build reproducible. Track dependency lockfiles, signing assets, export settings, and environment variables in your team’s change history too.
name: ios-nightly
on:
workflow_dispatch:
schedule:
- cron: "0 13 * * *"
jobs:
archive:
runs-on: [self-hosted, macOS, xcode-16.2]
strategy:
fail-fast: false
matrix:
scheme: [App-Prod, App-Staging, Widget]
env:
DEVELOPER_DIR: /Applications/Xcode-16.2.app/Contents/Developer
steps:
- uses: actions/checkout@v4
- name: Archive
run: |
xcodebuild archive \
-workspace App.xcworkspace \
-scheme "${{ matrix.scheme }}" \
-configuration Release \
-archivePath "build/${{ matrix.scheme }}.xcarchive"
- name: Export
run: |
xcodebuild -exportArchive \
-archivePath "build/${{ matrix.scheme }}.xcarchive" \
-exportPath "build/export/${{ matrix.scheme }}" \
-exportOptionsPlist ci/export.plistReplace the workspace, scheme, and Xcode path with your project’s settings. GitLab also assigns jobs using runner labels. Manage certificates and keys with protected variables or a dedicated keychain; don’t commit them to your repository.
Singapore, Tokyo, Seoul, Hong Kong, and the US West Coast, with all three models available at every location. Start with where your team and repositories are, then check the actual network path.
Southeast Asia
East Asia
Northeast Asia
South China and Southeast Asia
North America West
Latency ranges are location references, not measurements from your network. SSH transfers, repository fetches, and VNC sessions each depend on their own network path. US West Coast time changes with daylight saving time. All locations operate year-round, 365 days a year; check the dashboard for current availability.
Use SSH for scripts and CI, and VNC screen sharing for Xcode and Simulator. Find your host address and credentials in the dashboard, then configure your client using the connection guide.
Install dependencies, register runners, and view build logs. Change your password and add a public key after your first login. Once you’ve verified the key works, adjust your authentication settings.
ssh -i ~/.ssh/armrdp admin@<host>Check Xcode settings, Keychain, and Simulator. For a more secure connection, use an SSH tunnel to forward a local port to the host’s screen-sharing service.
ssh -N -L 5901:localhost:5900 admin@<host>GUI and automation jobs use the same project files and toolchain, so there’s no need to copy build directories between environments.
Install dependencies, run archives, inspect logs and artifacts
Project settings, Simulator, signing, and UI debugging
vnc://localhost:5901These first-person examples show how different roles might plan their machines. They illustrate use cases—not customer testimonials or performance figures.
“During release week, I want each of our three schemes to have its own archive path. If jobs can go to different runners, I don’t have to keep watching one queue.”
iOS lead · Example requirement
“I want to pin the Xcode version and dependency lockfile together. I’ll check the result against the same commit first, then add this Mac to the production pipeline.”
CI/CD engineer · Example requirement
“I’ll rent an M4 Base for a day to get certificates and a GitLab runner working. Once I know what the project actually uses, I can choose a longer rental period.”
Independent developer · Example requirement
No. You get a dedicated physical Mac mini. During your rental, its hardware resources aren’t shared with other tenants. Check the chip, memory, and storage in System Information.
Yes. Install and retain multiple versions as your projects require. Point build scripts to a specific version with DEVELOPER_DIR, or switch with xcode-select. Check macOS compatibility and available disk space first.
Start with one machine running a single job. Record peak memory, archive time, and disk I/O, then decide whether to add concurrency on the same machine or bring in another. The number of schemes alone won’t tell you how long a build will take.
Store certificates in a dedicated keychain and keep sensitive variables in your CI system’s protected settings. Sync archives and exported artifacts to your own storage. Back them up and revoke any access credentials you no longer need before your rental ends.
Use a runnable Swift script to test escaped keys, array indices, and resolution errors while keeping missing fields distinct from valid null values.
DevOps & CI/CDKeep displayed percentages at an exact total with integer allocation, deterministic tie-breaking and executable Swift boundary checks.
SecurityRun a Swift script that rejects invalid characters, noncanonical trailing bits, and oversized unpadded Base64URL input.
New posts are in the works. In the meantime, browse the blog.
Choose your rental period and configuration, then review the order total. Base rental charges and add-ons are listed separately. Available payment gateways are confirmed by the backend.
Before paying on-chain, check the network and payment details. For card payments, follow the gateway’s checkout page. If your payment hasn’t been confirmed, check the order before trying again to avoid creating a duplicate payment.
M4 Base from $21.1/day. Start with one project and one runner, then grow your iOS build farm once everything’s working.
The timeline, runner, and queue show an example workflow, not live system data. Before ordering, check the dashboard for configuration, billing period, and delivery details. Build times depend on your project, toolchain, and cache.