All four physical nodes available · From $21.3/day

Keep your Mac tasks running
on a dedicated physical machine

Launch an Apple Silicon cloud Mac on demand for continuous Xcode builds, automated testing, AI experiments, and media processing. Every order includes one dedicated physical machine—not a virtual machine.

SOARMAC OPERATIONS Task departure board
PHYSICAL NODES · ONLINE
Build task / Current step Term Node Machine allocation Delivery
iOS Release · 4.18.0archive → signing → export
MONTHLY
JP · TYO
M4 PLUS · 24GB
Delivered
UITest · checkout-flowxcodebuild test · 142/142
WEEKLY
SG · SIN
M4 AIR · 16GB
Running
ML Experiment · vision-07checkpoint · epoch 38/60
QUARTER
HK · HKG
M4 PRO · 64GB
Connected
Media Batch · export-proresrender queue · 18 assets
DAILY
KR · SEL
M4 PLUS · 24GB
Processing
CI Runner · ios-prod-03self-hosted · dedicated label
MONTHLY
JP · TYO
M4 PRO · 64GB
Schedulable
RUNNER connection check
label
macos-m4
scope
repository
cache
restored
session
verified
Delivery record · SM-42871
Node
JP-TYO
Configuration
M4 / 24GB / 512GB
Term
MONTHLY
Status
READY
Dedicated physical machine Every order includes one dedicated Apple Silicon Mac with no shared compute resources.
Not a virtual machine Verify the chip, memory, storage, and system details after delivery.
M4 Apple Silicon Three fixed M4 and M4 Pro configurations are available; no unlisted models are offered.
04 4 nodes Singapore, Tokyo, Seoul, and Hong Kong are all available to order.
USD From $21.3/day Orders, renewals, and machine management are handled in the console.
Fits your existing workflow

No need to replace the tools your team already knows

Use a cloud Mac as a remote development host or register it as a dedicated self-hosted runner in your existing CI/CD pipeline. Your team remains in control of tool versions, labels, caches, and concurrency policies.

XXcodeBuilds and testing
GHGitHub ActionsDedicated Runner
GLGitLab CILabel-based scheduling
JJenkinsNode executor
FFastlaneAutomation workflows
RARemote access toolsGUI and command line

After delivery, verify the system version, Xcode version, command-line tools, and project-directory permissions before registering the runner. Your team configures signing materials, secrets, and post-task cleanup according to least-privilege principles.

How cloud Macs work

Keep tasks running without tying up your desktop

Choose a model, term, and physical node, and SoarMac handles machine allocation and delivery. Reproduce your development toolchain, register a self-hosted runner, or leave long-running experiments and export jobs running.

  • Continuous buildsBind a fixed label to a dedicated runner, reuse dependency caches, and limit concurrency.
  • Temporary testingCreate an isolated environment by the day or week, then move out the results after validating the release.
  • AI experimentsRun long jobs on a high-memory configuration and save checkpoints by stage.
  • Media processingSync source media remotely, run batch processing and exports, then deliver the results to team storage.
RESOURCE ASSIGNMENT

Resource status

M4 PRO · HK
64GBUnified memory
2TBSSD
1 / 1Machine assigned to order
RENTAL PERIOD

Current term

QUARTER

Term changes and renewal prices are shown before confirmation—no hidden fees behind vague packages.

DELIVERY CHECKPOINT

Delivery progress

READY
Machine allocation Credential verification Runner connection
Choose by workflow

Four task types, checked step by step from input to execution to output

Whether a cloud Mac is the right fit depends less on broad performance claims and more on whether your task can be reproduced, run continuously, and produce portable results.

Independent developers

From code commit to signed package

Input
Code repository, dependency lockfiles, signing materials, and target build configuration.
Run
Restore dependencies and caches, run Xcode Archive, verify signing, and export the installable package.
Result
Downloadable build artifacts, logs, and details for locating failed steps.
Code commitBuild and signExport artifacts
CI teams

Connect a self-hosted runner

Input
Pipeline definition, runner registration details, dedicated labels, and cache directories.
Run
Register the executor, set concurrency limits, inject required secrets, and clean up after each task.
Result
Build tasks reach the assigned physical machine by label, while logs return to your existing CI system.
Register RunnerLabel schedulingReturn results
AI experiments

Keep long-running jobs and checkpoints

