Dedicated Apple Silicon

Put a real Mac
into your build pipeline

A dedicated Apple Silicon physical node with no host sharing. Xcode builds, tests, and continuous integration jobs run on one continuously manageable cloud Mac.

From $20.5/day and choose daily, weekly, monthly, or quarterly billing. Live availability is reported in the control panel.

3 configurationsSingapore · Tokyo, Japan · Seoul, South Korea · Hong Kong Rent a cloud Mac now
Watch the product demo
PHYSICAL NODE / ONLINE JP-M4-0241
OrbVPS
Mac mini · M4 Dedicated physical node
RUN RECORD ARM64

$ xcodebuild archive

CompileSwiftSources normal arm64

ARCHIVE SUCCEEDED · 06:42

Runner
ONLINE
Unified memory
24GB
Current region
JP
PRODUCTCloud MacFull macOS GUI and command line
ALLOCATIONDedicated physical machineOne fixed host per order
BOUNDARYNot a virtual machineHardware state and toolchain retained
REGIONS4 nodesSingapore · Tokyo, Japan · Seoul, South Korea · Hong Kong
Available configurations

Three Apple Silicon node configurations

Clear options for lightweight builds, continuous integration, and memory-intensive workloads. Prices below cover daily and monthly plans; verify weekly and quarterly rates on the plans page.

Base build

Orb M4 16

m4-16-256

$20.5/ day
  • ChipM4
  • Memory16GB
  • Storage256GB
  • Monthly$102.3
  • Best forSingle-project builds and testing
Choose this configuration
Balanced configuration

Orb M4 24

m4-24-512

$41.6/ day
  • ChipM4
  • Memory24GB
  • Storage512GB
  • Monthly$208.1
  • Best forParallel CI and multi-branch builds
Choose this configuration
Memory-intensive workloads

Orb M4 Pro

m4pro-64-2tb

$60.1/ day
  • ChipM4 Pro
  • Memory64GB
  • Storage2TB
  • Monthly$300.6
  • Best forLarge projects and AI experiments
Choose this configuration

All three configurations are available in Singapore, Tokyo, Seoul, and Hong Kong. Listed combinations are generally orderable; live availability is reported in the control panel.

View full billing-cycle pricing and add-ons
Engineering workloads

Configured for real engineering workloads

No vague compute labels. Every workload maps to a verifiable toolchain, run record, and system metric.

BUILD

Xcode builds

Pin Xcode, runtime, and dependency versions, then retain successful archive logs as a baseline for future changes.

06:42Sample archive duration
Archive
RUNNER

iOS CI/CD

Keep the self-hosted runner on a fixed node and continuously reuse its workspace, dependency cache, and controlled execution environment.

18 JOBSSample queue record
Pipeline
TEST

macOS testing

Retain system settings, permissions, and test data so results before and after upgrades can be verified on the same physical node.

96%Sample test pass rate
Test Suite
MEMORY

AI experiments

Run small models remotely while reading unified memory, processor load, and temperature status to tune workload boundaries.

41.2GBSample memory usage
Memory
DESKTOP

Remote creative work

Use a persistent workspace through a graphical session for tasks that require the macOS interface and remote media processing.

2560×1440Sample display specification
Desktop
ORB RUN RECORD · JP-M4-0241 ONLINE 
$ ssh build@jp-m4-0241.orbvps.node
Host fingerprint verified · Apple M4 · arm64
Session attached to dedicated physical node

$ xcodebuild -workspace OrbApp.xcworkspace \
  -scheme OrbApp -configuration Release archive
ResolvePackageGraph
CompileSwiftSources normal arm64
Ld /Build/Products/Release/OrbApp normal
** ARCHIVE SUCCEEDED **  06:42

$ bundle exec fastlane beta
Reading archive metadata
Uploading build artifact
Writing deployment record
fastlane finished successfully
Verified run record

Commands run on a dedicated physical node

Your SSH address, toolchain, certificates, cache, and workspace stay on the same continuously manageable Mac. The environment is not replaced by temporary resources when a task ends.

  • Verifiable connectionsConfirm the host fingerprint on first login, then save the node ID and connection record.
  • Reproducible buildsPin Xcode, dependency, and runtime versions; use successful logs as the baseline for future changes.
  • Readable statusCheck memory, disk, load, and temperature with system tools instead of relying on abstract quotas.
View first-connection and build steps
Built for operators

Three teams, one controllable node model

Workloads vary, but the decision criteria are the same: fixed hardware, clear regions, verifiable toolchains, and persistent runtime state.

01 / MOBILE

Mobile developers

Keep signing materials, dependency caches, and nightly builds on a fixed node. Continue troubleshooting from the same logs the next day without rebuilding the environment.

02 / PIPELINE

CI/CD teams

Pin the self-hosted runner to a defined node and support controlled pipelines with labels, workspaces, and cache policies.

