4 available data centers

Put your Cloud Mac on the right side of the network

VMRunner offers dedicated Apple Silicon physical nodes in Singapore, Tokyo, Seoul, and Hong Kong. Each data center provides three available machine tiers for remote development, continuous builds, automated testing, MLX validation, and media workflows.

Node selection is about more than city distance. Test access paths from your team’s networks, then consider your code repository, dependency sources, artifact recipients, and collaboration regions. The same city can perform differently across carriers and enterprise networks.

Choose a Cloud Mac Read the connection guide
Data centers
4
Available models
3 tiers
Node type
Dedicated physical machine
Availability
365 days a year
REGION ROUTING BOARD

Node selection playbook

Full model lineup
SG
Singapore Southeast Asia collaboration and artifact delivery
3 tiers
JP
Tokyo, Japan Xcode builds, signing, and testing
3 tiers
KR
Seoul, South Korea Remote sessions and CI execution
3 tiers
HK
Hong Kong Cross-region sync and artifact handoff
3 tiers
Selection criteria Local network test → Workflow location → Hardware specs
Regional overview

Four data centers, one consistent physical-node lineup

Singapore, Tokyo, Seoul, and Hong Kong all offer VMRunner M4 S, VMRunner M4 X, and VMRunner M4 Pro X. These model combinations are generally available to order; check the console for live availability.

01

Test your team’s entry points first

Test separately from developer offices, home networks, and CI egress points. Do not use one team member’s result to represent the entire team.

02

Then follow dependency paths

The location of your code repository, dependency mirrors, test services, and artifact recipients all affect pull, build, and delivery times.

03

Choose the right specs last

The node city determines network paths; the chip, memory, and storage determine capacity for parallel builds, caching, and large projects.

Four-city status board

Three model tiers listed across all four data centers

This board shows the catalog relationship between models and cities, not a real-time resource snapshot. During checkout, rely on the actual availability returned by the console.

VMRunner data centers and three Cloud Mac model tiers
Data center Recommended region VMRunner M4 S VMRunner M4 X VMRunner M4 Pro X
SingaporeSG Southeast Asia teams and regional artifact delivery Available Available Available
Tokyo, JapanJP Japan and Northeast Asia development collaboration Available Available Available
Seoul, South KoreaKR Remote sessions and CI for Korean teams Available Available Available
Hong KongHK Cross-region sync, execution, and handoff Available Available Available
SG · SINGAPORE

Singapore nodes: move build execution closer to Southeast Asian teams

Singapore nodes suit teams whose developers, testers, and artifact recipients are mainly in Southeast Asia. Remote desktop work, code pulls, dependency restoration, continuous builds, and artifact delivery can be organized around one city, reducing back-and-forth across multiple paths.

For teams across Singapore, Malaysia, Indonesia, Thailand, and nearby networks, test SSH round-trip time, remote display stability, and large-file uploads separately. CI teams should also record repository pull time, dependency-cache restoration time, and build-artifact delivery time.

Choose a Singapore node View the three plans

Tasks worth validating first

  • Remote development Use the editor, terminal, and graphical tools continuously while monitoring session stability during peak hours.
  • Continuous builds Run one clean build and one incremental build, recording dependency restoration and compilation times separately.
  • Artifact delivery Upload a representative build artifact and measure the actual time required for cross-team handoff.
Model lineup
3 tiers
Node type
Dedicated Apple Silicon
Status
Available
JP · TOKYO

Tokyo nodes: bring Xcode builds, signing, and testing closer to your team

Tokyo nodes are designed for development teams collaborating across Japan and Northeast Asia. They suit workflows that frequently use the macOS graphical interface, run Xcode, verify signing, and review test results. A dedicated physical machine avoids sharing compute resources with other tenants, helping establish a more consistent build baseline.

Before choosing, run a complete workflow on a real project: pull the code, restore dependencies, unlock Keychain, run xcodebuild, run tests, and return the artifacts. Compare more than total time: also measure remote input response, dependency-source access, and the speed of retrieving failure logs.

