From Setup to Your First Task

Order a Cloud Mac in About Four Minutes

Start by defining your workload, then check the model, node, and term. After ordering, retrieve your connection details, check the environment, and run a verifiable Xcode build or MLX model-loading task.

Rent a Cloud Mac Now View All Three Configurations

Catalog Configurations: 3 options
Available Nodes: 4
Order Steps: About 4 minutes

Provisioning First-Task Checklist

Ready to Proceed

Use Case Build / Test / MLX Inference

Configuration Catalog M4 16 / M4 24 / M4 Pro 64

Node Catalog SG / JP / KR / HK

Billing Terms Daily / Weekly / Monthly / Quarterly

01 Configuration

02 Node

03 Payment

04 Connection

Delivery Status and Availability Use the live status returned by the console

Before You Begin

Clarify These Six Decisions Before Configuring Your Order

No complex documents are needed. Define your use case, budget, target node, and local connection requirements to avoid switching repeatedly between models and terms.

01 Define the Use Case

Distinguish Xcode CI/CD, iOS or macOS builds, multi-version testing, Unity iOS exports, and MLX inference. Your use case determines the priority of unified memory, storage, and runtime.

02 Set Your Budget

Your budget should cover the base model, rental term, and storage add-ons. Do not compare daily prices alone; check the catalog amount for your planned term.

03 Choose the Term

Schedule temporary validation by day or week; for ongoing builds and inference services, compare monthly or quarterly billing. Each term has its own catalog price—do not convert between them.

04 Choose a Node

Choose Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong. Prioritize your team’s time zone, data-transfer path, and the live availability shown in the console.

05 Estimate Disk Usage

Account for source code, dependency caches, build artifacts, model files, datasets, and logs. If base storage is insufficient, add +1TB SSD or +2TB SSD when ordering.

06 Check Local Connectivity

Confirm a stable local network and prepare an environment for accessing the macOS graphical interface or command line. Retrieve connection details only through order management, not from public pages.

Delivery Timeline

Four Confirmation Steps, About One Minute Each

This timeline describes the pace of the actions needed to complete an order, not a fixed delivery commitment. Configuration, nodes, payment gateways, and connection details depend on order status and the live console response.

About 4 minutes Choose, price, and pay

Choose a Configuration
About 1 minute

Choose one of VMCache M4 16, VMCache M4 24, or VMCache M4 Pro 64 based on memory, base storage, and task type.
Confirm the Node and Term
About 1 minute

Choose Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong, then check the applicable catalog price by day, week, month, or quarter.
Complete Payment
About 1 minute

Choose USDT-TRC20, or use Visa, Mastercard, or Amex processed by Stripe. All orders are settled in US dollars (USD).
Retrieve Connection Details
About 1 minute

Return to the console after payment to check your order status. When connection details are available, follow the on-page instructions and save them in your team-approved secrets manager.

Total About 4 minutes; actual timing depends on order status

Create Your Order

Three Models, Three Resource Profiles

All three are dedicated physical nodes, not virtual machines. Each rental provides one dedicated physical machine, with no shared processor, unified memory, or base storage.

Light Builds

VMCache M4 16

M4 · 16GB · 256GB

For Xcode builds and automated checks with manageable dependency sizes
For single-project validation, scripts, and short-term testing
Check disk usage for source code, caches, and artifacts first

Choose VMCache M4 16

Everyday Development

VMCache M4 24

M4 · 24GB · 512GB

For ongoing development, dependency caches, and multi-task builds
More unified memory for parallel tools and simulator environments
512GB of base storage for retaining more intermediate build artifacts

Choose VMCache M4 24

Large-Model Inference

VMCache M4 Pro 64

M4 Pro · 64GB · 2TB

For MLX model loading that requires more unified memory
For larger dependency caches, datasets, and persistent task directories
Validate memory and concurrency limits with the real model before production deployment

Choose VMCache M4 Pro 64

All Three Models Are Available in All Four Nodes

Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong operate continuously 365 days a year. Actual availability at ordering time is determined by the live console response.

Typically available Singapore SG · UTC+8

Typically available Japan (Tokyo) JP · UTC+9

Typically available South Korea (Seoul) KR · UTC+9

Typically available Hong Kong HK · UTC+8

Choose a Billing Term

Price Each Order Term Separately—No Conversion or Rounding

