Every plan provides a dedicated Apple Silicon server. Each order receives an exclusive physical node with no shared compute resources and is not a virtual machine. Rent by the day, week, month, or quarter, starting at $20.3/day.
Core is designed for light builds and single-project work. Plus provides more memory and storage headroom for multi-project development, parallel builds, continuous integration, and local model experiments. All prices are in USD.
Ideal for single-project work, light Xcode builds, archive validation, and low-concurrency automation.
Ideal for multi-project development, parallel build jobs, CI/CD runners, Unity iOS builds, and local model experiments.
Use daily or weekly billing for short-term validation; compare monthly and quarterly billing for long-running builds. The table lists base server costs only and excludes storage expansion and Thunderbolt 5 interconnects.
| Plan | Hardware configuration | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|---|
| VMArm M4 Core | M4 / 16GB / 256GB | $20.3/day | $54.9/week | $101.6/month | $276.4/quarter |
| VMArm M4 Plus | M4 / 24GB / 512GB | $39.4/day | $106.5/week | $197.2/month | $536.4/quarter |
Choose the billing term based on task duration, then select the configuration based on concurrency and memory usage. Do not substitute a short-term peak for your long-term average workload. If caches, archives, and build artifacts are growing quickly, review storage add-ons as well.
Both configurations use the M4 chip and provide a dedicated physical node. Network service is delivered according to the selected location, without shared virtual-machine quotas. Check the console for real-time connection status.
Both plans provide dedicated physical servers, not virtual machines, and support macOS graphical and command-line workflows. When you need more data space, add +1TB SSD or +2TB SSD to the base plan.
Add-ons follow the billing term of the selected base plan. Choose storage based on project data, dependency caches, and archive retention; Thunderbolt 5 interconnects are billed per machine.
Ideal for workflows that retain dependencies for multiple projects, build caches, archives, and test artifacts.
Ideal for large asset repositories, multi-branch builds, longer-lived caches, and local model datasets.
For node combinations with a clear multi-machine interconnect requirement. Confirm your workload and machine count before selecting it.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.8/day | $7.7/week | $14.2/month | $38.6/quarter |
| +2TB SSD | $5.6/day | $15.4/week | $28.4/month | $77.2/quarter |
| Thunderbolt 5 interconnect (per machine) | $1.2/day | $3.1/week | $5.8/month | $15.8/quarter |
Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West are included in both plan catalogs. We recommend choosing the location closest to your team, code repository, or primary build trigger.
| Configuration | Singapore | Japan (Tokyo) | South Korea (Seoul) | Hong Kong | US West |
|---|---|---|---|---|---|
| VMArm M4 Core | Available | Available | Available | Available | Available |
| VMArm M4 Plus | Available | Available | Available | Available | Available |
When developers frequently use a graphical interface, compare the actual network path from your team’s location to each node.
For CI/CD jobs, consider the code-pull location, artifact upload destination, and the runner’s continuous availability.
The matrix shows catalog relationships. Actual availability when submitting a configuration is returned in real time by the console.
Do not choose a configuration based only on the project name. The same Xcode project may require very different memory, cache, and storage capacity for a single archive versus multiple concurrent runners.
If your main tasks are code editing, dependency installation, single-job debugging, archive validation, or occasional automated builds, choose VMArm M4 Core.
When Xcode, dependency tools, simulators, or multiple build queues run simultaneously, 24GB of memory and 512GB of base storage provide more practical headroom.
Start with the 24GB memory in VMArm M4 Plus, then choose +1TB SSD or +2TB SSD based on model files, datasets, caches, and result retention.
Before submitting a configuration, cross-check task type, location, memory, storage, billing term, and payment method. Teams doing substantial remote work should also verify their local network and VNC client setup first.
Record your primary tasks, concurrently running tools, and expected number of parallel builds.
Choose the location closest to your team or repository from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West.
Choose between 16GB / 256GB and 24GB / 512GB, and estimate cache and archive growth.
Choose daily, weekly, monthly, or quarterly billing based on task duration. Do not use a single-day peak to represent long-term needs.
Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported, with all charges settled in USD.
Check your local network, VNC client, keyboard mapping, and required screen resolution.
All orders are settled in USD. Payment supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe); available gateways are determined by the console.