From Order to Verifiable Build

Rent a Cloud Mac and Complete Your First Build

Start by defining your workload, then choose a tier from Lemon M4 or Lemon M4 Pro. Confirm a node in Singapore, Tokyo, Seoul, Hong Kong, or the US West, and select a daily, weekly, monthly, or quarterly rental. You receive a dedicated Mac mini physical node with hardware reserved for you—not a shared server or virtual machine.

Models 2 tiers

Nodes 5

Terms 4 options

Rent a Cloud Mac Now Compare the Two Tiers

Before you begin, prepare an email address that can receive notifications. Note your use case, expected runtime, primary access location, and the amount of data to retain. Actual availability is determined by the live status returned in the console.

LEMON SLICE / START First Build Checklist

Path Ready

SG Singapore Southeast Asia access

JP Tokyo Japan and East Asia

KR Seoul Korea and Northeast Asia

HK Hong Kong Southern China and Southeast Asia

US-W US West North American West Coast

Physical Node: Dedicated Mac mini
Connection Methods: SSH / VNC
Starting Price: $19.8/day
Acceptance Goal: Successful test build

First-Order Checklist

Make These Six Decisions Before Ordering

This checklist helps eliminate the most common configuration mistakes. Answer every line clearly before starting setup.

01 Define Your Use Case

State whether you need remote development, Xcode builds, CI/CD, AI prototyping, or audio/video processing, and estimate the duration of each task.

02 Choose a Node

Prefer a location close to your main operators or your code and media sources; do not judge network performance by the server name alone.

03 Verify the Model

The base tier includes M4, 16GB, and 256GB; the higher tier includes M4 Pro, 64GB, and 2TB. Choose based on peak memory use and local data volume.

04 Choose a Rental Term

Use a daily or weekly term for short-term validation. For continuous development and stable build queues, compare monthly and quarterly terms before confirming billing.

05 Confirm Add-ons

Choose +1TB SSD or +2TB SSD based on your working set. If you need high-speed multi-node connections, also confirm the number of Thunderbolt 5 links.

06 Prepare Payment

We accept USDT-TRC20 or Visa, Mastercard, and Amex through Stripe. All orders are settled in USD.

Step One

Confirm Your Configuration and USD Bill

Once you enter the configuration flow, choose the model first, then select a node from that model’s catalog, along with the billing term and add-ons. The live availability shown on the page is the final basis for submitting your order.

Before payment, check the model name, chip, memory, base storage, node code, term, and add-on quantities one by one. The billed amount should match your current selections. Do not rely on an older configuration page left open in your browser.

Start Configuring Your Order

ORDER PRECHECK Check Before Submitting

Base Model: Lemon M4 or Lemon M4 Pro
Node Catalog: SG / JP / KR / HK / US-W
Rental Term: Daily / Weekly / Monthly / Quarterly
Payment Method: USDT-TRC20 or Stripe card payment
Settlement Currency: USD

The payment gateway actually available is determined by the backend response. After payment, view your order and service status in the console.

Step Two

Verify Your Connection Details Before Sharing Them

Connection details are credentials for accessing the service. Confirm that every field is complete, then store the details in a controlled credential-management location.

Host and Port

Confirm that the host address, SSH port, and graphical connection address are all provided. Do not copy extra spaces, and never mistake a sample address for the real connection target.

Connection Target

Account and Initial Credentials

Check the login username, initial authentication method, and first-login security notice. Share credentials only with members who need to operate the node, and record the scope of access.

Least Privilege

Match the Node to the Order

Compare the node code in the connection details with the order character by character. If the order specifies JP, the delivery record and subsequent network checks should also point to the Tokyo node.

Order Match

Never Share Credentials Publicly

Do not paste host credentials, private keys, recovery phrases, complete access tokens, or unsanitized signed materials into public repositories, group-chat screenshots, build logs, or issue descriptions. When support is needed, submit only the order ID, time of occurrence, node, and sanitized logs.

Credentials Updated Do not keep temporary values

System Version recorded Preserve the build-environment baseline

Time Zone Matches the workload Avoid timestamp mismatches in logs

Disk Capacity confirmed Reserve space for caches and artifacts

Tools Paths executable Verify Xcode and automation commands

Step Three

Establish a Reproducible First-Login Baseline

