Dedicated physical Mac mini
A remote Mac desktop for iOS and macOS development, automated builds, AI experiments, and audio/video processing. Each order includes dedicated chip, memory, storage, and system access, with connection available about four minutes after payment confirmation.
Remote access
Use the remote Mac desktop when you need a graphical interface, and SSH for scripts and pipelines. Choose macOS Screen Sharing or a compatible VNC client based on your local device and network.
Access the full graphical interface from another Mac for Xcode debugging, dependency setup, signing, archiving, and development tasks that require live status visibility.
Before connecting for the first time, prepare the node address, system account, and temporary credentials. After connecting, update the credentials and verify keyboard layout, resolution, and clipboard behavior.
NATIVE CLIENT / INTERACTIVE
Use VNC from Windows, Linux, or another compatible client to operate your cloud Mac. Ideal when you need Mac remote access but your local environment is not macOS.
If latency increases, reduce resolution, color depth, and frame rate in that order, and pause large background file transfers. For interactive work, choose a node closer to your client.
CONFIGURABLE QUALITY
Run scripts, xcodebuild, fastlane, or a self-hosted runner with key-based authentication. Ideal for CI/CD, batch testing, and unattended builds.
For automation, use a dedicated working directory, pin tool versions and cache paths, and check build logs, key permissions, and exit codes.
KEY AUTH / AUTOMATION
Resource boundary
This is neither a shared instance nor partitioned virtual capacity. Each tenant gets exclusive use of the Mac mini’s chip, memory, local storage, and system environment; no other tenant enters the same resource boundary.
M4 Core plan
M4 Core is the current fixed model. Daily, weekly, monthly, and quarterly terms use the same hardware; only the rental period changes. Actual regional availability is confirmed by inventory at checkout.
MAC MINI M4 · 16GB RAM · 256GB SSD
| Add-on | Day | Week | Month | Quarter |
|---|---|---|---|---|
| +1TB SSD | $2.7 | $7.2 | $13.3 | $36.2 |
| +2TB SSD | $5.4 | $14.4 | $26.6 | $72.4 |
| Thunderbolt 5 link / per Mac | $1.1 | $3 | $5.5 | $15 |
Thunderbolt 5 linking is suited to workflows that coordinate multiple physical nodes, such as split builds, parallel testing, or high-speed transfers between nodes. Confirm device count, software scheduling, and data-sync paths before ordering.
Timeline steps
The times below describe a typical automated delivery flow. Inventory, payment confirmation speed, and current initialization status affect the actual completion time.
Verify the order amount, USD settlement details, and payment status.
Reserve an available physical Mac mini in the selected region.
Prepare the macOS environment, system account boundary, and remote access services.
Issue temporary credentials and record connection details in node management records.
Complete the initial access check using Screen Sharing, VNC, or SSH.
$ ssh minid@jp-tyo.node Authenticating with public key... MiniDeploy physical node / M4 macOS 15.x · arm64 · status: ready $ xcodebuild test -scheme App Resolve Package Graph CompileSwiftSources normal arm64 ** TEST SUCCEEDED ** $ fastlane upload Uploading signed archive... ✓ Build delivered
Use cases
From task inputs through cloud execution to artifact output, teams configure tool versions, caching, working directories, and account permissions according to their engineering standards.
Open Xcode remotely for dependency installation, debugging, signing, archiving, and TestFlight distribution. Ideal for developers without a continuously available local Mac.
View the development workflow →Register a self-hosted runner, run tests, xcodebuild, and fastlane, and send logs and artifacts back to your existing pipeline.
View the build workflow →Set up Python, dependencies, and model environments to run local inference on dedicated Apple Silicon resources while recording latency, memory, and throughput.
View the experiment workflow →Sync proxy media first, then edit, render, and encode remotely before returning output files to team storage, avoiding large source-file transfers during interactive work.
View the media workflow →Migrate code, dependency manifests, and required media. Handle keys, signing materials, and production configuration separately, then verify permissions after transfer.
Pin Xcode, SDK, package manager, and build component versions, then validate a reproducible build from the same commit.
Register the runner, isolate the working directory, set cache cleanup rules, and check build certificates, exit codes, and log retention.
Regions & latency
Available regions include Singapore, Tokyo, Seoul, Hong Kong, and the western United States. For remote desktops, prioritize round-trip latency; CI/CD also depends on repository, dependency-source, and artifact-storage locations.
| Model | SG | JP | KR | HK | US-W |
|---|---|---|---|---|---|
| M4 Core |
| Client city | SG | JP | KR | HK | US-W |
|---|---|---|---|---|---|
| Shanghai | 78ms | 43ms | 46ms | 31ms | 151ms |
| Taipei | 66ms | 34ms | 52ms | 24ms | 128ms |
| Los Angeles | 174ms | 112ms | 139ms | 151ms | 29ms |
ICMP RTT · residential local carriers · 20:00–22:00 · median of 10 measurements per route. Data compares node directions; actual results vary with client connection, routing, and time of day.
Check node inventory and latency →Control & billing
The console is the central entry point for resource operations. Choose a node, term, and add-ons before ordering; after delivery, view connection details and renew or manage the resource during the rental term.
Use the console to order, renew, view node connection details, and manage existing resources.
Payment facts
Order prices and add-ons are displayed in USD. The available gateway is determined by the console response.
After selecting USDT-TRC20, pay using the details shown for the order. Verify the network, amount, and order status before submitting, then wait for payment confirmation before node allocation begins.
Visa, Mastercard, and Amex payments are processed by Stripe. Orders remain settled in USD, and the physical node in the selected region is reserved after payment confirmation.
In short:Only USDT-TRC20 and Visa / Mastercard / Amex via Stripe are supported. Every order is settled in USD.
Knowledge updates
From remote desktops and Xcode builds to CI/CD and Apple Silicon experiments, we document reproducible technical workflows with test conditions, step-by-step procedures, and practical limits.
A reproducible workflow for correlating build output with system events, filtering noise, and preparing a sanitized diagnostic archive.
Read on the blog →Connect a cloud Mac to an API on your development computer without publishing it to the internet. Follow the SSH setup, verification steps, and failure checks.
Read the article →Decouple long builds, tests, and processing jobs from the SSH connection, then recover the same tmux session and verify the result after a disconnect.
Read the article →Glossary mini
These terms distinguish hardware boundaries, connection protocols, and automated execution methods, making it easier to describe the same setup when ordering or troubleshooting.
Selected FAQ
Confirm the resource type, delivery time, payment options, node selection, and first-connection requirements before deciding whether it fits your workload.
Ready when allocated
Check the M4 Core specs, node, rental term, and add-ons on the plans page first. Visit the support page when you need to verify connection tools and credential requirements.