For teams in South China & Southeast Asia, run iOS builds and remote development on a dedicated physical Mac. No virtual machine: you get the full macOS desktop and command line. Start by getting one pipeline running, then decide whether to add more nodes.
Three configurations, four billing periods, from $21.1/day. Check the console for real-time availability.
All three options are dedicated physical nodes. Memory determines how much build and test work you can run; SSD capacity sets the space available for repositories, toolchains, and caches. Choose based on peak usage per build, not just how many builds you run each day.
Daily pricing is highlighted. Confirm your billing period and node on the configuration page when you order.
For validating your first iOS pipeline, archiving from scripts, and lighter development work. Start with one runner handling jobs sequentially, then monitor memory and cache growth.
$21.1/day
Allow for macOS, Xcode, and dependencies first, then estimate the space needed for DerivedData and retained archives.
For projects with a persistent runner, multiple dependency sets, or larger build caches. More unified memory and local storage than the entry-level configuration.
$41.4/day
Queue jobs across multiple schemes to start; use peak resource usage and task duration to decide whether to add concurrency.
For larger projects, simulator test suites, and local model inference. 64GB of unified memory and a 2TB SSD provide extra room for demanding workloads.
$59.5/day
More memory and storage do not mean unlimited concurrency. Test a real workload first, then increase the number of simultaneous jobs gradually.
These prices are for Mac rentals and are charged in US dollars. For additional SSD storage or Thunderbolt 5 expansion, check the add-ons in the full plan. Confirm the total on the configuration page. Plan buttons preselect a configuration; choose your node and billing period when you order.
The reference average latency for South China & Southeast Asia is 20~40ms. Use this range to compare locations; it is not a measurement of your current connection or a latency guarantee for every ISP route.
20~40ms
Route: South China & Southeast Asia → Hong Kong
Your actual experience depends on your local connection, inter-network routing, time of day, and display settings. Interactive latency, file transfer speed, and build time are three different metrics.
Nodes run 365 days a year. For long-running builds, keep a remote repository, backups, and archived artifacts. Use the runner as a rebuildable execution environment.
These time estimates assume you have everything ready. They can help you plan your first validation run, but are not activation or build-time guarantees. Allow extra time for payment confirmation, instance delivery, and project dependencies. Check progress in the console.
Allow 2–5 minutes. Choose a configuration, node, and billing period, then check add-ons and the order total. For a short validation run, start with daily billing. Test a real project before committing to a longer term.
Allow 3–5 minutes, not including payment confirmation. We accept USDT-TRC20, Visa, Mastercard, and Amex via Stripe. Charges are in US dollars. Available payment gateways are confirmed by the backend.
Allow 5–10 minutes once your credentials are ready. Find the host details in the console, connect over SSH or VNC, verify the host identity, change the initial password, and add your SSH public key.
Allow 10–20 minutes for setup, excluding tool downloads and build execution. Check your Xcode and command-line tools versions, add the project's signing assets, register your runner, and verify the archive and logs.
Before you start, prepare repository access, a dependency list, your target Xcode version, and signing assets. Never put private keys, certificate passwords, or full connection credentials in build logs.
Choosing a node is about more than picking the closest location. Consider whether your team, repository network, and artifact destination can form a reliable route.
It can be a good first option to test, but don't choose based on geography alone. Remote debugging depends on the connection between your team and the host. Automated builds depend on the routes between the host, your code repository, dependency sources, and artifact destination. Test the full workflow over your usual network before choosing a longer rental term.
No. This is a regional average latency reference for South China & Southeast Asia, indicating the approximate network round-trip time. Build duration also depends on project size, chip, memory, cache hits, and signing steps. Record clean and incremental builds separately to see whether a configuration fits your workload.
The plan buttons on this page preselect a configuration. On the configuration page, select Hong Kong and confirm your billing period. Before paying, check the configuration, node, storage add-ons, and total in your order. The page title doesn't confirm your selection; the configuration page and final order do.
Rent a dedicated physical Mac by the day and track build time, memory use, and storage for a real project. Use your own results to choose a configuration and rental term.