This guide follows the actual delivery sequence: confirm your Debug M4, rental term, and node, verify the access receipt, connect via SSH and VNC, and finish with a downloadable archive as your acceptance result.
Confirm your configuration, access materials, and add-ons before ordering to reduce back-and-forth after delivery. Actual availability is determined by the live console response.
The current Debug M4 plan includes a Mac Mini M4, 16GB RAM, and a 256GB SSD. Each order maps to one dedicated physical node, not a virtual machine.
Choose daily, weekly, monthly, or quarterly billing based on your task window. Base prices are $19.5,$52.8,$97.7, and$265.7.
The catalog includes five nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West. Prefer the region closest to your code repository, artifact storage, or primary operators.
Use a dedicated key pair and store the private key locally. Check that the public key is complete before submitting it. Never place the private key in order notes, repositories, or tickets.
For command-line builds, start with SSH. Enable a VNC session when you need a graphical interface, display checks, or interactive Xcode work.
For large dependencies, models, or asset workloads, choose +1TB SSD or +2TB SSD. For multi-machine workflows, select Thunderbolt 5 interconnects per machine.
The console summarizes the base configuration, billing period, node, and add-ons you select. Before payment, rely on the final USD amount shown rather than verbal quotes or estimates.
Confirm the chip is M4, memory is 16GB, and base storage is a 256GB SSD. Do not add options outside the catalog.
Select one of the five available nodes, then choose a day, week, month, or quarter based on task duration.
Pay only for the storage or Thunderbolt 5 interconnects required by this workflow, and confirm the billing unit.
Check the region, period, add-ons, and payable USD amount item by item, then complete payment through an available gateway.
Do not connect as soon as you see a host address. First verify the region, identity, fingerprint, and rental-term boundaries, then store sensitive credentials in a team-approved secure location.
| Receipt field | What to verify | What to do if there is an issue |
|---|---|---|
| Node region | It must match one of the regions selected in the order: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or US West. | Pause the first connection, then submit a ticket in the console with the order identifier. |
| Host address | Confirm the address is complete and contains no spaces, punctuation, or line breaks from copying. | Run resolution and port checks first; do not repeatedly guess the address. |
| Username | Use the system username specified in the receipt. Do not replace it with your local computer username. | Keep the original terminal error, redact sensitive data, and submit it. |
| Host fingerprint | The fingerprint shown during the first SSH connection must match the receipt character for character. | Abort immediately if they differ. Do not enter a confirmation character. |
| Access issuance status | The SSH public key and VNC credentials should show as issued or ready for use. | Wait for the status to update or verify it through a console ticket. Do not create another order. |
| Rental end time | Record the time zone and end time to schedule builds, exports, renewals, and access revocation. | If the period is incorrect, review the order details first, then submit a billing ticket. |
The two entry points serve different checks. Use SSH to verify identity, architecture, disk, and toolchain; use VNC to verify display, keyboard mapping, and reconnection after disconnects.
uname -m, expected result: arm64.df -h to check system and additional storage capacity.date to check system time and the time zone used for task records.The fingerprint matches, key-based login succeeds, the architecture is arm64, and disk capacity and system time match the order and workflow expectations.
The graphical session establishes securely, display and keyboard layout are correct, and you can reconnect after a deliberate disconnect using the receipt details.
The host, username, key path, repository, and project names in these examples are illustrative aliases. Never put real credentials in shared documents, build logs, or public repositories.
$ ssh -i ~/.ssh/<KEY_FILE> <USER>@<HOST>$ uname -m
arm64$ xcodebuild -version
Xcode <VERSION>
Build version <BUILD_VERSION>$ xcodebuild -workspace <APP>.xcworkspace \
-scheme <SCHEME> \
-configuration Release \
-archivePath build/<APP>.xcarchive \
archive
** ARCHIVE SUCCEEDED **$ bundle exec fastlane <LANE>
[fastlane] archive: build/<APP>.xcarchive
[fastlane] result: success
A successful connection does not make a workflow reusable. Your first build should leave version, command, artifact location, and timing records for future automation and troubleshooting.
Use repository credentials with only the permissions required for this task. Record the commit identifier so the same source can be reproduced later.
Input: commit identifierRecord the Xcode version, build version, Ruby, and fastlane environment. Avoid unnecessary upgrades during first acceptance.
Input: version inventorySave the complete command, exit status, and key logs. If it fails, first isolate dependency, project-setting, or access issues instead of blindly rerunning it.
Action: archiveCopy the archive to the agreed location, confirm its size, directory structure, and download result, and avoid keeping the only copy on the node.
Artifact: xcarchiveRecord dependency retrieval, compilation, archiving, and transfer time separately. Use these records to compare later tasks, not as a cross-project performance guarantee.
Output: timing breakdownInclude the order identifier, node region, time of occurrence, reproduction steps, exit code, and redacted logs, then follow the support path for the issue type.
View troubleshooting guidearm64Choose a node and rental term, then review the configuration, add-ons, and USD amount. After delivery, verify the fingerprint, connect remotely, and run your first archive using the receipt.