Do not start a long-running task immediately after your first login. Update temporary credentials, confirm the system version and time zone, then check available disk space, command-line tool paths, and the dependencies required by your project.

The goal is not to create elaborate documentation, but to establish a comparison baseline for troubleshooting. If your build scripts depend on a fixed Xcode path, shell environment variables, or cache directories, complete a manual check before running the pipeline.

Run system and hardware checks, and save the chip, memory, and system version.
Check the remaining space on the project disk, cache disk, and export directory.
Run tool-version commands to confirm that Xcode, Git, and fastlane are available to the current account.
Set the time zone to match your team logs to prevent task and alert timestamps from drifting apart.

Step Four

Complete Your First Build Through the Shortest Path

Verify SSH first, then run a repeatable Xcode test build and confirm that the automation tools can read the project and produce output.

first-build.log

$ ssh -p 22 build@host
Last login: secure session established

$ sw_vers -productVersion
15.x

$ xcodebuild -scheme App \
  -configuration Debug \
  -destination 'generic/platform=macOS' build

Resolve Package Graph
CompileSwiftSources normal arm64
Ld build/Debug/App normal arm64
** BUILD SUCCEEDED **

$ fastlane lanes
Available lanes:
  mac test
  mac build
  mac archive

$ fastlane mac test
Tests: passed
Artifacts: ./build/reports

Continue Only After a Successful Connection

On your first connection, verify the source of the host fingerprint. If the connection fails, do not change several variables at once; first check the address, port, username, and local network.

Run a Small Test Target First

Choose a scheme with few dependencies and a predictable runtime to verify the compiler, dependency resolution, cache directory, and output permissions.

Save the Raw Logs

When a build fails, retain the complete command, exit code, and sanitized logs. The final line alone is usually not enough to identify the failed stage.

Step Five

Compare Measured Node Results with Your Order

A successful test build only proves that the toolchain runs. Before production use, also confirm that the hardware, storage, region, and network egress match your order.

Cloud Mac First-Delivery Checklist
Check	How to Verify	Pass Criteria
Chip and Memory	Read the system hardware overview or command-line hardware information	Base tier: M4 / 16GB; higher tier: M4 Pro / 64GB
Base Storage	Check total disk capacity, available space, and mount points	Base tier: 256GB; higher tier: 2TB, matching the selected add-ons
Node Region	Compare the order node code, delivery record, and network egress direction	SG, JP, KR, HK, or US-W matches the order selection
Development Tools	Run version commands and a small test build	Tools are callable, dependencies resolve, and the build exits successfully
Remote Session	Exit, disconnect, and reconnect once	Credentials work, SSH or VNC reconnects reliably, and background task status is as expected

Network egress information confirms access direction; it does not establish the precise facility location. If any key field differs from the order, stop writing important data and submit a ticket through the console.

Delivery Acceptance

Complete Five Tests Before Moving Production Workloads

Acceptance proves that the full path from local connection to artifact retrieval works. Do not treat seeing the desktop as a substitute for build and export tests.

Remote connection: Complete the first SSH or VNC connection and verify that you can reconnect after disconnecting.

Repository checkout: Use controlled credentials to fetch a test repository and confirm that networking, permissions, and disk writes work normally.

Test build: Run a repeatable small build and save the command, exit code, and logs.

Artifact export: Write the test artifacts to the specified directory and complete one secure download or archive.

Exit and reconnect: End the session deliberately, reconnect, and confirm that the environment, task status, and files remain as expected.

5 / 5 The node passes first acceptance only after all five checks succeed

Choose the Path That Matches Your Current Need

Whether you need to improve the connection experience, troubleshoot a build, or manage the current service, you do not need to repeat the entire process.

Configure SSH and VNC

Review connection parameters, image quality and resolution settings, latency troubleshooting, reconnect procedures, and session-security recommendations.

View Remote Access Guide

Troubleshoot Build and Network Issues

Find steps by error message, tool name, connection method, and order topic, and prepare sanitized logs for support troubleshooting.

Visit Help Center

Manage Orders and Services

View the current term, node, add-ons, and service status. When support is needed, submit a ticket with the order ID from the console.

Open Console

Ready to Start

Confirm Your Use Case, Node, and Term Before Ordering

Both dedicated Mac mini physical-node tiers are available daily, weekly, monthly, or quarterly. Actual availability is determined by the live status returned in the console.

Rent a Cloud Mac Now View Full Pricing