Dedicated physical Mac mini

Keep iOS builds and
automated app builds running

Every order delivers one dedicated physical Mac mini—not a virtual machine. Connect over SSH or VNC and run Xcode, fastlane, and your existing CI workflows on a verifiable cloud node.

Mac Mini M4 16GB RAM 5 nodes $20.3 / day
Rent a cloud Mac now View Runner M4 plans
RunnerVM Mac mini build cluster connecting nodes in Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast 5 REGIONS · READY One order, one physical node

Rent now

Choose Runner M4, one of five regions, and a billing cycle, then confirm storage or Thunderbolt 5 parallel options for your workload.

Start your order

Review the configuration

Check the M4, 16GB RAM, 256GB SSD, four billing cycles, and all add-ons before selecting a node and rental term.

Open the plan page
Use cases

Schedule nodes around your workload—not the other way around

RunnerVM provides dedicated physical Mac nodes. Your team remains responsible for configuring repository policies, signing permissions, dependency caching, and release rules.

CI

iOS / macOS continuous integration

Register the node with your existing CI and isolate working directories by repository. Lock toolchain versions, restrict build-account permissions, and define clear expiration rules for dependency caches.

CI RUNNER
XC

Xcode cloud builds

Confirm your Xcode, SDK, and Command Line Tools versions first. Then import certificates and provisioning profiles, run archive and export, and verify the build artifacts.

XCODEBUILD

Remote development

Use SSH for scripts, dependencies, and background tasks; use VNC when you need a graphical interface. Before disconnecting the remote desktop, confirm that builds are running in a persistent session.

SSH + VNC
AI

AI experiments

Measure peak model memory, disk usage, and data-transfer paths first. Runner M4 suits experiments that fit within a 16GB memory limit; assess capacity before running larger workloads.

EVALUATE FIRST
Build pipeline

A repeatable automated app build pipeline

Pin commits, isolate signing materials, retain complete logs, and verify each exported IPA, dSYM, and archive result.

build-lane / ios-release / current-run Task orchestration

Build lane · ios-release

The commands and directories below illustrate the pipeline structure only; adjust the actual parameters to match your project configuration.

Traceable logs
  1. 01

    Push code

    Check out the pinned commit, verify submodules, and restore dependency caches from the lockfile.

  2. 02

    Inject certificates

    Create a temporary keychain, import certificates and provisioning profiles, and restrict access.

  3. 03

    Run the build

    Run xcodebuild or fastlane while continuously saving standard output and error logs.

  4. 04

    Archive artifacts

    Verify the IPA, dSYM, Archive, and export logs before handing them to the next stage.

$ fastlane ios release --env runner
→ archive/RunnerApp.ipa
→ archive/RunnerApp.app.dSYM.zip
→ checksum verified
Project view

Commands, hardware, and purpose in one checklist

After connecting, verify the host fingerprint, system information, and toolchain versions. Adapt the example commands to your project, certificates, and directory structure.

runner-m4-sg · build session SSH 
developer@local $ ssh runner@sg-m4-node
Host fingerprint verified
Dedicated physical Mac mini

runner@node $ xcodebuild \
  -workspace RunnerApp.xcworkspace \
  -scheme RunnerApp \
  -configuration Release archive
** ARCHIVE SUCCEEDED **

runner@node $ fastlane ios package
[12:43:31] Export RunnerApp.ipa
[12:43:52] Verify artifact checksum
lane completed
The sample output illustrates the connection, archive, and export sequence only. Replace the hostname, directories, scheme, and signing parameters with your project’s actual values.
Hardware label

Runner M4 specifications

Chip
Mac Mini M4
Memory
16GB RAM
Storage
256GB SSD
Connectivity
SSH / VNC
Properties
Dedicated physical Mac mini, not a virtual machine
Selection guide

Choose based on your workload

Light builds
Runner M4
Daily development
Runner M4
AI experiments
Assess the 16GB memory limit, storage, and Thunderbolt 5 parallelization needs first
5 nodes

Start where your team, code source, or dependency mirror is closest

RunnerVM has 5 nodes or data centers worldwide: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East Coast. All listed combinations are generally available to order; live availability is returned by the console.

SG

Singapore

Suitable for Southeast Asian teams, regional code sources, and dependency mirrors. Re-test the route from your actual office network before ordering.

Available

JP

Japan (Tokyo)

Suitable for Japanese and Northeast Asian workflows. We recommend testing both SSH interaction and large-file transfers.

