A dedicated physical machine, not a VM, across 6 locations, $20.1/day
A dedicated Mac for your iOS team: check out code, archive, sign, and send builds to TestFlight.
SG
Tokyo JP
Seoul KR
Hong Kong HK
US East US-E
US West US-W
| Scheme | Version | Location | Duration | Signing |
|---|---|---|---|---|
| Ledger-iOSbuilt at 09:42 | 2.8.1 (412) | Singapore | 6m12s | Signed |
| Ledger-Widgetbuilt at 09:38 | 2.8.1 (412) | Singapore | 2m47s | Signed |
| Ledger-Watchbuilt at 09:21 | 2.8.1 (412) | Tokyo | 3m05s | Signed |
| Ledger-Betabuilt at 08:57 | 2.8.1 (411) | Hong Kong | 6m30s | Signed |
| Ledger-macOSbuilt at 23:10 | 2.8.0 (409) | US West | 7m02s | Signed |
** EXPORT SUCCEEDED **
Ledger-iOS.ipa · 48.2 MB
Uploaded to TestFlight
Ready to install for internal testing group “QA-Nightly”
TestFlight · Install confirmation
2.8.1 (412)Test notes: Fixed offline caching on the orders page and added dark mode for the widget.
Your runner is never shared with other customers. Your code, dependencies, and build cache stay on your own physical node.
The entire Mac mini is assigned to one customer. CPU, memory, and storage are never shared, so you don't have to wait for someone else's job to finish before archiving.
Keep SPM downloads, CocoaPods dependencies, and DerivedData on the machine by project. Cache hits depend on your branch, dependency versions, and build settings—so you don't have to rebuild the environment every time.
Need a machine for a release week? Rent the M4 for $54.2/week. For ongoing nightly builds, compare monthly and quarterly plans—no need to buy an office build machine upfront.
All four rental terms have published prices. Choose a term to fit your workload, then confirm the location, storage, and end date. Once your machine is ready, use your own scripts to schedule the build queue.
Singapore, Tokyo, Seoul, Hong Kong, US East, and US West. Both machine configurations are available in all 6 locations. Choose based on where your team and dependent services are.
For remote development, consider the interactive connection distance. For automated builds, also consider the routes to your repository and artifact storage. Locations run 365 days a year, making them a reliable home for scheduled archives.
From $20.1/day. Choose M4 for a single-app archive; consider M4 Pro for multiple targets, parallel tests, or inference.
A great starting point for one app with 1–3 archives a day. Set up your source code, Xcode, and commonly used dependencies, then decide if you need extra SSD storage.
Room to run multiple targets, UI tests, and MLX experiments. The number of parallel jobs depends on your project's peak memory use and test workload—run a test build before increasing concurrency.
All prices are in USD. Check the console for live location availability, and confirm your rental term, add-ons, and order total before paying.
From push to TestFlight, keep the tools you already use. Here’s a five-step Ledger-iOS handoff; timings are illustrative.
Push your branch after committing locally. Your configured CI triggers the build.
git push origin release/2.8.1
Pin the commit so branch changes don't cause a mismatch between the archive and release records.
git fetch origin release/2.8.1 && git checkout --detach FETCH_HEAD
Set the Scheme, Release configuration, and archive path. Logs are saved with the build artifacts.
xcodebuild -scheme Ledger-iOS -configuration Release -destination 'generic/platform=iOS' -archivePath build/Ledger.xcarchive archive
Prepare your certificate and provisioning profile, then specify signing and distribution in the export configuration.
xcodebuild -exportArchive -archivePath build/Ledger.xcarchive -exportOptionsPlist Export.plist -exportPath build/export
Set up distribution credentials, upload the IPA, and make the build available to your testing group.
fastlane pilot upload --ipa build/export/Ledger-iOS.ipa --api_key_path asc-key.json
Your team configures this workflow; renting a machine doesn't automatically connect it to your repository. First, align your Xcode version, dependency lockfile, and signing setup. Then register a GitHub Actions self-hosted runner, GitLab Runner, or Jenkins agent. Project size, caching, and network conditions all affect build time.
Start with your team's time zone, then consider the connection route to each location. Latencies below are regional reference ranges, not measurements for every city.
Southeast Asia
A good fit for teams in Southeast Asia: work during the day, then run archive and distribution jobs overnight.
Order a Singapore nodeEast Asia
A good fit for teams working in East Asia time zones, with development, testing, and nightly handoffs scheduled around the same hours.
Order a Tokyo nodeNortheast Asia
A good fit for teams collaborating across Northeast Asia, with remote development and build troubleshooting during the same workday.
Order a Seoul nodeSouthern China and Southeast Asia
A good fit for teams on UTC+8. Actual connection quality also depends on your local provider and network routing.
Order a Hong Kong nodeEastern North America and Western Europe
A good fit for teams in eastern North America and Western Europe. Schedule archives before handoff so colleagues in the next time zone can pick up logs and test builds.
Order a US East nodeUS West Coast
A good fit for teams working on the US West Coast. Consider repository checkouts, dependency downloads, and artifact uploads together—not just the feel of a remote desktop.
Order a US West nodeTime zones are for collaboration planning; some regions adjust seasonally. Actual latency depends on your location, provider, and network route. Check the console for live location availability.
Be specific about what you need to build, and you'll know whether renting a machine makes sense. Here are three example handoffs for different workflows.
We moved our nightly builds from a teammate’s MacBook to a Tokyo node. By the time we get to work, the IPA is already in TestFlight.
Fastlane and UI tests pass in one go on an M4 Pro with 64GB—no more waiting in line for a shared runner.
I run inference experiments with a 7B model locally, rent by the week, then stop. The bill is easy to understand.
Choose your machine and rental term, then check the payment gateway shown at checkout. Manage billing and your machine in the console.
All payments are in USD. Available gateways are confirmed at checkout. Stripe processes card numbers; this site does not store them. After paying, view your order, delivery status, invoices, and renewal options in the console. You can also submit a support ticket there.
DerivedData, SPM caches, and simulator images can quickly use up disk space. Decide what can be regenerated and what archives you need to keep before choosing how much storage to add.
An external SSD works well for build caches and large assets. Before your rental ends, sync any source code, archives, and logs you need to keep to your own storage. Don't rely on an expansion drive as your only backup.
View add-on pricingDerivedData and SPM caches
Multiple simulator versions and archive storage
For multiple M4 Pro machines, confirm the topology and job assignments first
Practical guides to distribution, remote environments, and signing. Run the workflow once, then automate the steps you repeat.
Define XML import boundaries with an executable Swift guard, then test DTD rejection, namespaces and resource limits using fixed fixtures.
DevOps & CI/CDImplement SemVer comparison without integer conversion, exercise malformed input and prerelease ordering, and keep upgrade policy separate from version precedence.
DevOps & CI/CDExtract geofence decisions into testable logic, then check distance calculations, accuracy filtering and separate entry and exit thresholds without live location.
New posts are in the works. In the meantime, browse the blog.
Let's clarify the machine, toolchain, and data handoff first.
It's a dedicated physical Mac mini, not a VM. CPU, memory, storage, and build caches aren't shared with other customers. The macOS desktop and command line are fully available; your team still configures its own project dependencies, signing assets, and CI jobs.
Rent by the day, with the M4 from $20.1/day and the M4 Pro from $60.3/day. You can also choose a week, month, or quarter. Rent by the day for a short toolchain test, weekly for a release push, or monthly or quarterly for ongoing nightly builds. Check the term, amount, and end date on your order before paying.
You can register a self-hosted runner or GitLab Runner on the machine, or connect a Jenkins agent. Pin your Xcode version and dependencies first, then configure your Fastlane lane. Assign runner tags only to the build jobs that should use the machine, so concurrent archives don't compete for the same directory. See Connect to your machine for connection and migration steps.
You'll need to configure your project and signing first. Set up the Scheme, certificates, provisioning profiles, and Export.plist. For uploads, you can use an App Store Connect API Key. Never commit a .p12 file, private key, or API Key to a public repository. Run archive and export manually first, then add automation to make troubleshooting easier.
When the machine is reclaimed, its disk is securely erased and the system is reinstalled before it goes to the next customer. Before your rental ends, export any archives, artifacts, and logs you need, remove certificates and CI credentials, and revoke access you no longer use. If you need more time, check your renewal options and order status in the console. Don't use a build node as your only storage.
Submit a ticket through the console with your order number, location, Xcode version, reproduction command, and the last 50 lines of the log. Say whether the issue is an SSH connection, dependency download, compilation, or signing failure, and note what changed most recently. Remove tokens, private keys, and passwords from logs. You can also email support@osxbuild.com.
Choose a configuration and location. Once your machine is ready, connect over SSH and run your first archive. Let your release workflow take it from there—no more waiting for a free Mac.