Daily, weekly, monthly, and quarterly terms have separate catalog prices. Determine the actual usage duration first, then read the corresponding column. Do not multiply the daily price or round decimal amounts.

Complete Term Pricing for Three VMCache Cloud Mac Models
Model	Configuration	Daily	Weekly	Monthly	Quarterly
VMCache M4 16	M4 / 16GB / 256GB	$19.8	$53.4	$98.8	$268.7
VMCache M4 24	M4 / 24GB / 512GB	$39.2	$105.9	$196.1	$533.4
VMCache M4 Pro 64	M4 Pro / 64GB / 2TB	$60.3	$162.9	$301.7	$820.6

Set the Duration First

For one-time validation, choose the term closest to the actual number of usage days; for continuous pipelines, choose monthly or quarterly billing based on the full operating plan.

Review Add-Ons

Extra storage and Thunderbolt 5 aggregation have separate term prices. Add them only when the task requires them.

Review the Order Last

Before submitting payment, recheck the model, node, term, and add-ons, and confirm that the displayed USD total matches your expectations.

Complete Payment

Two Payment Options, Settled in USD

VMCache supports USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe. Actual gateway availability is determined by the backend response.

Confirm the order currency is USD
Confirm the model, node, term, and add-ons
Return to the console after payment to check order status
Keep the order ID for future support requests

Digital Asset

USDT-TRC20

Pay using the network and amount shown on the order page. Confirm the network type and recipient details before sending; do not switch to another network.

Bank Card

Visa / Mastercard / Amex

Card payments are processed by Stripe. Whether this gateway is shown and available depends on the live order-page response.

First Connection and Security Checks

A Successful Connection Is Not the Finish Line

After first access, establish an environment baseline before syncing source code, dependencies, or models. This separates connection, system, and task issues during troubleshooting.

First-Access Checklist Check in This Order After Connecting

6 items

01

Confirm the Order and Node

Check the order ID, model, and node in the console to ensure you are connecting to the dedicated physical machine assigned to this rental.
02

Check Login Details

Retrieve connection details only through order management. Never place passwords, private keys, or complete connection information in public tickets, repositories, or chat logs.
03

Record the System Version

Confirm that the macOS version matches the task requirements. For multi-version testing, record the target version and test batch first.
04

Verify the Network Path

Test reachability to code repositories, dependency sources, and internal team services. If connection problems occur, first distinguish local-network symptoms from node-side symptoms.
05

Check Available Disk Space

Check available space before downloading dependencies, datasets, or models, and leave room for caches, temporary files, archives, and logs.
06

Create a Task Directory

Use clear directories for source code, caches, artifacts, models, and logs. Do not treat the node as your only backup location.

Run Your First Task

Run a Small, Complete Validation Loop First

The first task is not about using all available resources immediately. Confirm that the toolchain, inputs, outputs, and log paths are reproducible. The two workflows below cover development builds and MLX inference.

Xcode Build Validation

Validate the Toolchain with a Reproducible Build

Confirm Versions
Record the Xcode and command-line tools versions and ensure they match the project requirements.
Prepare Dependencies
Pull the source code and restore dependencies while monitoring cache directories and disk-space changes.
Run a Clean Build
Run one build from a clean state and record the command, duration, and failure stage.
Check the Artifacts
Confirm that the archive or test results are in the expected directory and retain redacted logs.

Troubleshoot Xcode Builds

MLX Model Validation

Validate Model Loading Before Increasing Request Concurrency

Check the Model Format
Confirm that the model files, tokenizer, and runtime script are compatible with the current MLX environment.
Monitor Unified Memory
Load one model and record unified-memory usage; do not use a single peak as a substitute for long-term assessment.
Limit the Listen Scope
Start the service on a controlled address and confirm access controls and log-redaction policies.
Increase Request Batches Gradually
Start with one request, gradually increase batch size and concurrency, and record errors and loading logs.

Troubleshoot MLX Inference

First-Task Completion Criteria

The input source is clear, the command is reproducible, the output location is defined, logs are redacted, and the team knows which order and environment details to provide when issues occur.

Open the Console

Ready to Start

Choose a configuration, then create your Cloud Mac order

Confirm the three models, four nodes, and four billing terms in the order flow. If you need to compare memory, storage, and total pricing first, return to the plans page and review each item.

Rent a Cloud Mac Now Compare Rental Plans