Choose a Tokyo node View build troubleshooting

Tokyo node validation checklist

  • Xcode builds Record clean-build, incremental-build, and unit-test times instead of judging performance from a single benchmark.
  • Signing workflow Verify that certificates, provisioning profiles, Keychain permissions, and command-line tool paths are consistent.
  • Test delivery Check that test reports, symbol files, and install packages can be handed off through your team’s standard workflow.
Model lineup
3 tiers
Primary uses
Builds, signing, testing
Status
Available
KR · SEOUL

Seoul nodes: balance remote sessions with automated pipelines

Seoul nodes suit development teams whose members and enterprise networks are primarily in South Korea. They can handle graphical remote sessions, SSH administration, CI Runner jobs, and developer-toolchain execution in one verifiable environment.

For CI, first verify Runner permissions, environment variables, cache directories, concurrent jobs, and artifact delivery. For graphical sessions, test resolution, keyboard mapping, clipboard behavior, and reconnection. If the same node handles interactive work and long builds, choose enough memory and storage for peak demand.

Choose a Seoul node View remote connection options

Seoul node validation checklist

  • Remote sessions Test display response, input mapping, session locking, and reconnection during working hours.
  • CI Runner Run one complete pipeline and verify permissions, caching, environment variables, and failed-job retries.
  • Toolchain execution Pin Xcode and command-line tool versions, and save job logs and build artifacts.
Model lineup
3 tiers
Primary uses
Remote sessions, CI
Status
Available
HK · HONG KONG

Hong Kong nodes: shorten paths for cross-region code sync and artifact handoff

Hong Kong nodes suit teams whose members, repositories, test services, or artifact recipients span multiple regions. They provide a shared point for code sync, build execution, and artifact handoff, especially for workflows that frequently transfer large project files between collaborators.

During evaluation, record “interaction smoothness” separately from “on-time task completion.” For remote desktops, focus on input and display; for builds, focus on CPU, memory, and disk; for file handoff, focus on upload, download, and verification. Only separate measurements can show whether an issue comes from the network, configuration, or project load.

Choose a Hong Kong node Compare model configurations

Hong Kong node validation checklist

  • Code sync Record full clones, incremental pulls, and dependency restoration to identify repository or network bottlenecks.
  • Build execution Use a real project to capture CPU, memory, disk peaks, and end-to-end task duration.
  • Artifact handoff Verify compression, checksums, uploads, and downloads so the recipient can retrieve the artifact repeatedly.
Model lineup
3 tiers
Primary uses
Sync, builds, handoff
Status
Available
Selection method

Compare candidate cities with the same repeatable workload

City distance is useful only for initial screening. Make the final choice using your team’s real networks, project, and handoff paths, and retain the data for later retesting.

  1. 01

    Define test entry points

    List office networks, home networks, corporate VPNs, and CI egress points. Run the same SSH, remote-session, and file-transfer tests from each.

  2. 02

    Standardize the workload

    Use the same code version, dependency state, Xcode version, and build command so project changes are not mistaken for node differences.

  3. 03

    Track metrics separately

    Record connection setup, code pull, dependency restoration, compilation, testing, and artifact delivery times separately instead of keeping only one total.

  4. 04

    Match available headroom

    Choose among the three model tiers based on concurrent jobs, memory peaks, cache directories, and project storage needs; do not use the node city as a substitute for hardware selection.

Choose and order

Choose a city from real team network tests, then configure a dedicated physical machine

During checkout, choose Singapore, Tokyo, Seoul, or Hong Kong, then select VMRunner M4 S, VMRunner M4 X, or VMRunner M4 Pro X. All charges are settled in USD. Payment options include USDT-TRC20 and Visa / Mastercard / Amex via Stripe; final gateway availability is determined by the backend response.

Choose a node and order now Compare the three prices first