03 / EXPERIMENT

AI experiment users

Run small models in the unified-memory environment of M4 Pro and directly observe process activity, memory pressure, and temperature changes.

Deployment orbit

Four available nodes on one deployment path

Choose a region based on team location, code repositories, and upstream pipeline services. The catalog covers Singapore, Tokyo, Seoul, and Hong Kong only.

Regions
4 nodes
Runtime
365 days
Catalog status
Listed combinations generally orderable
Choose a node by region Check the configuration matrix
DEPLOYChoose an entry point
SG · 20~50 MSSingaporeFor collaboration across Southeast Asia
JP · 30~60 MSTokyo, JapanFor teams in Japan and East Asia
KR · 30~50 MSSeoul, South KoreaFor teams across Northeast Asia
HK · 20~40 MSHong KongFor collaboration across South China and Southeast Asia
Local workflow, extended

Extend your local development environment to a cloud Mac

Migration is more than copying a repository. Connection methods, toolchain versions, and persistent jobs need verifiable boundaries established step by step.

01 / ACCESS

Start remote access by verifying identity

On first connection, confirm the node ID, address, and host fingerprint. Then configure SSH keys, save recovery details, and verify the graphical session and reconnect behavior.

  • Use SSH for commands, automation, and log collection
  • Use the graphical session for Xcode, system settings, and remote creative work
  • Include the node ID and timestamp when submitting a support ticket for connection issues
ACCESS CHECK
Host fingerprintVERIFIED
SSH keyED25519
Desktop sessionREADY
02 / TOOLCHAIN

Record toolchain versions in the run record

Before the first successful build, record macOS, Xcode, runtime, package manager, and dependency lock-file versions. Before upgrading, copy the baseline and compare the results.

  • Save Xcode and SDK version output
  • Pin Node, Ruby, CocoaPods, and project dependencies
  • Add successful logs and build artifacts to team records
TOOLCHAIN LOCK
XcodePINNED
DependenciesLOCKED
Baseline archiveSAVED
03 / CONTINUITY

Continuous builds depend on a fixed workspace

Keep the runner, workspace, cache, and keys on a defined node. After a failed job, continue checking the state of the same Mac instead of starting with a new environment.

  • Set clear labels and concurrency limits for the runner
  • Use project-based workspaces and cache cleanup policies
  • Run controlled test jobs after a restart to verify recovery
CONTINUOUS BUILD
RunnerONLINE
WorkspacePERSISTED
Recovery testPASSED

“After moving nightly builds to a fixed node, I no longer have to rebuild certificates and caches repeatedly.”

— Mobile engineering lead

“I need a continuously manageable Mac, not a temporary environment.”

— CI engineer

“When running small models remotely, I can see memory and temperature status directly.”

— AI researcher
Engineering notes

From platform principles to actionable steps

Engineering notes on physical-node boundaries, build migration, remote debugging, and version testing.

View all articles
2026-08-11
Platform principles

Audit outbound connections from a cloud Mac CI node

Use lsof, nettop, and tcpdump to capture processes, active connections, and short TCP sessions during a cloud Mac CI build, then create a reviewable baseline.

Read article
Build guide

Diagnosing and Safely Resetting macOS TCC Permissions in Cloud Mac CI

Trace Cloud Mac CI permission failures through the runtime user, GUI session, responsible process, and code signature, then recover safely with tccutil and a correctly scoped LaunchAgent.

Pin dependencies and establish a build baseline Remote workflow

Diagnosing and Safely Releasing CI Tools Blocked by Gatekeeper on a Cloud Mac

Learn to separate permission, architecture, code-signing, and Gatekeeper quarantine failures in cloud Mac CI, then release only a verified artifact after checksum and policy-log checks.

Define the boundaries of local device operations
Selected questions

Clarify service boundaries before buying

Models, regions, billing, permissions, and connection methods are clearly defined. Match the workload first, then choose a configuration.

View all questions
What resources does each order include?

Each order includes one dedicated Apple Silicon physical node: a remotely accessible cloud Mac, not a virtual machine. The host is not shared with other orders.

Which models are currently available?

The catalog includes only three configurations: Orb M4 16 (M4, 16GB, 256GB), Orb M4 24 (M4, 24GB, 512GB), and Orb M4 Pro (M4 Pro, 64GB, 2TB).

Which regions are available for ordering?

Singapore, Tokyo, Seoul, and Hong Kong. All three configurations are available across all four nodes; live availability is reported in the control panel.

Which payment methods are supported?

Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All orders are settled in USD; the payment gateway available at checkout is returned by the backend.

Configure a physical node

Choose a model, region, and rental period

Choose one of three Apple Silicon configurations, then confirm a node in Singapore, Tokyo, Seoul, or Hong Kong. After ordering, manage the service and submit support tickets in the control panel.

Rent a cloud Mac now Contact the team