Confirm Apple Silicon compatibility
Check whether your project dependencies, binary tools, build scripts, and container workloads support arm64. Record legacy tools that require Rosetta separately; do not assume every dependency runs natively.
First Deployment Runbook
Deploy Your Cloud Mac in About 4 Minutes
Choose from three Apple Silicon configurations and six nodes, complete USD checkout, then verify SSH, Xcode, dependencies, and artifact output. Every step includes clear inputs, checkpoints, and completion criteria.
3 plans
Available configurations
6
Available nodes
About 4 minutes
Complete initial verification
OPSVM / DEPLOYMENT MANIFEST
READY
One order, one dedicated physical machine
Not a shared virtual machine. After node initialization, verify the host fingerprint before connecting your development toolchain.
- Architecture
- Apple Silicon
- Term
- Day / Week / Month / Quarter
- Availability
- 365 days
Before You Begin
Document all six choices before opening the configuration page
No additional software is required to prepare. Decide your workload, region, and connection method in advance to avoid changing key settings after node initialization.
Choose a target node
Choose from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West. Consider your team’s access patterns, then factor in your repository, artifact storage, and target market.
Match the plan to your workload
OpsVM M4 Core includes M4, 16GB, and 256GB; OpsVM M4 Plus includes M4, 24GB, and 512GB; OpsVM M4 Pro includes M4 Pro, 64GB, and 2TB.
Estimate storage needs
Estimate code, DerivedData, dependency caches, simulator data, and artifacts separately. Add +1TB SSD or +2TB SSD when needed; do not size storage based on repository volume alone.
Choose your rental term
Day, week, month, and quarter are separate billing terms. Choose daily billing for short compatibility checks and a longer term for stable pipelines based on actual usage; do not infer prices across terms.
Prepare remote access tools
For command-line work, prepare an SSH client and keys first. If you need the Xcode graphical interface, also prepare a graphical remote client and confirm that your local network allows the required connections.
From Order to Ready
Four checkpoints, with a target total time of about 4 minutes
Timing starts once your configuration is clear. Actual completion depends on node status and payment confirmation; use the live result shown in the console.
-
01 About 1 minute
Choose a configuration
Choose OpsVM M4 Core, OpsVM M4 Plus, or OpsVM M4 Pro, then confirm one of six regions, a day/week/month/quarter term, and any storage add-ons.
Complete: Order configuration matches the expected workload -
02 About 1 minute
Complete USD checkout
Check the order amount and term, then pay with USDT-TRC20 or with Visa / Mastercard / Amex through Stripe.
Complete: The console shows the payment confirmation -
03 About 1 minute
Initialize the physical node
The system assigns a dedicated physical machine to your order and generates connection details. Do not create duplicate orders or repeatedly submit the same action during initialization.
Complete: Node status and connection details are available -
04 About 1 minute
Verify the first connection
Check the address, account details, and host fingerprint, establish an SSH session, and verify the system version. Configure a remote graphical session only if you need a GUI.
Complete: The command line works and the host identity is verified
Create an Order
The configuration page requires three core choices
Choose the compute specification, then the node and term. All three models can be ordered in six listed regions; availability is based on the live console response.
Configuration order
CONFIG → REGION → TERM
Choose from three available models
- OpsVM M4 CoreM4 · 16GB · 256GB
- OpsVM M4 PlusM4 · 24GB · 512GB
- OpsVM M4 ProM4 Pro · 64GB · 2TB
Choose from six nodes
Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West. Prefer the node with lower, more stable latency from your team’s actual office networks.
View the node guideChoose based on the task duration
Rent by the day, week, month, or quarter. After confirming the term, check whether you need a +1TB SSD, +2TB SSD, or Thunderbolt 5 expansion add-on.
Configure an OrderUSD Checkout
Two payment options, with all orders priced in USD
Before submitting, verify the model, node, term, add-ons, and final USD amount. The available payment gateway is determined by the console response.
Bank card
Visa / Mastercard / Amex are supported and processed through Stripe. Before checkout, check the billed amount, order term, and issuer verification result.
USDT-TRC20
Carefully verify the network, recipient details, and USD order amount. Do not use transfer details from another network for this order.
Final checks before payment
Order identifier
USD amount
Payment network or card channel
Console confirmation
First Connection
Verify SSH first, then enable a graphical remote session
The priority during the first connection is not installing tools immediately. Confirm that you reached the correct physical node and preserve a trusted baseline for future troubleshooting.
-
01
Read the console connection details
Verify the node region, host address, account details, and key usage method. Never copy connection details into public repositories, chat histories, or unencrypted documents.
-
02
Check private key permissions
Restrict access to the key file locally, confirm that it belongs to this node, and then initiate the connection.
-
03
Verify the host fingerprint
Compare the fingerprint shown on first connection with the information provided in the console. If they differ, stop connecting and do not ignore the warning.
-
04
Start a session and inspect the system
After connecting, record the macOS version, hostname, available disk space, and current Xcode path to establish the first-deployment baseline.
Command line first
Use SSH for Git, dependency installation, builds, tests, and log exports whenever possible; the steps are easier to record and reproduce.
Read the connection guideEnable graphical sessions as needed
Configure a remote graphical session only when you need Xcode’s GUI, and adjust resolution, frame rate, and color quality to suit network conditions.
View connection troubleshootingMigration Path
Migrate in three layers: code, toolchain, and automation
Do not move the entire old environment at once. Validate each layer independently and preserve the results so you can identify whether an issue comes from data, dependencies, or pipeline configuration.
A1
Input layer
Migrate code and required data
Get code through Git whenever possible. Transfer large data sets, cache seeds, or media assets with SFTP or verified archives; do not copy unrelated temporary files.
- Confirm the repository branch and commit
- Separate code, data, and build caches
- Record checksums for archives
- Check available space on the target disk
B2
Environment layer
Reproduce the Xcode and dependency toolchain
Record the Xcode version and selected path, then install dependencies from the lockfile. Pin command-line tools, Ruby, Node, and other runtimes instead of relying on interactive historical configuration.
- Confirm Xcode and command-line tool paths
- Restore dependencies from the lockfile
- Separate project-level and system-level configuration
- Run one clean test build
C3
Automation layer
Connect CI, signing, and artifact delivery
Start with a minimal task that validates checkout, build, test, and export before connecting the full pipeline. Provide sensitive signing materials with least privilege and keep them out of logs.
- Limit CI task access
- Separate sensitive variables from code
- Verify test reports and exit codes
- Confirm artifact delivery paths and checksums
Toolchain Verification
Deployment is complete only when all five checks pass
Verify from system facts through artifact results. If any step fails, preserve the complete output first; do not upgrade multiple dependencies or change several configuration groups at once.
System version
Confirm that the macOS version, architecture, and hostname match expectations.
sw_vers && uname -m && hostname
Xcode path
Check the active developer directory and Xcode version to prevent the command line from targeting the wrong installation.
xcode-select -p && xcodebuild -version
Dependency installation
Restore dependencies from the project lockfile and save the installation output and failed items.
git status --short
Test build
Run the project’s defined test targets and verify the exit code, failed cases, and test report.
xcodebuild -list
Artifact output
Confirm the artifact directory, file sizes, checksums, and delivery target; do not stop at a successful build.
find ./build -type f -maxdepth 2
Security Finalization
After the build, secure access boundaries and recovery paths
A node being available does not mean deployment is finished. Complete the following before running production tasks and assign an owner within your team.
Replace temporary credentials used during initialization and avoid sharing credentials
Restrict SSH and graphical remote access by source; expose only the required entry points
Store private keys in a controlled location; never put them in repositories, build logs, or artifacts
Check automatic sleep settings to prevent long-running tasks from being interrupted by system state changes
Record the system version, Xcode path, dependency versions, and first test results
Create separate recovery procedures for code, required data, and pipeline configuration
Exit unused graphical sessions and close network entry points you no longer need
Prepare a redacted log export method so support requests can include the necessary details directly
With your configuration confirmed, create your Cloud Mac order
Choose one of the three models, one of the six nodes, and the required term. If connection issues remain, read the remote access guide first.