For developers and teams in East Asia. Run Xcode builds, iOS tests, and CI on a dedicated physical machine, with full access to the macOS desktop and command line. No virtualization.
$21/day · 3 configurations · 4 billing periods
Choose a node and billing period when you order. Availability is confirmed in real time in the console. Connection details are typically ready about 4 minutes after payment is confirmed.
CPU, memory, and storage are dedicated to you. Start with daily billing for a short test. For ongoing builds or team development, estimate how long you’ll need the machine, then compare weekly, monthly, and quarterly rates. All billing periods are listed below for easy comparison.
$21/day
For lightweight builds, single-project CI, and short regression tests. Keep your project, toolchain, and current test resources on the node; archive older build artifacts separately to avoid filling the disk with cached files.
Check real-time availability in the console.
Rent Hold 16$41.4/day
For everyday Xcode development, running multiple simulators, and UI testing. Compared with the entry-level plan, it offers more memory and storage for your development environment, test device images, and frequently used build caches.
Check real-time availability in the console.
Rent Hold 24$59.5/day
For MLX experiments, large language model inference, and full builds of large projects. The 64GB of unified memory and 2TB SSD leave room for model weights, project dependencies, and build artifacts. Check your workload’s actual memory requirements first.
Check real-time availability in the console.
Rent Hold Pro 64Same configuration, different billing periods. Changing the displayed rate does not change the chip, memory, or storage. The button preselects the configuration; confirm the node and billing period on the order page. The period displayed here is not submitted automatically.
Add storage if you need it. Optional add-ons include +1TB SSD, +2TB SSD, and Thunderbolt 5 daisy chaining. Add-ons are priced separately and are not included in the base rates above. See the plans page for prices across all four billing periods.
Prices in USD. Payment is accepted via USDT-TRC20 or Visa / Mastercard / Amex (through Stripe). Available payment gateways are determined by the backend. Check the order total and billing period before paying.
For users in East Asia, the average round-trip latency reference is 30~60ms. This is a regional reference, not a live measurement of your connection or the response time of every remote desktop frame.
Scrolling, clicking, and typing in a remote desktop are affected by your local network, the route to the node, display resolution, and encoding load. Connect over the network you normally use, then test a real project from editing and building through to reviewing test results.
Focus on consistent responsiveness during extended use, not a single latency reading.
CI builds usually run locally on the node, but the initial repository checkout, dependency downloads, and artifact uploads still use the network. Keeping dependency caches on the node reduces repeated transfers. For large files, check upload speed at the source and available storage at the destination.
Track build and transfer times separately to identify the bottleneck.
| What to check | What this page provides | How to verify |
|---|---|---|
| Regional latency | Average round-trip latency reference for East Asia: 30~60ms | Connect from your usual location and network. Results vary by provider, route, and time of day. |
| Desktop experience | Remote desktop connection details after setup | Use your everyday display resolution for editing and debugging. Check input response, screen updates, and connection stability. |
| Builds and transfers | Dedicated local compute and storage, with SSH access | Time code checkouts, builds, and artifact transfers separately. Don’t treat the end-to-end time as network latency. |
If your experience differs significantly from the reference, note your network, connection time, symptoms, and machine ID, then open a support ticket in the console. Never include passwords, private keys, or signing certificates in diagnostic details.
These are estimates for a typical setup, not a countdown guarantee. Payment confirmation, physical node assignment, and system initialization each take time. Check your order status and delivery details in the console.
About 1 minute
Choose a machine, billing period, and node for your workload. Check the memory, storage, and add-ons, then confirm the order total. Don’t judge the long-term cost by the entry-level daily rate alone.
About 1 minute
Pay with USDT-TRC20 or Visa / Mastercard / Amex (through Stripe). Follow the payment page instructions and wait for your order to be confirmed. Confirmation time depends on payment processing.
About 1.5 minutes
Your dedicated machine is assigned and the environment is initialized. Check your order progress while this happens; don’t mistake a pending setup for a connection failure before your connection details are available.
About 0.5 minutes
Find your machine ID and remote desktop and SSH details in the console. Change the initial password after your first connection, then transfer your code and toolchain. Store credentials in a secure, team-controlled location.
Once your machine is ready, use its machine ID to identify the instance and your order status to check the rental period. Nodes run year-round, 365 days a year. Before renewing or ending your rental, check the expiry date and back up any data you need to keep.
Find out how to choose a location, understand pricing, and plan for multiple machines. First decide whether your workload is interactive development or background builds, then choose how to reserve your machine.
It’s a good place to start, but physical distance isn’t the only factor. Remote desktop work depends more on actual round-trip latency and connection stability. For background builds, consider the locations of your repository, dependencies, and artifact destination too. The 30~60ms figure on this page is a regional reference; check your actual route over the network you normally use. For a long-term rental, test with a real workload before choosing a longer billing period.
Each of the three base prices covers one dedicated physical machine with the chip, memory, and SSD listed on its card. The latency reference doesn’t mean there’s an extra low-latency fee. Storage upgrades and Thunderbolt 5 daisy chaining are optional add-ons, priced separately. On the order page, check the node, billing period, and add-ons, then pay the USD total shown in your order confirmation. You can compare all base and add-on prices on the plans page.
List interactive development machines and background runners separately, and note each machine’s purpose, expected concurrent workload, data volume, and rental period. Using the same node for frequently transferred project resources can simplify management, but it won’t eliminate transfer time. Check the configuration and order for each machine individually. If you already have a machine, plan data synchronization, runner registration, and credential separation before adding another. A new instance is not an automatic copy of your existing one.
Once you’ve settled on a configuration and billing period, you’re ready to order. If you’re still comparing plans, check the full prices and add-ons rather than guessing from the configuration names.
Three dedicated physical configurations, available daily, weekly, monthly, or quarterly. Check the node and price before paying, then get your connection details in the console once setup is complete.