Rent for your project
A remote macOS environment for developers in East Asia. Build your project on Windows or Linux, then use a cloud Mac to compile and export your iOS app.
From $19.9/day. Pay in advance by the day, week, month, or quarter. Service stops when your term ends unless you renew.
Choose for your workload
Both options are dedicated Apple Silicon Mac mini physical machines—not virtual machines—and CPU and memory are not shared with other users.
M4 / 16GB / 256GB SSD
For routine iOS builds with Flutter or React Native, or moving an existing project to macOS for build verification.
Check how much space your dependencies, project, and build cache need. If you keep multiple archives, include their storage requirements when choosing a configuration.
M4 Pro / 64GB / 2TB SSD
For Xcode projects exported from Unity, large asset builds, or workloads that need several development tools running at once.
64GB of unified memory and a 2TB SSD give you more room for demanding workloads. Actual build times still depend on project size, dependencies, and build settings.
Just checking your build process? Start with daily billing. For ongoing development and delivery, compare weekly and monthly billing. For a dedicated build machine or continuous integration, check the quarterly rate. Each term is priced independently in the table above; don't calculate another term by multiplying the daily rate.
Before ordering, confirm the Mac, node, billing term, and expiry date. Add-ons such as extra storage are priced separately during setup. Check your order summary before paying.
Check your connection
The Tokyo node serves East Asia, with a reference round-trip range of 30~60ms. This is a regional guide, not a live measurement of your connection's average latency.
If you work in Xcode's graphical interface, round-trip latency and jitter can both affect responsiveness. On your first connection, check input, window switching, and screen updates at your usual resolution.
If the desktop feels sluggish, lower the resolution and check local network usage.
A smooth remote desktop doesn't necessarily mean faster compilation. When you build over SSH, the task runs on the physical node without continuously streaming the desktop.
Save command output to a log to help identify failures and reproduce issues.
Uploading a project and downloading archives also depend on bandwidth, routing, and file count. Round-trip latency doesn't predict transfer speed, and the reference range is not a bandwidth guarantee.
Transfer only the source files and assets you need. Avoid re-uploading caches that can be regenerated.
Reference range only; actual results depend on your network. Nodes operate year-round, 365 days a year. The 99.9% figure is a service availability commitment, not a guarantee of your local network quality. See the plans page for details.
Allow time to get set up
The times below are estimates for user actions, not service activation statistics. Payment confirmation, provisioning, and project transfer each depend on their actual status; no fixed number of minutes is promised.
Choose a Mac, term, and node, then review add-ons and the total. Have your project requirements and estimated usage period ready to avoid last-minute changes.
Estimated time: 3–5 minutes
Prices are charged in USD. Pay with USDT-TRC20 or Visa / Mastercard / Amex (via Stripe). Use the payment option available at checkout.
Estimated time: 2–5 minutes; confirmation time varies
Once your service is activated that day, check the instance status and connection details in the console. Verify the address, port, and credentials. Never put connection details in a code repository or public screenshot.
Activation: same day; check instance status
In macOS, check toolchain versions, disk space, and project dependencies before uploading your project. Run a small build to verify the process, then start the full archive job.
Connection checks: 5–10 minutes; transfers and builds take longer
Before paying, prepare your source-code access, project dependency notes, and any required signing materials. After your build, download the output and back up your project before deciding whether to renew.
Confirm your node choice
Choose based on how you work, not just where you are. If you mainly submit builds over SSH, focus on project transfers and dependency downloads. If you'll spend long periods using the graphical desktop, consider the actual round-trip latency and jitter between your network and the node. The 30~60ms figure is a reference for East Asia only; it may not apply to other regions.
Both Mac options on this page are available at this node. XcodeHost M4 comes with M4 / 16GB / 256GB SSD; the Pro option comes with M4 Pro / 64GB / 2TB SSD. Base prices for each term are listed above. Choosing a location won't switch you to a different configuration. Add-ons are priced separately, and availability is shown live in the console.
Plan for a redeployment rather than an instant move of a running instance. Export your project, build settings, and required materials, then restore dependencies and verify your build on the new instance. If you need to change an existing order, submit a support ticket through the console to confirm the available options. Don't assume data will transfer automatically or that the remaining term will be credited automatically.
Choose a configuration and term, then check the node and expiry date before paying.