Dedicated Apple Silicon physical node

Turn iOS builds from local waiting into a cloud pipeline.

OakVM provides Mac Mini physical nodes that connect directly to existing CI/CD workflows for iOS and macOS teams. Each order includes one dedicated device for Xcode, Fastlane, self-hosted runners, command-line builds, and remote debugging.

  • Not a virtual machine
  • About 4-minute delivery
  • All prices in USD
OakVM cloud Mac build workspace background
RUN RECORD 3 min 42 sec Example of the latest archive duration
BUILD LEDGER ios-release / task 0281 node-hk-m4-06

$ git checkout release/2.8.0

HEAD is now at 4f70c2a release metadata

$ bundle exec fastlane ios archive

[11:24:07] Resolving Swift packages...

✓ Dependencies restored from node cache

$ xcodebuild -workspace App.xcworkspace \\

  -scheme App -configuration Release archive

CompileSwiftSources 100%

✓ ARCHIVE SUCCEEDED 03:18

Signing identity: Distribution certificate ••••••••

Exporting IPA 100%

✓ EXPORT SUCCEEDED

artifact/App-2.8.0.ipa 184.7 MB

Uploading symbols and sanitized build log...

✓ ARTIFACT STORED

M4 Mac Mini / Dedicated node16GB · 256GB · HK

Connect your existing toolchain without rewriting the entire pipeline.

These workflow labels illustrate compatibility scenarios only and do not imply endorsement of OakVM by the referenced tools or platforms.

XC

Xcode

Run command-line builds, archives, signing checks, exports, and symbol-file organization.

GT

Git

Check out the target branch, pin the commit version, and preserve the code baseline for each task.

FL

Fastlane

Reuse existing lanes to turn testing, archiving, and artifact handling into repeatable tasks.

SR

Self-hosted runner

Use runner labels to schedule macOS jobs on a designated physical node.

VN

VNC

Perform remote checks when a graphical interface is needed, while keeping routine automation on the command line.

TF

TestFlight

Connect exported build artifacts to your team's existing test distribution workflow.

6 Available node regions Covering collaboration time zones across Asia and the eastern and western United States
2 Apple Silicon configurations available M4 and M4 Pro, both dedicated physical nodes
About 4 minutes Standard delivery process From payment confirmation to the first connection check
Day / week / month / quarter Four rental terms Choose by task frequency without changing hardware ownership

Connect a dedicated Mac node to your existing iOS build farm.

Keep your existing code repository, workflow orchestration, and artifact storage. Schedule only the macOS, Xcode, and Apple Silicon stages to OakVM.

PUSH / 01

Push code

Merge the target branch and record the commit hash. Repository access, review rules, and branch protection stay in your existing system.

Input
Target branch, commit version, build parameters
Acceptance
The node can fetch code with least-privilege access
TRIGGER / 02

Trigger remotely

Trigger jobs with self-hosted runner labels, a task queue, or SSH commands, avoiding competition with stages that do not need macOS.

Input
Runner labels, task ID, timeout policy
Acceptance
Only the target pipeline enters the Mac queue
EXECUTE / 03

Execute on a physical node

Call xcodebuild or Fastlane on a dedicated Mac Mini to resolve dependencies, test, archive, check signing, and export.

Input
Xcode version, scheme, export configuration
Acceptance
The same commit can be rebuilt with fixed commands
STORE / 04

Archive artifacts

Return the IPA, xcarchive, symbol files, and sanitized logs. Keep caches separate from production artifacts for easier cleanup and traceability.

Output
Build artifacts, verification results, duration records
Acceptance
The task ID maps to the complete artifact set

Start with a non-production branch: fetch, build, archive, and return the artifacts. Then migrate release jobs. This validates network access, the toolchain, signing assets, and artifact storage separately instead of troubleshooting four boundaries after one failure.

From $20.3/day

Choose between two configurations based on build load and peak memory.

OakVM M4 suits regular iOS packaging, automated testing, and single-pipeline jobs. OakVM M4 Pro is built for large workspaces, parallel tasks, AI experiments, and higher local storage throughput.

Both plans support Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the eastern United States, and the western United States. Live availability is returned by the console.

View full pricing and add-ons
REGULAR PIPELINE

OakVM M4

M4 · 16GB RAM · 256GB SSD

$20.3 / day
$54.9 / week $101.7 / month $276.6 / quarter
  • Regular iOS packaging and automated testing
  • Single-pipeline build jobs
  • A stable, repeatable fixed environment
Rent OakVM M4

Choose from 6 node regions by collaboration time zone.

