From order to first build

Enable your Cloud Mac securely and complete delivery checks in about four minutes

Start with your workload, then choose from three catalog machine configurations and six locations. After delivery, verify remote desktop, SSH public-key access, versions, and a test build in order—without guessing between credentials, networking, and the build environment.

Rent a Cloud Mac now View three plans

Catalog configurations: 3 plans
Available locations: 6
Delivery check: About 4 minutes

ACTIVATION MANIFEST

Activation checklist

Path verified

Recommended starting configuration Office M4 Build M4 · 24GB · 512GB

Location selection: Close to your primary operators or code repository
Graphical access: Verify the remote desktop session first
Command-line access: Then upload and test a dedicated SSH public key
Acceptance task: Run one cache-free test build

Choose Order Connect Build

Before you start

Prepare these five items before configuration

Console account

Prepare an email address that can receive verification codes. After signing in, you can view orders, location details, billing, and support ticket status.

Dedicated SSH public key

Generate a separate key pair for this Cloud Mac instead of reusing an old key that has been widely distributed. Keep the private key only on a controlled device.

Remote desktop client

Install a compatible client in advance and confirm that your local network allows access to the location address and port listed in the delivery details.

Xcode and macOS requirements

Record the project’s required Xcode major version, minimum macOS version, dependency manager, and approximate disk space for a complete build.

Target location

Confirm the locations of your primary operators, code repository, and build-artifact recipients. Do not choose a location solely based on your team’s registration address.

Choose a configuration

Work backward from your workload to memory and storage

Light builds START

Office M4 Start

M4 · 16GB · 256GB

$21.7 / day

week$58.6

month$108.5

quarter$295.1

Suitable for maintaining a single project, checking dependencies, light Xcode builds, and low-concurrency scripts. With 256GB of storage, archive and cache cleanup needs to be more proactive.

Choose Office M4 Start

Everyday development and parallel CI BUILD

Office M4 Build

M4 · 24GB · 512GB

$40.3 / day

week$108.9

month$201.7

quarter$548.6

Designed for everyday Xcode development, multiple simulator tasks, self-hosted runners, and medium-concurrency pipelines. 24GB of memory and 512GB of storage provide a more balanced starting point.

Choose Office M4 Build

Inference and heavy workflows PRO LAB

Office M4 Pro Lab

M4 Pro · 64GB · 2TB

$61.1 / day

week$165

month$305.6

quarter$831.2

Suitable for local inference with larger models, heavy builds, parallel multitasking, and high-capacity asset processing. 64GB of unified memory and 2TB of storage reduce the need to move data frequently.

Choose Office M4 Pro Lab

Choose a location

Six locations. Decide using a repeatable path

Singapore

Suitable for Southeast Asian teams, cross-border product maintenance, and everyday remote operations serving Asia-Pacific users.

Choose Singapore

Japan (Tokyo)

Suitable for Japan-based operators, repositories near Tokyo, and development teams that need a stable Asia-Pacific collaboration route.

Choose Japan

South Korea (Seoul)

Suitable for South Korean teams, collaborators near Seoul, and projects running builds continuously across Northeast Asia.

Choose South Korea

Hong Kong

Suitable for cross-border collaboration in East Asia, distributed development, and workflows serving multiple Asia-Pacific operators.

Choose Hong Kong

US-E

US East

Suitable for teams in the eastern United States, code repositories in US East, and Asia-Pacific teams running long tasks overnight.

Choose US East

US-W

US West

Suitable for West Coast developers, projects spanning both sides of the Pacific, and continuous build tasks.

Choose US West

Test the operator path first

Compare candidate locations on the same network, protocol, and similar test window. Record connection setup time and interaction responsiveness.

Then check repositories and artifacts

When pulling many dependencies or uploading build artifacts, the locations of the code repository and recipient may matter more than the operator’s location.

Finally, match working hours

For teams across time zones, develop during the Asia-Pacific daytime and assign long-running tasks on US locations to overnight hours.

Confirm billing

Check the term, extensions, and quantities item by item

Billing checklist

Do not look only at the final total

USD

01
Machine configuration
Verify the machine name, chip, memory, and base storage so added storage is not mistaken for the base specification.
02
Rental term
Confirm whether billing is daily, weekly, monthly, or quarterly. Each term has its own catalog price; do not simply multiply the daily price.
03
Target location
Before submitting, verify Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, or US West once more.
04
Add-ons
Confirm added SSD capacity and the number of Thunderbolt 5 parallel connections. Remove unused options when the quantity is zero.

Payment methods

Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. Actual available gateways are determined by the console.

One final look before submission

