This getting-started guide breaks ordering, connecting, migrating, and acceptance testing into checkable actions. Verify configuration and access boundaries first, then deploy your code and build tools to avoid writing sensitive data before the environment is confirmed.
Region, memory, and rental term directly affect your migration approach. Create a concise run sheet first—it is more reliable than filling in requirements after placing an order.
State whether your primary workload is Xcode builds, a self-hosted runner, local model inference, or media processing. Then choose the node closest to your team or dependent services: Singapore, Tokyo, Seoul, or Hong Kong.
For short-term adaptation and light builds, start by evaluating BookaMac M4. For high-memory concurrency, model inference, and demanding media workloads, consider BookaMac M4 Pro. Choose a daily, weekly, monthly, or quarterly term.
Prepare working SSH and VNC clients. Generate a dedicated SSH key pair locally and submit only the public key. Keep the private key on a controlled device; never send it by email or through a support ticket.
Both plans provide a dedicated physical Mac mini, not a virtual machine. Before creating an order, verify the model, node, rental term, and additional storage. The console returns current availability and final order details in real time.
Delivery does not mean you can immediately write data. Verify the configuration and access boundaries first, then pull private repositories or import signing materials.
Confirm that the region selected in the order matches the region shown on the delivery page. Do not determine node location from connection speed alone.
Check the chip, memory, and storage capacity in System Information, comparing each item with the order confirmation.
Verify the SSH address, port, username, and source of the host fingerprint. Save the verification result on first connection.
Confirm the scope, replacement steps, and entry point for temporary credentials. Do not forward complete credentials in shared channels.
Define the inputs, actions, and verification result for every step. If the previous step has not passed, do not move more repositories, credentials, or tasks onto the node.
First pull a repository that can build independently, then verify its branch, commit hash, submodules, and large-file resources. Rebuild dependency caches as needed; do not copy full-machine caches from unknown sources.
Verify the current developer directory, install the command-line tools explicitly required by the project, and restore dependencies from lockfiles. Do not upgrade every tool globally first and then try to explain build differences.
Assign clear labels to the node, isolate the working directory, limit concurrency, and first run a verification pipeline without release actions. Logs must not print keys, tokens, or complete signing materials.
The documentation examples on the right use placeholder addresses. In practice, follow the connection address, username, project workspace, and build target shown on the delivery page.
$ ssh build@203.0.113.24
The authenticity of host is confirmed.
Connected to dedicated Mac node
$ xcode-select -p
/Applications/Xcode.app/Contents/Developer
$ xcodebuild \
-workspace Sample.xcworkspace \
-scheme Sample \
-configuration Debug \
build
** BUILD SUCCEEDED **
$ bundle exec fastlane env
System Locale: zh_CN
Xcode Path: /Applications/Xcode.app
Environment check completedUse SSH for daily automation. When you need Xcode, a simulator, or graphical tools, connect with a VNC client.
Use a trusted VNC client and enter the address, port, and credentials provided on the delivery page. Do not export connection settings to a shared sync directory or let the client permanently save shared credentials.
Start your first connection with moderate resolution and color quality. If interaction feels slow, lower image quality first and check your local network. Do not confuse build duration with display-refresh latency.
Clipboard sync is suitable for short commands and ordinary text; never use it for private keys, complete access tokens, or unsanitized credentials. For sensitive configuration, use a controlled file workflow and verify permissions.
When graphical work is complete, exit the relevant tools, lock the macOS interface, and disconnect the VNC session. Long-running tasks should be managed by scripts or a runner, not by an open desktop window.
Being able to sign in only proves connectivity. Proper acceptance should cover code, dependencies, builds, logs, and networking, leaving a baseline you can reuse next time.
If any item fails, first record the command, exit code, timestamp, and relevant logs, then narrow the variables. Do not change Xcode, dependency versions, and network settings simultaneously, or the true cause will be difficult to identify.
The target branch and commit hash are correct, and submodules and large-file resources are complete.
The lockfile is applied, installation is repeatable, and key dependencies were not upgraded unexpectedly.
The specified target builds successfully, and the artifact location, size, and creation method are traceable.
The complete log is archived, sensitive fields are redacted, and the exit code and job ID are clear.
The repositories and dependency endpoints required by the project are reachable, with no unrelated access exposed.
Complete security setup immediately after first acceptance, and review it again before team handoffs, runner changes, and the end of the rental term.
After completing the initial verification, replace temporary passwords or access credentials and confirm that the old credentials no longer work.
Use a dedicated SSH public key, verify authorized_keys, and restrict local private-key file permissions.
Give each member a traceable access method instead of allowing long-term shared use of one administrator identity.
Remove test archives, temporary downloads, expired caches, and unused credential copies, then review remaining capacity.
Record Xcode switches, dependency upgrades, runner labels, and network changes so future troubleshooting has an audit trail.
Define where build artifacts, repository changes, and required logs will be exported; do not postpone data cleanup until after the rental term ends.
Manage orders, renewals, and hosts in the console. Payments support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe); all charges are in US dollars (USD). Actual available gateways are determined by the backend response.