Start with your team's location
Singapore, Tokyo, Seoul, Hong Kong and the US West Coast—all with availability.
Start with the nearest node for team members who work at the desktop regularly, then factor in the path for builds and file transfers. You get a dedicated physical Mac mini, not a virtual machine. Actual connection quality depends on your location, ISP and network access.
Same price across all 5 nodes, from $21.8/day. Check the portal for real-time availability when you place your order.
Node directory
Use the coverage areas below to narrow down your options. They don't guarantee a specific route or connection latency. Both plans are available in all 5 locations. Choose a node first, then pick a configuration based on your project's memory and storage needs.
Coverage: Southeast Asia
Keep day-to-day desktop work and builds close to your Southeast Asia team. When handing work across time zones, check that the previous shift's tasks are complete before taking over on the same machine.
Coverage: Japan and East Asia
Keep desktop tasks involving frequent clicks, scrolling and previews close to your team in Japan. Tokyo may also suit teams elsewhere in East Asia; check how your own network performs.
Coverage: South Korea and Northeast Asia
Give team members in South Korea a nearby node for macOS graphical work. Seoul and Tokyo share a time zone, but that doesn't mean their network routes will perform the same way.
Coverage: South China, Hong Kong, Macau and Taiwan
Consider Hong Kong for teams in South China, Hong Kong, Macau and Taiwan with graphical workloads. If you're connecting from mainland China, check your local ISP and cross-border network conditions—geographic proximity doesn't guarantee low latency.
Coverage: North America's West Coast
Keep desktop work and regression testing close to your team on the North American West Coast. When handing work to an Asia-Pacific team, record the date as well as the time to avoid confusion across day boundaries.
Local times are based on your device clock and update every minute. US West time automatically accounts for daylight saving time. The clock doesn't monitor node status; check the portal for real-time availability.
Assessing connectivity
We don't have a verified round-trip latency range to cite for these nodes. The guidance below is based on coverage and workload—not sample ping times or assumed distances.
| Node | Coverage | Best for | What to check |
|---|---|---|---|
| Singapore | Southeast Asia | Remote desktop, builds, file transfers | Desktop responsiveness for your Southeast Asia team, plus the routes used to fetch projects and download build artifacts. |
| Japan (Tokyo) | Japan and East Asia | Remote desktop, builds, file transfers | Keyboard and mouse responsiveness for team members in Japan and East Asia, and the reliability of dependency downloads. |
| South Korea (Seoul) | South Korea and Northeast Asia | Remote desktop, builds, file transfers | Interaction quality for team members in South Korea and Northeast Asia, and any interruptions during file transfers. |
| Hong Kong | South China, Hong Kong, Macau and Taiwan | Remote desktop, builds, file transfers | Network performance during your primary users' normal working hours—not just the result of a single round-trip test. |
| US West Coast | North America's West Coast | Remote desktop, builds, file transfers | Desktop responsiveness for your West Coast team, plus the route used to hand artifacts off to Asia-Pacific. |
Actual performance depends on your network. Lag can also come from your local connection, video streaming or the workload on the machine. A single round-trip test can't tell you which is responsible.
Choose based on your workload
First, identify who uses the desktop every day, then choose a node near them. Browser-based remote desktop requires a modern browser and a stable connection. Tasks involving frequent dragging, scrolling and visual review are more sensitive to interruptions.
Work out who uploads and downloads the code, dependencies and build artifacts, then choose a node near the majority of your team. You can use SSH for command-line builds; desktop responsiveness and compile speed are separate considerations.
If your team spans Asia-Pacific and the US West Coast and both groups need regular desktop access, you can rent one machine in each region. Each instance is billed separately and stores its own data. Keep work in sync through your code repository and artifact handoffs; files don't sync automatically.
Example team setups
These examples illustrate how to choose a node; they aren't customer stories or latency tests. Start with team locations and workloads, then decide whether one shared machine is enough or you need an instance in each region.
Consider Hong Kong or Singapore. If the primary desktop users are in South China, start with Hong Kong. If most builds and artifact handling happen in Southeast Asia, start with Singapore. In either case, check the actual network connection.
Consider Tokyo or Seoul. Both locations share a time zone, so start with the primary users and agree on a schedule for the shared desktop. A dedicated machine is assigned to one customer; multiple team members using it at the same time can still get in each other's way.
Consider US West for a closer connection. Before handing over, the Asia-Pacific team should commit its code and record whether the task is complete. The US West Coast team can verify the version before running regression tests. If you rent another machine, align the toolchain and dependencies first.
Before you order
Only the 5 nodes listed here are available. Changing the region option won't move an existing instance. To switch nodes, create a new instance in your target region from the portal, then migrate your project and toolchain.
Take stock of your project repository, uncommitted files, signing certificates, provisioning profiles and dependency versions. Note any tasks running on the original machine to avoid duplicate builds or missing artifacts during migration. Both instances are billed while they're in use.
Match the Xcode and dependency versions on the target instance, then run a project build. If you use CI, register the build machine again and verify a job. Once desktop access and file paths are working, let your team know to update its connection details and handoff notes.
Same plans in every region
UDP M4 16 comes with M4 / 16GB / 256GB SSD for $21.8/day. UDP M4 24 comes with M4 / 24GB / 512GB SSD for $40.9/day. Choose from 4 billing periods: day, week, month or quarter. Billing starts once payment is complete.
Payments are accepted via USDT-TRC20 and Visa / Mastercard / Amex (through Stripe), and are charged in USD. Available payment gateways are confirmed by the backend at checkout.
Start with your team's primary work location, then choose a configuration and billing period. Before working across regions, get your tool versions and handoff notes in order.