From Order to First Build

Connect to a Cloud Mac in about 4 minutes

Choose your configuration and region, then place the order, retrieve connection details, and validate the development environment. Each instance is one dedicated physical Mac mini, not a virtual machine. Use the live console status as the source of truth for initialization progress.

Rent a Cloud Mac Now Review Configuration & Pricing

2 configurations available

4 regions available

About 4 minutes to complete the basic validation

GPUMini Delivery Runbook First Connection Check

Verifiable Process

Physical Node 1 Mac mini per instance

Configuration: GPUMini M4 Core / GPUMini M4 Plus
Regions: Singapore / Tokyo, Japan / Seoul, South Korea / Hong Kong
Delivery: Host details, connection credentials, and instance status

01Choose a configuration and termConfirm memory, storage, and task duration
02Choose an access regionPrefer the region with the lowest measured latency
03Connect and validateCheck SSH, desktop access, and the build toolchain

Before You Start

Prepare five details to avoid switching back and forth during setup

You do not need extensive documentation before starting, but you should know who will receive the credentials, where the project will run, how long you expect to use the instance, and how you will connect locally. Once these details are ready, you can complete plan selection and initial validation in one pass.

Credential Delivery Email

Use an address that reliably receives mail and is controlled by the responsible administrator. After receiving the delivery details, verify the hostname, region, and rental configuration first. Do not forward credentials to public groups or project logs.

Target Region

Choose from Singapore, Tokyo, Japan, Seoul, South Korea, and Hong Kong. Do not judge by city name alone: test each region from your everyday office network, then record median latency and connection stability.

Planned Rental Term

Evaluate daily or weekly terms for short-term troubleshooting or one-off builds. Monthly or quarterly terms are generally better for ongoing development, cache reuse, and long-running tasks. The final amount is the itemized total shown on the order confirmation page.

Remote Connection Tools

Prepare an SSH client at minimum, plus a compatible remote desktop client if you need a graphical interface. Confirm that your local network allows the required connections, and do not store credentials long-term on shared devices.

Project Development Environment

Record the Xcode version, command-line tools, Fastlane dependencies, repository access method, and expected disk growth. If you need multiple toolchains, list the minimum runnable versions and test commands first.

Choose a Plan

Choose by memory, storage, and build intensity—not by plan name

Both plans provide a dedicated physical Cloud Mac node. The main differences are memory and local storage. Start with your project’s actual peak usage, then account for cache and artifact growth during the planned rental term.

Lightweight Tasks & Short-Term Validation

GPUMini M4 Core

m4-16-256

M4 16GB RAM 256GB SSD

Best for:Single-project development, feature validation, command-line builds, and short-term compatibility checks.
Measure first:Peak memory during a full build, plus DerivedData and dependency-cache usage.
Upgrade signal:Persistent memory pressure, or required build artifacts cannot be retained even after clearing caches.

Choose GPUMini M4 Core

Everyday Development & Heavier Builds

GPUMini M4 Plus

m4-24-512

M4 24GB RAM 512GB SSD

Best for:Continuous development, dependency-heavy projects, larger caches, automated builds, and long-running tasks.
Measure first:The combined peak of parallel tasks, simulator usage, build caches, and exported artifacts.
Why choose it:More memory and local storage reduce the need to clear caches and rebuild during peak workloads.

Choose GPUMini M4 Plus

Start with Core Repeatable tasks, known peaks, and manageable caches

Prefer Plus Ongoing development, many dependencies, parallel builds, or large artifacts

Still unsure Record the memory and disk peaks of one complete build, then choose a configuration

Choose a Region

A nearby region is not always faster—measure from the same network first

All four regions offer GPUMini M4 Core and GPUMini M4 Plus. Test repeatedly from your primary office network, using median latency, jitter, and packet loss together. Do not rely only on the single lowest result.

Reference Guide to the Four Available Regions
Region	Primary Reference Area	Reference Latency	Available Plans	Order
SingaporeSG	Southeast Asia access and cross-region collaboration	20–50 ms	Core / Plus	Choose Singapore
Tokyo, JapanJP	Japan and East Asia access	30–60 ms	Core / Plus	Choose Tokyo
Seoul, South KoreaKR	South Korea and Northeast Asia access	30–50 ms	Core / Plus	Choose Seoul
Hong KongHK	Southern China and Southeast Asia access	20–40 ms	Core / Plus	Choose Hong Kong

Step 1

Use a Consistent Test Network

Test on the wired or stable wireless network you actually use for work. Pause temporary downloads and bandwidth-heavy sync jobs so local congestion is not mistaken for a region problem.

Step 2

Record Multiple Results

Observe multiple requests for each region and record median latency, variation, and packet loss. Remote desktops prioritize stability; automated builds should also account for the location of your code source.

Step 3

