For developers in South China & Southeast Asia, run Xcode builds, CI jobs, and remote desktop sessions on one dedicated Apple Silicon machine. Choose a rental period that fits your project—no need to buy local hardware upfront.
Shell M4 from $21.8/day. Check provisioning status, connection details, and expiry date in the console.
All three configurations give you exclusive use of the machine's CPU, GPU, and unified memory. Start with daily rental for a quick test, then compare weekly, monthly, or quarterly options for ongoing builds. Changing the billing period only updates the displayed price and order selection—not the machine specifications.
Showing daily prices. All prices are in USD.
Single-project development and short build tests
$21.8/day
Ideal for getting an Xcode build pipeline running, fixing a release issue, or checking whether an existing script works on macOS. Start with one build at a time, then decide whether to move up based on actual memory use.
Continuous integration and larger project caches
$39.6/day
Designed for keeping dependency caches, working across multiple repositories, and connecting the machine to a self-hosted runner. Measure a clean build and a cached build before setting concurrency, so simultaneous builds don't exhaust memory or disk space.
Heavier builds and unified memory workloads
$61.6/day
Suitable for larger project workspaces, demanding builds, and MLX or llama.cpp experiments. Whether a model fits also depends on quantization, context length, and runtime overhead—not just the model file size.
Need extra storage or a multi-machine setup? Check the order configuration for +1TB SSD, +2TB SSD, and Thunderbolt 5 daisy-chain add-ons. Add-ons have separate pricing by billing period and are not included in the machine rental prices above.
We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All charges are in USD. Available payment gateways and node status are shown in real time in the console.
Average latency guidance for South China & Southeast Asia is 20~40 ms. Use this range to compare locations; it is not a measurement of your connection or a guarantee of the latency you'll see on every session.
20~40ms
Users in South China & Southeast Asia can consider Hong Kong as a potential node. This figure helps indicate interaction distance; your results will also depend on your ISP, international routing, Wi-Fi, and any local proxy.
For remote desktop, check latency and jitter. For file transfers, also consider throughput and packet loss—one figure can't tell you both.
Nodes are available 365 days a year. Test network quality on your own connection, and track build time separately from time spent waiting on the network.
If your workflow is mostly committing code and waiting for CI, focus on repository checkout, dependency caching, and artifact uploads. If you spend hours at the desktop each day, test the interactive experience first. Don't make the final choice for your team based on geography alone.
The times below are estimates for the setup tasks, not provisioning guarantees. Payment confirmation, node delivery, and environment setup are separate steps; check the console for the latest status.
First, identify whether you need the machine for builds, CI, or inference. Then choose a configuration, billing period, and any add-ons. Before submitting, check the machine specifications, node, and total. Avoid paying for more concurrency than you've tested.
Choose a payment gateway available on the page. For USDT-TRC20, verify the network, payment details, and amount. For card payments, complete the verification steps through Stripe. Confirmation time depends on the payment result.
Once delivery is complete, check the IP address, connection details, login credentials, and expiry date in the console. The order status shows when delivery is complete; a payment confirmation page does not mean the machine is ready to connect.
On your first connection, verify the host fingerprint, update the login password, and configure an SSH public key. Then check the Xcode path and available disk space. Run a small project to confirm the build works; installing large toolchains and downloading projects take additional time.
Choose your node before planning your workflow. These three points affect your first order and any future migration.
This page covers Hong Kong, but you still need to check the selected node in the configurator. Don't rely on the page you came from. Before paying, confirm the node, configuration, billing period, and total shown in the configurator. Once the machine is delivered, check its instance details. The console shows current availability when you place your order.
No. Regional guidance isn't a measurement of your individual connection, and 20~40 ms is a starting point for comparing locations—not a latency guarantee. Test SSH response times, desktop interaction, and file transfers on your usual work network and at the times you'll use the machine. Switching ISPs or proxies from the same location can also change your experience.
Don't plan on an automatic migration. Before switching nodes, confirm the new order and environment, then sync your code, required data, certificates, and build configuration yourself. Recheck your runner and job tags. Back up the old workspace before it expires, and avoid running the same release task on both machines during the migration.
ssh → build → ship
Get started with Shell M4 from $21.8/day. Choose a configuration and billing period, confirm the node in your order, then proceed to payment. Base your choice on a real project, not a guess.