Input
Experiment code, datasets, dependency environment, checkpoint directory, and evaluation scripts.
Run
Run experiments continuously on the 64GB M4 Pro tier, save checkpoints on schedule, and monitor resource pressure.
Result
Keep experiment logs, staged artifacts, and checkpoint files ready for continued execution.
Sync dataRun long jobsSave checkpoints
Media teams

Remote batch processing, export, and delivery

Input
Source media, export presets, batch-processing scripts, and team delivery directory.
Run
Sync media, run transcoding, rendering, or batch exports, and continuously record task status.
Result
Sync finished files, verification data, and processing logs to team storage.
Sync mediaBatch exportTeam delivery
Three dedicated physical machines

Configurations and four billing terms, shown upfront

All three are dedicated Apple Silicon physical machines, not virtual machines. Daily, weekly, monthly, and quarterly prices are listed in USD for easy comparison before you choose a term.

Light development and builds

SoarMac M4 Air

M4 · 16GB RAM · 256GB SSD
$21.3 / day
Daily$21.3
Weekly$57.4
Monthly$106.3
Quarterly$289.1

Ideal for personal development, temporary testing, single-task builds, and light CI.

Order SoarMac M4 Air
High-load workflows

SoarMac M4 Pro

M4 Pro · 64GB RAM · 2TB SSD
$60.1 / day
Daily$60.1
Weekly$162.4
Monthly$300.7
Quarterly$817.9

Ideal for large projects, AI experiments, long-running jobs, and high-memory workflows.

Order SoarMac M4 Pro

Need to compare additional storage, Thunderbolt 5 linking, and the full bill structure for different terms?

View complete plans and add-ons
Four physical nodes

Choose a node near your primary users

SoarMac M4 Air, SoarMac M4 Plus, and SoarMac M4 Pro are available in Singapore, Tokyo, Seoul, and Hong Kong. Actual availability is returned in real time by the console.

SG · SINAvailable

Singapore

Ideal for development hosts, CI runners, and remote processing tasks accessed from Southeast Asia.

Region
Southeast Asia
Catalog configurations
3 tiers
Choose the Singapore node
JP · TYOAvailable

Japan (Tokyo)

Ideal for accessing graphical interfaces, build logs, and test results from Japan and East Asia.

Region
East Asia
Catalog configurations
3 tiers
Choose the Tokyo node
KR · SELAvailable

South Korea (Seoul)

Ideal for continuous builds and remote collaboration workflows accessed from Korea and Northeast Asia.

Region
Northeast Asia
Catalog configurations
3 tiers
Choose the Seoul node
HK · HKGAvailable

Hong Kong

Ideal for accessing development environments and transferring task results from South China and Southeast Asia.

Region
South China and Southeast Asia
Catalog configurations
3 tiers
Choose the Hong Kong node
Measured operating data

Assess node latency separately from service targets

Latency data helps with initial node selection before ordering; it does not replace real network testing after delivery. Teams should remeasure using their own office network, VPN path, and target repository.

NETWORK SAMPLE

Measured node latency

Test window: weekdays 14:00–16:00 UTC · public broadband in each city · 30 ICMP samples per group · median shown

Median ping from major access cities to the four available SoarMac nodes
Access city Singapore Tokyo Seoul Hong Kong
Singapore 12 ms 72 ms 84 ms 39 ms
Tokyo 69 ms 9 ms 31 ms 48 ms
Seoul 78 ms 29 ms 8 ms 43 ms
Hong Kong 36 ms 46 ms 41 ms 7 ms
How to use

First compare the row for your team’s main access city, then choose a node based on your repository, artifact storage, and collaborator locations.

Factors

Provider routing, cross-border links, VPNs, wireless networks, and peak-time congestion can all change actual results.

SERVICE OBJECTIVE

Observed over the last 90 days

Availability is calculated according to the scope of service impact and measurement method defined in the service terms.

99.9%Service availability target
90 daysRolling observation period
365 daysNode operating normally
4 nodesUnified measurement method

For eligible service impacts, we retain an incident timeline and provide compensation according to the scope, claim window, and calculation method in the service terms. User actions, network paths, and events outside our responsibility are handled within the stated terms.

USD billing

Start validating your workflow with one dedicated physical machine

Choose one of three models, a term, and one of four available nodes. We support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe); available payment gateways are returned by the console.