Available

KR

South Korea (Seoul)

Suitable for local Korean development and nearby workloads. Assess cross-border access using p95 latency and route results.

Available

HK

Hong Kong

Suitable for teams connecting to East and Southeast Asian networks. Run additional tests from the network hosting your code source.

Available

US-E

US East Coast

Suitable for US East Coast teams and nearby services. Asian teams should evaluate transoceanic routing and file synchronization.

Available
Node testing

Measured node latency

The sample below shows ICMP ping p50, p95, sampling time, and network operators between nodes. Your team should still retest from its own network.

Five-node test sample

Each route collected 20 consecutive ICMP echo requests at one-second intervals.

20 PACKETS / ROUTE
Test source Target node p50 p95 Sampling time Network operator
Singapore Japan (Tokyo) 67.4 ms 72.8 ms 02:10 UTC Cogent / NTT
Japan (Tokyo) South Korea (Seoul) 31.2 ms 35.9 ms 02:14 UTC IIJ / KT
South Korea (Seoul) Hong Kong 48.6 ms 55.1 ms 02:18 UTC KT / PCCW
Hong Kong Singapore 36.9 ms 42.7 ms 02:22 UTC PCCW / Singtel
US East Coast Japan (Tokyo) 168.3 ms 176.5 ms 02:26 UTC Zayo / NTT
Methodology: ICMP echo requests were sent from the corresponding RunnerVM node and round-trip-time percentiles were calculated. Cross-border routing, local carriers, congestion, and test timing affect results; this table compares paths and does not replace validation on your team’s network.
Only plan available

Runner M4, from $20.3 / day

Mac Mini M4, 16GB RAM, and 256GB SSD, available for daily, weekly, monthly, or quarterly rental. All orders are settled in US dollars (USD).

Available

Runner M4

Mac Mini M4 · 16GB RAM · 256GB SSD

Daily$20.3
Weekly$54.7
Monthly$101.3
Quarterly$275.5
Rent Runner M4 now

Additional storage and Thunderbolt 5 parallelization are billed separately for the selected term. Live node and option availability is returned by the console.

Service status

Daily status over the past 90 days

Target availability, daily status, and verified incidents are presented using the same methodology. All nodes operate continuously 365 days a year.

99.9%

Target availability

Daily records help identify regional network or node incidents but do not replace order- or connection-specific logs.

Daily status for the past 90 days

Each cell represents one calendar day.

Normal

Incident details

Status records include the region, node, start and end times, impact scope, and verification findings. Service credits or compensation are subject to the applicable service terms and final verification.

View service terms
Developer FAQ

Six questions to answer before ordering

Clarify the hardware, connection methods, toolchain boundaries, and order term before moving build workloads to a cloud Mac.

What does a dedicated physical machine mean?

One order corresponds to one dedicated physical Mac mini. The CPU, memory, and local storage come from that device itself; RunnerVM does not describe shared virtual resources as dedicated hardware. After delivery, verify the host information, connection credentials, and system environment first.

How do I connect remotely?

Use SSH for command-line work, dependency installation, and automation, and VNC for tasks that require the macOS graphical interface. On your first connection, verify the host fingerprint, change the initial password, and restrict unnecessary inbound ports.

What should I prepare before delivery?

List your Xcode and SDK versions, project dependencies, certificates, provisioning profiles, build scheme, export configuration, and network requirements in advance. Your team should also decide who can access signing materials and where logs and artifacts will be stored.

What billing cycles are available?

Runner M4 is available daily, weekly, monthly, or quarterly, priced at $20.3/day, $54.7/week, $101.3/month, and $275.5/quarter. The console-confirmed order times, region, and add-ons take precedence.

What happens to data when the order ends?

Move your code, build artifacts, logs, and any caches you need to retain before the order ends. The termination process revokes access credentials and processes device data; your team should also revoke certificates, tokens, and repository permissions.

Which node should I choose?

Prioritize the locations of your team, code source, dependency mirrors, and artifact recipients. Run ping, traceroute, SSH interaction, and file-transfer tests over your real network rather than choosing solely by city distance.

Next build pipeline

Hand your next build to a cloud Mac

Choose Runner M4 and one of five regions, then move Xcode, fastlane, and your existing CI workflow to a dedicated physical node. Contact support if you need to confirm storage, parallelization, or build workflows.

Rent a cloud Mac now Contact support