XOps 16
For quantized model experiments, solo development, and on-demand builds.
- Chip
- M4
- Unified memory
- 16GB
- Storage
- 256GB
Day $19.4 · Week $52.3
Month $96.8 · Quarter $263.3
For development teams in Northeast Asia: run MLX inference, Xcode builds, and remote macOS workflows on a cloud Mac dedicated to your use.
Choose the right fit for your memory needs, from M4 / 16GB to M4 Pro / 64GB. Pay in advance by the day, week, month, or quarter. Check live availability in the console when you place your order.
From $19.4/day · Ready in about 4 minutes
One order, one dedicated physical Mac
Choose a model and billing period, then confirm the node and live availability at checkout.
All prices are in USD. Switch between billing periods to compare all three plans. Storage upgrades and other add-ons can be selected at checkout.
For quantized model experiments, solo development, and on-demand builds.
Day $19.4 · Week $52.3
Month $96.8 · Quarter $263.3
For running common 7B–8B quantized models and continuous builds.
Day $40.8 · Week $110.1
Month $203.8 · Quarter $554.3
Extra unified memory for larger models or running multiple models in parallel.
Day $61.2 · Week $165.1
Month $305.8 · Quarter $831.8
All three plans include SSH and VNC access. Confirm available configurations, node availability, and the final amount through the live console. Pay in USD using USDT-TRC20 or Visa / Mastercard / Amex (via Stripe).
The reference latency from Northeast Asia is 30~50ms. Use this figure as a starting point when choosing a location; it is not a fixed latency for every carrier route or connection.
Your experience also depends on your city, carrier routing, peak-time congestion, and local network. SSH command-line work is less sensitive to round-trip latency. Before using a VNC desktop or syncing large model weights, test your own connection and choose a node and transfer window accordingly.
Choose a location based on where your team connects from. Reference latency is not a service guarantee. Before ordering, check your own network with ping and route diagnostic tools.
This is the typical process. Payment confirmation and actual delivery progress are shown in the console.
Confirm the billing period and configuration, then complete payment in USD at checkout.
Once your order is confirmed, you get an entire machine with compute resources that aren't shared with other customers.
Delivery information and connection credentials are available in the console after you sign in.
Test your connection, then install dependencies, sync your project, or start an inference service.
The three plans and four billing periods listed here use the same USD catalog prices across locations. After choosing a node, confirm the final configuration, add-ons, and total at checkout. Availability is shown live in the console.
No. The reference figure is not a guarantee for every connection. Routing, your carrier, and your local network all affect latency. If you mainly use a graphical desktop or transfer large files, test round-trip latency to the node from your work network, then use the connection guide to adjust display quality and transfer times.
All three listed plans are available at this node. Choose a configuration that meets your current memory and storage needs when you order. If you need to make a change later, check the available options and current configuration in the console before deciding whether to redeploy. Back up your files and model weights before migrating projects.
Plans start at $19.4/day. Confirm the node, billing period, and live availability at checkout. Delivery typically takes about 4 minutes.