Once your code is ready on Windows or Linux, choose a cloud Mac near you from 5 locations. If you’ll be using Xcode interactively, prioritize connection distance. If you’ll mostly be waiting for builds, consider both the code upload and artifact download paths.
Available only in Singapore, Tokyo, Seoul, Hong Kong, and the US East. Starting at $19.2/day, subject to real-time availability shown in the console.
All 3 tiers are available at every location. Start with the coverage area, then consider your own network. A node’s location doesn’t guarantee connection quality from where you are.
Coverage: Southeast Asia. A good fit for desktop work, checking archive results, or pulling code and building in the same location.
Reference round-trip latency: 20–50 ms
Starting at $19.2/day
Coverage: East Asia. Consider this location if you’ll repeatedly check Xcode settings in a browser, run Archive, and review build logs.
Reference round-trip latency: 30–60 ms
Starting at $19.2/day
Coverage: Northeast Asia. Try remote desktop over your local network, then handle interactive work and builds on the same machine.
Reference round-trip latency: 30–50 ms
Starting at $19.2/day
Coverage: Southern China and Southeast Asia. A nearby option for interactive work, but cross-network routing can still affect responsiveness and transfers.
Reference round-trip latency: 20–40 ms
Starting at $19.2/day
Coverage: Eastern North America and Western Europe. Intended for users and teams in these regions; the ranges below don’t apply to connections from Asia-Pacific.
Reference round-trip latency: 25–35 ms
Starting at $19.2/day
“Plenty available” is a catalog indicator, not a live inventory snapshot. Check real-time availability in the console when ordering. Selecting a location only updates this page’s rental link; it won’t create an order or charge you. You can also use the rental button on any card.
These ranges show reference latency between a node and its coverage area; they aren’t results from tests in every city. They can’t predict Archive time, download speeds, frame rates, or the delay for each mouse action.
| Node | Coverage | Reference round-trip latency | Recommended workflow |
|---|---|---|---|
| Singapore | Southeast Asia | 20–50 ms | Remote desktop work, builds, and file transfers within the region |
| Tokyo | East Asia | 30–60 ms | Interactive Xcode work, archiving, and build result checks |
| Seoul | Northeast Asia | 30–50 ms | Remote desktop debugging, builds, and log checks |
| Hong Kong | Southern China and Southeast Asia | 20–40 ms | Nearby desktop work, uploading projects, and retrieving build artifacts |
| US East | Eastern North America and Western Europe | 25–35 ms | Desktop work, builds, and file transfers for users in the coverage area |
Performance may vary by provider and time of day, even for the same node. Remote desktop lag can also depend on bandwidth, packet loss, display settings, and your local device. A different machine tier won’t shorten the network route.
Mouse input, build time, and file transfers follow different paths, even for the same iOS release. Choose based on the step that happens most often or has the biggest impact—not just the lowest number in the table.
If you’ll be opening Xcode settings, checking signing, viewing the simulator, or reading error messages, start with the coverage area that includes your city and choose a nearby node.
Your location is only a starting point. Cross-network routing can make a farther node perform better than expected. Treat the reference ranges as estimates, not a guarantee for your connection.
If your main tasks are Flutter builds, React Native archives, or compiling Unity exports, you can be more flexible about node distance. Make sure you can set up the SDK, dependencies, certificates, and provisioning profiles during your rental.
Build time also depends on project size, caching, and machine tier. Lower network latency doesn’t mean the same project will build sooner.
For large Unity assets, dependencies, or build artifacts, consider each route: your device to the node, your repository to the node, and the node to the artifact destination. Base your choice on the files you need to transfer—not on latency as a proxy for bandwidth.
Use Git where possible for reproducible code and dependency instructions. For large files, transfer them over SSH or another suitable method for your connection. Don’t assume browser-based remote desktop supports drag-and-drop file transfers.
After activating your machine, sign in to the console, open browser-based remote desktop from the instance details, and check responsiveness. Then pull your project, install dependencies, and run a build check.
If things feel slow, identify whether the issue is desktop responsiveness, file transfer, or compilation. Note when it happened and how to reproduce it, then adjust your connection method or submit a support ticket.
A node is where a machine is located—not a shared folder that syncs projects automatically. Teams can rent a dedicated physical machine at different locations; orders and billing are listed per machine. Code, dependencies, and signing materials must be prepared separately for each copy of a project.
Choose a location based on who will actually use remote desktop. If multiple people need to build at the same time, arrange separate machines and rental periods. One dedicated physical machine is not multiple independent build environments.
Use a commit ID, toolchain version, and artifact name to make handoffs clear and avoid mixing up build results from different nodes.
Set up each machine separatelySelecting a node on this page only sets the location for a new order; it won’t change an existing instance. Sign in to the console and submit a support ticket to confirm whether an existing order can be moved and how the rental period and charges would be handled.
Don’t assume a move can happen in place without data loss. Back up your project, export any required settings, and record dependency versions before following the confirmed process.
Sign in to the console and submit a ticketDownload your artifacts and save the setup notes you’ll need to recreate the environment before your rental ends. If you need more time, confirm an extension in the console in advance. Don’t rely on disk data remaining available after expiration.
Import certificates, provisioning profiles, and other sensitive materials only on machines that need them. When handing off or finishing, check for local copies and any remaining files on the machine.
You’re responsible for backups and handoffsAll locations are billed in US dollars (USD). We accept USDT-TRC20 and Visa, Mastercard, or Amex through Stripe. Available payment gateways are confirmed by the backend; payment confirmation times depend on blockchain confirmations or your card issuer.
At checkout, confirm the machine tier, rental period, and configuration. After signing in, open the macOS remote desktop in your browser—no separate client needed. Clipboard and file transfer capabilities depend on your connection method.
Current selection: Singapore. This location will be preselected at checkout.