Test a build
Build a test release or check whether your project builds with the target toolchain.
M4 Pro $59/day
Mac development workstations · for Flutter, React Native and Unity developers
Keep developing on the computer you know; move only the macOS-dependent build steps to the cloud.
Plan around your project
Choose a rental term that fits your project. Pick one of four options when you order.
Build a test release or check whether your project builds with the target toolchain.
Run integration tests for contract work, and handle signing checks and fixes in one environment.
Keep dependencies and build files during development to avoid setting up the build environment again.
Configure a self-hosted runner for continuous delivery and fit the build environment into your team’s workflow.
Service stops at expiry unless renewed. No long-term contract.
Estimate the time needed for compilation, device testing and fixes before choosing a term. A one-off build check and ongoing team builds are different use cases; don’t base the full rental period only on the first Archive.
Get connected
Choose your configuration and start building in three steps.
Choose a model, location and rental term. Check the total, then pay.
Check the live status in your console. Before connecting, prepare a list of project dependencies so you have the files you need to build.
Once your Mac is ready, find its address, port and login credentials, and check the order they belong to.
Save your order details in the console. If you have connection issues, open a support ticket for that order. Never put passwords, private keys or signing assets in public logs.
Use VNC for the desktop and SSH to run xcodebuild. Set up dependencies as your project requires.
Check the macOS, Xcode and command-line tools versions, then restore project dependencies. When the build finishes, copy the artifacts and any necessary logs to your own storage.
Check the hardware
For large Unity projects or multiple simulators running in parallel, consider the M4 Pro configuration.
Entry-level XcodeHost M4: M4 / 16GB / 256GB SSD
Memory needs to accommodate build processes, your editor and simulators. Storage also needs room for dependency caches, build files and exported artifacts. Check your project’s actual usage before choosing; the chip model alone doesn’t guarantee build times.
Start with your framework
You don’t have to move your entire development workflow. Connect only the part that depends on a Mac.
Write your app on Windows, check the toolchain on your Mac, restore dependencies, then run flutter build ipa.
Run project diagnostics first to distinguish SDK, native plugin and signing configuration issues. After a successful build, check that the app installs and runs—don’t rely on the command’s exit code alone.
On a remote macOS environment, run pod install, compile native dependencies, then archive and export.
Keep the project’s dependency lockfile, and check the Node, Ruby and CocoaPods versions. If Hermes or a native module fails, start with the relevant build log.
Export an Xcode project on Windows, upload it, then build on a Mac, check signing and export a test build.
Check the Unity iOS Build Support module, export settings and plugin dependencies. For large projects, check space for the project and intermediate files before choosing a configuration.
Compare USD prices
Two configurations, four rental terms. Compare specs, then choose the term that fits your project.
M4 · 16GB unified memory · 256GB SSD
For standard iOS builds, checking native dependencies and short-term testing. Before you start, make sure the project, caches and exported files fit in the selected storage.
| Daily | $19.9/day |
|---|---|
| Weekly | $53.8/week |
| Monthly | $99.7/month |
| Quarterly | $271.2/quarter |
M4 Pro · 64GB unified memory · 2TB SSD
For projects that need more memory and storage. Consider this configuration for large Unity assets, multiple simulators or larger build caches.
| Daily | $59/day |
|---|---|
| Weekly | $159.4/week |
| Monthly | $295.1/month |
| Quarterly | $802.7/quarter |
Prices are for the listed model and rental term. See the plans page for additional storage and Thunderbolt 5 linking options. Check the configuration, total and expiry date when you order, and keep a separate backup of your project.
Choose a location
Start with the location that works best for the primary user, then consider upload and download routes for your project and build artifacts.
Choose from 5 locations. Click to open the order page with your location preselected. Check live availability in your console.
Every machine is a dedicated physical machine, not a virtual machine. CPU and memory are not shared with other users.
Full macOS desktop and command-line access. A dedicated machine doesn’t replace access controls: keep credentials secure and configure access to suit your project.
Locations operate year-round, 365 days a year, with a 99.9% uptime commitment.
Based on 30 days, this is about 43 minutes of downtime. Beyond that allowance, service time is credited in proportion to the affected period. Submit a support ticket with your order number and the affected time range.
Only these two payment methods are supported. Check the backend response for currently available payment gateways. If you have a payment issue, keep your order number and transaction record, and never send your full card number.
The details that matter
You can keep writing app code on Windows or Linux. Run Xcode builds, archives and exports for iOS on a cloud Mac; you’ll still need to configure the toolchain, dependencies and signing assets for your project.
Prepare a valid certificate, private key and provisioning profile for your distribution method. Check the Bundle ID and target devices. Upload only assets your current project needs, then export a backup and remove them when you’re done.
No. You can sync just the project files and assets needed for the build. Include the dependency lockfile to avoid restoring different versions. Local caches and unrelated large files don’t need to be uploaded.
Use VNC for the desktop and SSH to run commands repeatedly. Desktop responsiveness depends on your network; you can run continuous builds from the command line. See the user guide.
You can configure a self-hosted runner on your machine. First verify a manual build, then enable automated triggers. Your team manages build credentials, repository permissions and artifact retention.
The machine stops at expiry, and data is cleared as described in the service terms. Retrieve your project, certificates, build artifacts and necessary logs before expiry. Don’t rely on an expired machine as accessible storage.
Consider your project size, peak memory usage and tools running at the same time. The M4 may suit routine checks; consider the M4 Pro for larger assets and parallel tasks. Actual build times depend on your project, dependencies and build settings.
Sign in to the console and open a support ticket with your order number, when the issue occurred, tool versions and error logs with sensitive information removed. For presales questions or email support, contact support@xcodehost.com.
Keep up with the latest
Find guidance for your project, check tool versions first, then follow the steps.
Build a runnable Swift harness for request-signing bytes, reference vectors and tampering cases, then define what the server must do to prevent replay.
SecurityRun a Swift script against reference vectors, leading zeros, and time-step boundaries, then separate client generation from server replay prevention.
SecurityRun known-answer tests with Swift and CommonCrypto, check password byte boundaries, and define a migration contract for salts and work factors.
New articles are in the works. Browse the blog for now.
Get started with XcodeHost M4 from $19.9/day. Choose a rental term and check the expiry date.