Regions primarily affect remote access paths and team handoff time zones, not the build performance of an individual node. Both OakVM M4 and OakVM M4 Pro are available in all six regions.

OakVM six-node route map The route map shows six regions: Singapore, Tokyo, Seoul, Hong Kong, the eastern United States, and the western United States. SG JP KR HK US-E US-W NODE ROUTE / UTC COVERAGE 06 REGIONS
Nodes run normally 365 days a year with continuous availability; live status is returned by the console.
SG

Singapore

Well suited to Southeast Asian collaboration time zones and handoffs across Asian teams.

Available
JP

Japan (Tokyo)

Well suited to East Asian collaboration time zones and Japan-based development teams.

Available
KR

South Korea (Seoul)

Well suited to Northeast Asian collaboration time zones and cross-region task handoffs.

Available
HK

Hong Kong

Well suited to remote access from teams in southern China and Southeast Asia.

Available
US-E

Eastern United States

Well suited to collaboration time zones across eastern North America and Western Europe.

Available
US-W

Western United States

Well suited to teams on the US West Coast and across the Pacific.

Available

Migrate from a local Mac by validating data, the toolchain, and CI access.

Do not copy an entire development machine first. Define what must move, which versions must be pinned, and which jobs belong on a cloud Mac to shorten the troubleshooting path for your first pipeline.

01 / DATA

Define data and permission boundaries first

Separate source code, dependency caches, signing assets, build artifacts, and logs. Caches can be rebuilt; production artifacts need independent archiving, and sensitive assets should be exposed only to necessary jobs.

Acceptance checklist

  • The node can access the target repository with least privilege
  • Signing assets are managed separately from regular project files
  • IPA, xcarchive, and symbol files can be backed up independently
02 / TOOLCHAIN

Pin a repeatable build toolchain

Record the versions of Xcode, SDKs, command-line tools, package managers, and critical dependencies. Put repeatable commands in scripts to reduce ad hoc GUI operations.

Acceptance checklist

  • Xcode matches the SDK version required by the project
  • Command-line builds still complete after clearing caches
  • Dependency lockfiles and cache invalidation rules have been verified
03 / CI ACCESS

Connect CI last and isolate jobs

After registering a self-hosted runner, use labels to distinguish projects, priorities, and environments. Queue rules—not manual conventions—should determine which jobs a node runs at the same time.

Acceptance checklist

  • Only target jobs are scheduled on Mac nodes
  • Failure logs have been sanitized for sensitive information
  • Build artifacts can be returned to the existing artifact repository

“Release handoffs no longer depend on one Mac in the office. The next time zone can continue from the same task record.”

Mobile lead · Cross-time-zone app team

“Once runner labels map projects to nodes, the build environment is easier to verify than a personal computer.”

Release engineer · CI/CD team

“Remote experiments retain fixed dependencies and records, so changing locations does not require rebuilding the Apple Silicon environment.”

Machine learning engineer · AI experimentation user

The content above illustrates role-specific concerns in typical workflows and does not constitute a rating or performance commitment. Actual duration depends on project size, dependency state, node region, and network access.

Before you order

Confirm node ownership, integration methods, and payment boundaries first.

Before ordering, teams should confirm peak memory, cache usage, concurrent jobs, target region, and rental term. For signing assets, also define responsibility for import, rotation, backup, and cleanup at release.

Open the operations guide
Is an OakVM node a virtual machine?

No. Each order corresponds to one dedicated Apple Silicon Mac Mini physical node. Hardware specifications depend on the selected plan, and compute resources are not shared with other customers.

Can it connect to an existing CI/CD system?

Yes. Teams can trigger nodes with self-hosted runners, task queues, or SSH commands, and isolate projects with labels, working directories, and queue policies.

What are the starting price, billing currency, and payment methods?

The starting price is $20.3/day, and all orders are billed in US dollars (USD). Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported; actual gateway availability is determined by the backend.

Who backs up signing assets and build artifacts?

Users are responsible for authorization, secure management, and backups of their code, certificates, provisioning profiles, private keys, and build artifacts. Provide only sanitized logs when submitting a support request; never paste credentials on a public page.

Do nodes stop running on a regular schedule?

All nodes run normally 365 days a year with continuous availability. User actions, network conditions, force majeure, and other boundaries are governed by the terms of service.

DEDICATED PHYSICAL NODE

Give your next iOS build a dedicated physical Mac.

OakVM provides non-virtualized Apple Silicon nodes in two configurations across 6 regions, with day, week, month, and quarter rentals billed in USD. Order for your task cycle or have your team review the region and configuration.