4 nodes available

Place your Cloud Mac near your team’s working hours

VMCache currently offers four nodes in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. All three models are available at every node. Each rental includes one dedicated physical machine, with no shared compute, unified memory, or local storage.

Rent a Cloud Mac now Compare the three plans
Number of nodes
4 nodes available
Model coverage
3 configurations covered
Operating model
1 rental = 1 physical machine
Node allocation

Four regional work zones

Full catalog availability
SG
Singapore UTC+8 · Southeast Asia collaboration
Available
JP
Japan (Tokyo) UTC+9 · Japan development hours
Available
KR
South Korea (Seoul) UTC+9 · Build and test collaboration
Available
HK
Hong Kong UTC+8 · Cross-region handoffs
Available
Available configurations M4 16GB · M4 24GB · M4 Pro 64GB
Review each node

Filter by time zone, then confirm the workflow

A node name identifies the region where the physical device is located; it does not restrict the software environment or task type. Xcode builds, iOS and macOS testing, Unity builds, and MLX inference can run on any available node. Prioritize your team’s main working hours, upload sources, and artifact destinations.

SG All three available

Singapore node

Ideal for teams covering Southeast Asian working hours or keeping build jobs aligned with the same calendar rhythm as UTC+8 teams.

Local time zone
UTC+8
Collaboration hours
Suitable for daytime development, overnight batch builds, and next-morning acceptance testing for teams in Singapore and nearby regions.
Typical workloads
Dependency downloads, continuous integration, mobile app archiving, and continuously running MLX services.
VMCache M4 16 VMCache M4 24 VMCache M4 Pro 64
JP All three available

Japan (Tokyo) node

Designed for product, development, and QA teams working primarily on Japan time, keeping remote debugging, build batches, and on-call coverage in one time zone.

Local time zone
UTC+9
Development collaboration
Suitable for interactive daytime development in Tokyo, post-commit archiving, and artifact checks before testers start the next batch.
Typical workloads
Xcode toolchain validation, macOS app testing, Unity iOS builds, and dependency cache management.
VMCache M4 16 VMCache M4 24 VMCache M4 Pro 64
KR All three available

South Korea (Seoul) node

Ideal for scheduling automated builds, regression tests, and artifact checks within the Korean workday, while creating a one-hour offset from UTC+8 teams.

Local time zone
UTC+9
Build and testing
Split commit triggers, dependency preparation, archiving, testing, and artifact registration into sequential batches for clear ownership handoffs.
Typical workloads
Parallel builds, version regression, continuous testing, model loading, and inference service health checks.
VMCache M4 16 VMCache M4 24 VMCache M4 Pro 64
HK All three available

Hong Kong node

Ideal for UTC+8 teams managing cross-region work, with clear data paths for code uploads, builds, and artifact delivery.

Local time zone
UTC+8
Cross-region collaboration
Use it as a handoff point for distributed teams, with consistent records of build batches, test results, and MLX service changes.
Typical workloads
Mobile development pipelines, cross-team artifact delivery, multi-version test tracking, and continuous MLX inference.
VMCache M4 16 VMCache M4 24 VMCache M4 Pro 64
Model and node matrix

12 catalog combinations available

All three models are available across four nodes in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Each combination is a dedicated physical node, not a virtual machine; the processor, unified memory, and local storage are not shared with other tenants.

VMCache three-model availability matrix across four nodes
Model Configuration Singapore Japan (Tokyo) South Korea (Seoul) Hong Kong
VMCache M4 16 M4 · 16GB · 256GB Available Available Available Available
VMCache M4 24 M4 · 24GB · 512GB Available Available Available Available
VMCache M4 Pro 64 M4 Pro · 64GB · 2TB Available Available Available Available
Same operating boundaries

All nodes run normally 365 days a year. During your rental, you can use the full macOS graphical interface and command line, and install the software required for builds, testing, or MLX inference according to your team’s workflow.

Same specifications

VMCache M4 16 is fixed at M4, 16GB, and 256GB; VMCache M4 24 is fixed at M4, 24GB, and 512GB; VMCache M4 Pro 64 is fixed at M4 Pro, 64GB, and 2TB.

How to choose a node

Narrow your choice with three questions

The node does not replace the model decision. First determine the unified memory and storage your workload requires, then choose the location that is easiest for your team to manage from the four nodes supported by that model.

  1. 01

    Which time zone does your team primarily work in?

    If you frequently open the graphical interface, monitor build logs, or adjust model services, choose a node close to the main operators’ working hours. For UTC+8, compare Singapore and Hong Kong; for UTC+9, compare Tokyo and Seoul.

    Result 2 priority nodes
  2. 02

    Where is data uploaded, and who receives the artifacts?

    List the sources and destinations for your code repositories, dependency caches, test data, model files, and build artifacts separately. For large models or artifacts, measure the transfer path using your team’s own network environment rather than using a city name as a proxy.

    Result Define the primary data path
  3. 03

    Confirm the real-time result when ordering

    In the order flow, select the model, billing cycle, and node. The console returns the combinations currently available, after which you confirm storage expansion and rental term. The four catalog nodes do not redirect to separate regional landing pages.

    Result Finalize the order configuration
Quick check

Match the node to the workflow and the model to the workload

Start lightweight builds and basic automation with VMCache M4 16 at 16GB / 256GB; choose VMCache M4 24 at 24GB / 512GB for daily development, dependency-heavy builds, and multitasking; choose VMCache M4 Pro 64 for MLX inference workloads requiring 64GB unified memory and 2TB local storage. Node selection does not change model specifications or term pricing.

Confirm first Unified memory and local storage
Compare next Team time zone and transfer path
Verify finally Combinations returned by the console in real time
Configure your order

Choose your Cloud Mac from four nodes

All three models are available in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Select the configuration, term, and node, then confirm the real-time result in the console and complete your order.

Configure a Cloud Mac Check the full pricing first