Singapore, Tokyo, Seoul, Hong Kong, and the eastern United States. Keep interactive work close to your team and run builds on a dedicated physical Mac mini.
Both Mac configurations are available in all five locations. These aren't virtual machines: your entire machine is dedicated to you for the rental term. Choose a region based on your team's location, code repository, and artifact download route—without having to rethink your Mac configuration.
For frequent remote desktop use, prioritize round-trip latency. For CI workloads, focus on the paths to your repository, package sources, and artifact destination. The latency ranges below are guidance for comparing locations—not measurements of your current connection or a guarantee of performance.
A good fit for teams in Southeast Asia and distributed teams that want development and build work to happen within the same Asian workday.
Test dependency downloads and artifact uploads first, then decide whether to move your regular remote desktop work here too.
Rent in SingaporeWell suited to development and test teams working on Japan time. If you switch between Xcode and the simulator frequently, test the interactive experience first.
Use a complete pull, Archive, and download cycle as your benchmark—not just a ping test.
Rent in TokyoA good fit for teams working on Korea time. Use it as a daily development environment or dedicate it to automated builds and regression testing.
For collaborative work, test the desktop from the primary operator's network rather than using one teammate's connection as a proxy for the whole team.
Rent in SeoulA good fit for teams working primarily across South China and Southeast Asia. Consider it early if remote desktop responsiveness matters to your workflow.
Performance can vary across carriers and international routes. Test from your actual work network instead of relying on geographic distance.
Rent in Hong KongA good fit for teams in eastern North America, and worth comparing if key collaborators or artifact destinations are on either side of the Atlantic.
These ranges reflect networks near the eastern United States. Test access from Western Europe and Asia separately. The time difference shifts with daylight saving time.
Rent in the eastern USEach link preselects a location. Choose your Mac and rental term on the next step. Availability is confirmed in real time in the console.
Base M4 and Trunk M4 Pro are both available in all five locations. Use the table to compare Mac options and locations; it's not a live monitoring dashboard. Availability at checkout is confirmed in real time in the console.
| Mac | Singapore | Tokyo | Seoul | Hong Kong | Eastern US |
|---|---|---|---|---|---|
| Base M4M4 · 16GB RAM · 256GB SSD | Available | Available | Available | Available | Available |
| Trunk M4 ProM4 Pro · 64GB RAM · 2TB SSD | Available | Available | Available | Available | Available |
Choose a Mac based on compute and unified memory, then choose a location based on your network paths. A nearby node can improve remote interaction and data transfer, but it doesn't change the chip, memory, or SSD configuration.
Track the paths from the operator to the Mac, from the Mac to the repository, and from the Mac to the artifact destination. Desktop development and unattended CI have different bottlenecks, so you don't have to run every workload in the same region.
Teams in South China can start by comparing Hong Kong; teams in Southeast Asia can start with Singapore. International routing from mainland China varies considerably by carrier. Test SSH connectivity, VNC responsiveness, and artifact downloads over your usual work network. If CI rarely needs manual intervention, prioritize reliable transfers to your package sources and repositories.
Teams in Japan can start with Tokyo; teams in South Korea can start with Seoul. Both locations use UTC+9, making it easier to handle builds, log reviews, and handoffs within the same workday. For cross-region teams, consider both the primary developer's desktop experience and the time it takes to pull from your shared repository.
Start by evaluating the eastern United States, especially if your operators, repository, or artifact destination are in eastern North America. Test actual routes for West Coast or transatlantic access. If remote colleagues only need to review build results, keep coding locally and let a remote runner build to reduce desktop round trips.
For a useful comparison, run the same project at similar times and record cold-clone, cached-build, and artifact-download times. Note the network, cache state, and project version so a cache hit isn't mistaken for a faster node.
Each node has a dedicated public IP. Find the connection address, port, and login credentials in your instance details in the signed-in console. Don't infer them from public pages or example hostnames.
If you need to allowlist an address with a repository, artifact service, or firewall, wait until your node has been assigned. Recheck the connection details after a reinstall or a new order.
Connection guideThis page doesn't equate advertised bandwidth with download speed. Check your order and instance details for the bandwidth configuration. International routing, remote rate limits, and concurrent transfers all affect throughput.
For large projects, test dependency downloads, cache restores, and artifact uploads. Low latency doesn't guarantee fast bulk transfers, and access routes can vary between repository services.
Check your instanceYou can't switch an existing Mac to another region instantly. Place a new order in your target region, then migrate your project, cache, and required configuration after delivery.
Back up first, then validate the target environment. Update runner registration, connection details, and allowlists, and complete a build and artifact check. Once the new node is ready, arrange for the original node to expire.
Configure a locationEvery rental is a dedicated physical Mac mini. CPU, GPU, unified memory, and storage aren't shared with other customers. All five nodes operate year-round, 365 days a year, with the same isolation regardless of location.
Before moving source code or signing materials to a remote Mac, review access permissions, backups, and how data is handled at the end of your rental. See the security guide for details on isolation, data deletion, and availability compensation.
Base M4 starts at $20.3/day. Choose a location, Mac, and rental term, then confirm availability and the USD price in your order configuration before paying.
Payment is available only via USDT-TRC20 and Visa / Mastercard / Amex (through Stripe). Available payment gateways are confirmed by the backend.