Bring your Xcode build machine closer to your team in East Asia. Each Mac mini is assigned to one customer—not shared as a virtual machine.
From $19.2/day · Two Apple M4 configurations · Check the console for live availability.
Choose a configuration based on your project's memory and cache needs, then select a term based on how long you'll use it. Each order covers one dedicated physical machine, never shared with another customer.
Showing daily pricing. Confirm your billing period and node when placing your order.
Everyday CI for a single app and sequential builds.
$19.2/day
A good starting point for moving one build pipeline. Keep your dependencies and DerivedData cache, compare the first build with incremental builds, then decide whether you need more concurrency.
Builds with multiple targets and mixed technology stacks.
$39.7/day
Well suited to multi-target archives and iOS builds with Flutter or React Native. Extra memory and storage make it easier to keep multiple dependency sets on hand. Measure your project to determine the right level of concurrency.
All prices are in USD and cover the base machine. +1TB SSD, +2TB SSD, and Thunderbolt 5 daisy-chaining are optional add-ons, billed separately. The billing buttons only change the prices shown on this page. Confirm your machine, billing period, and node at checkout.
Tokyo offers a nearby connection option for teams in East Asia. Interactive remote desktop use, code transfers, and build processing are separate parts of the workflow—a single latency figure can't tell you how the whole setup will perform.
30~60 ms
This average latency range for East Asia comes from the regional network reference in the node directory. It is not a live test of your connection or a latency guarantee for every client.
The directory does not specify a standard test carrier, sampling window, or probe endpoint. Actual round-trip latency varies with your local provider, cross-region routing, wireless network, and time of day.
Start with a full workflow on a daily plan. Keep a record of the test time, connection, and build logs before choosing a long-term node and billing period for your team.
These steps take about 4 minutes in total. This estimate excludes blockchain confirmations, card verification, manual processing, and project dependency downloads. Check the console for machine assignment progress.
Verify your account by email. Use an address where you can receive order updates; your orders, invoices, and support tickets are all managed in the same account.
Choose one of the two configurations, then confirm the billing period and node. Add storage if you need room for more dependencies, caches, or build artifacts.
Pay with USDT-TRC20 or Visa / Mastercard / Amex, processed by Stripe. Available payment gateways are determined by the backend. Keep your payment page and transaction record until payment is confirmed.
Once payment is confirmed, the system assigns your machine and makes SSH / VNC credentials available in the console. Test your connection, check the Xcode toolchain, import your signing assets, and clone your repository.
Get clear on how your team will work across locations and what to check in your order before you place it.
Consider who needs frequent graphical access, and where your repositories, dependency sources, and artifact users are based. If most of your users are in East Asia, start by considering a Tokyo node. Team members elsewhere can submit jobs over SSH and download artifacts centrally, reducing the need for constant remote desktop sessions.
If people in both locations need extended interactive access, evaluate a separate dedicated machine closer to each group. Choose a node based on real connection tests—not on the assumption that everyone will see the reference latency range.
No. The reference value describes network round-trip latency. An archive runs on your dedicated machine, and its build time also depends on code size, dependency state, compiler settings, memory pressure, and cache hits. A smoother connection does not mean build times will improve by the same proportion.
When evaluating a Tokyo node, record a cold-cache build, an incremental build, and an artifact download. These results can help your team identify whether the bottleneck is the network or the build process.
The machine buttons on this page preselect the corresponding configuration. On the configuration page, explicitly choose Tokyo and confirm the billing period, storage add-ons, and order total. Viewing a node's details does not select it for you.
If you need to move existing tasks and caches, back up your code, signing assets, and artifacts first, then make sure the new machine is ready. A new node does not automatically migrate data from your old environment.
A dedicated physical Mac mini, online 365 days a year. Test your project with daily billing, then choose a longer term that suits your team's workflow.