About VMRunner

Run macOS workloads reliably on dedicated physical nodes

VMRunner provides Cloud Mac environments for continuous builds, automated testing, and remote development. We deliver dedicated Apple Silicon physical nodes—not shared virtual machines—with configurations, rental terms, node regions, and support boundaries available for review before ordering.

Rent a Cloud Mac View 3 plans
Available models
3 plans
Data center regions
4
Availability
365 days
SERVICE RUN SHEET

A verifiable delivery run sheet

Physical node
  1. 01
    Catalog confirmation Model, term, node, and additional storage listed item by item
    Verifiable
  2. 02
    Node assignment Each order maps to one dedicated Apple Silicon physical node
    Dedicated
  3. 03
    Connection delivery Node address, separate credentials, and connection instructions provided
    Controlled
  4. 04
    Support tracking Resolution proceeds using the order ID, logs, and reproduction steps
    Traceable
Scope Builds · Testing · Remote development · MLX validation
Our origin

Started with a build task—not a generic server

Teams that need macOS usually do not want to “own a remote computer.” They need to complete a defined workflow: pull code, restore dependencies, compile, sign, test, export, and return the artifacts to the pipeline.

VMRunner is designed around this workflow. Teams can rent a Cloud Mac by the day, week, month, or quarter, running short-term validation, releases, and continuous integration in an isolated environment without exposing a local development machine to automation.

We do not define the product as vague “cloud compute.” Every order maps to a specific catalog model, memory configuration, storage capacity, node city, and rental term. You know what you selected before ordering and can verify delivery against the same fields afterward.

This approach suits engineering teams that need a fixed macOS environment, want to isolate their local workspace, or need distributed teams to share the same build baseline. It is not a shared desktop, nor does it replace real Apple Silicon physical nodes with a virtualized resource pool.

Service definition

You rent a physical node; VMRunner turns the order into a usable environment

The service starts with the configuration catalog and ends with connection delivery and support tracking. Project content, development credentials, and backup policies on the node remain under your control.

What you receive

Dedicated Apple Silicon physical node

Each order maps to one physical node listed in the catalog. CPU, memory, and local storage are not sold as shared virtual-machine resources, giving you a stable build and test baseline.

Platform responsibilities

Catalog, node assignment, and connection delivery

VMRunner provides ordering for three available models across four data centers, assigns a node against the confirmed order, and provides its address, separate credentials, and basic connection instructions.

Support approach

Follow the evidence, not guesswork

When connectivity or builds fail, support checks the order ID, node city, time of occurrence, reproduction steps, and redacted logs. You do not need to send private keys, full access tokens, or certificate passwords.

Service boundaries

VMRunner provides the Cloud Mac ordering entry point, node assignment, and order-related support processes. It does not manage your code repositories, certificates, project dependencies, team permissions, or business-data backups.

Engineering principles

Replace vague promises with verifiable information

Engineering teams need facts they can retest, reconcile, and reproduce. Our product information and support process follow four principles.

01

Transparent configuration

The catalog lists only three available models. Chip, memory, local storage, available nodes, and add-ons are shown before order confirmation instead of being replaced by vague performance tiers.

02

Consistent pricing

Original USD amounts are shown by day, week, month, and quarter. The page, configuration flow, and confirmed order use the same pricing fields instead of attracting clicks with unclear converted prices.

03

Verifiable logs

Issue handling is based on timestamps, command output, build logs, and expected results. Reproducible failures are turned into clear steps first, rather than described only as “occasional slowdowns.”

04

Direct communication

Support replies state confirmed facts, next actions, and missing information. When the available evidence is insufficient, we clearly request the needed materials instead of replacing a conclusion with generic performance claims.

Who it is for

Four workflows that need a real macOS environment

One Cloud Mac can support different tasks, but selection should start with runtime, concurrency, peak memory, storage usage, and delivery requirements.

Development

iOS and macOS developers

Run Xcode builds, tests, signing preparation, and release exports. Schedule short release tasks by the day or week, or choose a longer term for an ongoing development environment.

  • Keep everyday local workspaces separate from release environments
  • Lock Xcode, dependency, and cache baselines
  • Retain build logs and artifact handoff records
Automation

CI/CD engineering teams

Register a dedicated Runner for code checkout, dependency restoration, builds, tests, and artifact delivery. A dedicated node helps control caches, environment variables, and concurrency boundaries.

  • Separate Runner permissions by project
  • Record cold-build and incremental-build differences
  • Limit key scope and rotate credentials
Experimentation

AI and MLX experimenters

Validate model loading, inference workflows, and memory usage on Apple Silicon. Before selecting a node, record model size, peak memory, and per-run duration.

  • Separate model files from runtime cache usage
  • Pin dependency versions and experiment parameters
  • Save reproducible input and output summaries
Media

Audio and video workflow teams

Process proxy media, project files, and export jobs remotely. Before a full migration, test network performance, graphics-session resolution, media capacity, and finished-file transfer time.

  • Sync only the required media instead of the full archive
  • Calculate local storage needs by project
  • Verify checksums and file integrity after export
Regions

4 data centers available, with clearly defined cities

Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong all offer the three catalog models. Actual availability is determined by the real-time response in the console.

SG

Singapore

For remote development, continuous builds, and cross-region artifact delivery for Southeast Asian teams.

Catalog models
3 plans
Status
Good availability
JP

Japan (Tokyo)

For Xcode builds, signing preparation, and automated testing for teams in Japan and Northeast Asia.

Catalog models
3 plans
Status
Good availability
KR

South Korea (Seoul)

For remote sessions, CI Runners, and development-toolchain workloads for teams in South Korea.

Catalog models
3 plans
Status
Good availability
HK

Hong Kong

For code synchronization, build execution, remote development, and artifact handoff across distributed teams.

Catalog models
3 plans
Status
Good availability
View node selection guide
Responsibilities

The platform delivers; you control projects and credentials

Clear responsibilities do not reduce support—they speed up diagnosis when something goes wrong by first identifying whether the issue concerns node delivery, network connectivity, toolchain configuration, or the project itself.

VMRunner handles

Physical node delivery and order-related support

  • Maintain the ordering catalog for three models across four data centers
  • Assign nodes and deliver connection details against confirmed orders
  • Support connectivity, node status, and billing verification
  • Troubleshoot issues using order IDs, timestamps, and logs
  • Operate continuously 365 days a year
You handle

Account access, code assets, certificates, and data backups

  • Protect connection credentials, code-repository tokens, and team account permissions
  • Manage project certificates, provisioning profiles, keys, and their validity periods
  • Maintain separate backups for code, media, configuration, and build artifacts
  • Control Runner permissions, environment variables, and third-party dependency sources
  • Redact logs and configuration files before submitting support information
Next steps

Verify the configuration and node, then hand your workload to a dedicated Cloud Mac

View the three plans and confirm the chip, memory, storage, rental term, and data-center region. If you need to migrate an existing environment, read the remote access guide first.

Start your order Remote access guide