Choose Based on Primary Users

For individual use, prioritize your everyday access location. For teams, compare member distribution, repository location, and where automated tasks are initiated.

The ranges in this table are for initial screening and are not fixed results for every network. Carrier routing, local networks, cross-region paths, and test timing all affect actual connection quality.

Delivery Timeline

Validate the four actions separately to pinpoint issues faster

Under normal conditions, basic connection validation takes about 4 minutes from configuration to completion. Initialization time may vary with the selected configuration and live task progress. The instance status shown in the console is the final authority.

About 4 minutes Configuration, ordering, initialization, and connection validation

01

Choose Configuration
About 30 seconds

Confirm GPUMini M4 Core or GPUMini M4 Plus, then choose a daily, weekly, monthly, or quarterly term. Check that memory, storage, and add-ons match your task requirements.
Completion: The order configuration summary matches your expectations.
02

Place the Order
About 1 minute

Choose Singapore, Tokyo, Japan, Seoul, South Korea, or Hong Kong, review the term, base plan, and add-ons, then submit the order.
Completion: The corresponding order and instance record appear in the console.
03

Initialize the Node
About 2 minutes

Wait for the system to configure the node and prepare connection details. Do not submit repeated orders or use information from an old page to judge failure while the status is still changing.
Completion: The instance status and host connection details can be verified in the console.
04

Verify the Connection
About 30 seconds

Verify the host details first, then try SSH or the remote Mac desktop. On the first connection, check the host fingerprint or connection target to avoid reaching the wrong address due to a copying error.
Completion: You can establish a session and read the system time and disk space.

First Login

Confirm machine identity and basic status before syncing code and dependencies

The first session is not for starting development immediately. Confirm that the host, configuration, time, and storage match the order. After the basic checks, update the credentials and sync the project.

Basic First-Session Checks

Three commands to verify the system, time, and disk

The following commands only read local system information. Save the output with the console configuration and region records in the delivery acceptance report.

sw_vers
date
df -h /

Development Environment Validation

Check the connection, tools, and project layers in order

Do not run the full pipeline first. Confirm the basic connection, then validate Xcode and the command-line tools, and finally run a controlled, repeatable project build. This makes it easier to identify the failing layer.

SSH

Verify the address, account, host confirmation, and command execution. After connecting, read the system version and disk information.

Pass criteria: The session is stable and commands return successfully.

Remote Mac Desktop

Verify the graphical session, display resolution, local input, and reconnection. Start with conservative image quality to observe interaction latency.

Pass criteria: The display is usable and the session can be restored after disconnection.

Xcode

Confirm that the required version launches, the project opens, and the build settings and toolchain paths match expectations.

Pass criteria: Project indexing completes without environment-level errors.

xcodebuild

Query the version and available schemes first, then run one clearly defined test-build command and save the exit code and key logs.

Pass criteria: The command runs repeatedly with consistent results.

Fastlane

Check the Ruby environment, dependency installation, and lane list. Start with validation tasks that do not involve production release.

Pass criteria: Dependencies resolve normally and the target lane is recognized.

Repository Access

Verify the repository host, SSH key permissions or controlled-token configuration, and access to project submodules and dependency sources.

Pass criteria: You can pull the specified branch without exposing credentials.

Recommended Minimum Validation Sequence Read versions first, list project targets next, then run a test build

ssh user@host
xcodebuild -version
xcodebuild -list -project YourProject.xcodeproj
fastlane lanes

Delivery Acceptance

Leave a run record that others can reproduce

An acceptance record should not simply say “works.” It should specify the region, configuration, connection method, project location, and the build command that ran successfully.

GPUMini Node Acceptance Form

Initial Delivery Record

Archive After Completion

Region: One of Singapore / Tokyo, Japan / Seoul, South Korea / Hong Kong
Configuration: GPUMini M4 Core or GPUMini M4 Plus
Login Method: Record whether SSH, the remote Mac desktop, or both were verified
Project Path: Record the working directory without entering sensitive credentials in the acceptance form
Test Build: Record the command, scheme, exit code, and log storage location
Disk Baseline: Record available space before and after syncing the project to track future growth

Pass Condition

One Repeatable Build

Run validation repeatedly with the same code version, command, and build target. Results should be reproducible, with no blocking errors caused by missing environment components.

If Support Is Needed

Submit Actionable Details

Prepare the region, time of occurrence, connection method, reproduction steps, error messages, and sanitized logs. For order, instance, and billing issues, submit a ticket through the console first.

Submit a Ticket in the Console

Next Steps

Choose a configuration and region, then deploy and complete your first validation

See the remote connection guide when you need graphical session setup. For build, network, or billing issues, visit the Help Center. When ready, rent a Cloud Mac directly.

Rent a Cloud Mac Now View the Remote Connection Guide Visit the Help Center