The machine, term, location, storage expansion, parallel-connection quantity, and USD total must match in the same order.

Configure and order

USD prices for add-ons by day, week, month, and quarter
Add-on	Daily	Weekly	Monthly	Quarterly
+1TB SSD	$2.6	$7.1	$13.2	$35.9
+2TB SSD	$5.2	$14.2	$26.4	$71.8
Thunderbolt 5 parallel connection (each)	$2	$5.3	$9.9	$26.9

Delivery timeline

Four checkpoints, about four minutes total

Stage 1 About 1 minute

Submit the order

Confirm the machine, term, location, added storage, Thunderbolt 5 parallel-connection quantity, and USD total, then complete payment using an available method.

Order number generated
Machine and location combination recorded

Stage 2 About 1 minute

Register the physical node

The system links the order to a dedicated physical machine. Delivery is a physical node, not a virtual machine, and each order corresponds to the selected catalog configuration.

Device configuration matched
Target location linked

Stage 3 About 1 minute

Generate access details

The console displays the location address, port, account name, temporary credentials, and host fingerprint. Save the order number first; do not forward the complete access details.

Remote desktop details displayed
SSH verification details displayed

Stage 4 About 1 minute

Complete the first connection check

Open the graphical session first to confirm the desktop state, then test the SSH public key. Only after both connections pass should you pull the project and restore the build environment.

Remote desktop session available
SSH host fingerprint verified

Standard activation path 4 stages · about 4 minutes total

If the connection check fails, stop writing project data and verify the local network, location address, port, credential status, and client settings first.

First connection

Graphical interface first, SSH second, credentials updated afterward

Connection 01

Verify remote desktop

Read the location address, port, account name, and temporary credentials from the console. After connecting, confirm that the machine name, location, and order record match, then check the keyboard layout and display scaling.

Desktop loads normally Mouse and keyboard input work normally Session can be resumed after disconnection

Connection 02

Verify the SSH host fingerprint

Before the first connection, compare the host fingerprint shown by the client character by character with the delivery details. If they differ, stop and do not accept the unknown host directly.

ssh -i ~/.ssh/ovps_ed25519 user@host

Connection 03

Upload and test the public key

Use a dedicated key for the Cloud Mac. After confirming public-key login works, disable the temporary credentials and restrict local access to the private-key file.

chmod 600 ~/.ssh/ovps_ed25519
ssh-add ~/.ssh/ovps_ed25519

Connection 04

Record recovery details

Save the order number, location, account name, host fingerprint, and key identifier. Do not write the password or private-key contents in the recovery record.

View the remote connection guide

First workflow

Complete acceptance with one repeatable build

Recommended acceptance order

Read versions first, then pull the code; run a local test build before registering a CI runner. This helps determine whether a failure comes from the project environment or the pipeline configuration.

01

Verify the system and toolchain

Record the macOS, Xcode, command-line tools, dependency manager, and build-script versions. If they do not meet project requirements, adjust the environment first instead of modifying business code.
02

Pull the minimum project scope

Check out the acceptance branch first, then check available disk space and dependency directories. For large repositories, start with a shallow clone and fetch history as needed.
03

Run one test build

Record whether caching was used, the parallel-task count, build command, and start and end times. Do not compare the first cached result directly with later cache-free tests.
04

Connect a self-hosted runner

Limit the projects the runner can access, use a dedicated working directory, run a test task without publishing permissions, and verify that temporary files are cleaned up correctly.

Version-check commands

sw_vers
xcodebuild -version
df -h
git --version

Secure the setup

Complete these six closeout steps after the build passes

Delete temporary files

Clean download folders, temporary archives, debug output, and unneeded installers so sensitive data does not remain in shared paths.

Restrict key sources

Keep only the SSH public keys required by controlled devices in the current team, remove temporary test keys, and record the owner of each key.

Check automatic screen lock

Set a reasonable screen-lock policy for the task and confirm that sensitive windows are not left exposed on the desktop after a remote session disconnects.

Define session exit rules

Define exit behavior for interactive development, unattended builds, and long-running inference to avoid stopping tasks accidentally or leaving orphaned sessions.

Save node records

Record the location, host fingerprint, connection port, and purpose. Do not save passwords or private-key contents. Update the team’s internal register after changes.

Archive order information

Save the order number, machine, term, add-ons, and billing result. When submitting a support ticket later, cite the order number first, followed by the time and reproduction steps.

Ready to begin

Choose a configuration for your real workload, then complete the four-minute activation check

Three dedicated physical-machine tiers cover Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West. Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported, and all billing is in USD.

Rent a Cloud Mac now View configurations and pricing