Claim device
Read the device ID, node, connection address, and temporary credentials in the order details.
Order confirmed → Device assignedCloud Mac / Dedicated physical node
Cloud Mac,dedicated physical machine, not a virtual machine.
Rent a dedicated physical Mac mini on demand and keep builds, tests, and experiments running continuously. Review the hardware, node, and rental term first, then retrieve connection details from the console and connect to your device.
$19.9/ day
Dedicated to one order
SG · JP · KR · HK · US-W / 5 nodes running year-round
Supported workflows
Connect, verify, run
Follow verifiable steps from device claim to a ready session.
Read connection details from the console. On first access, verify the device identity and host fingerprint, configure SSH, and enable the macOS graphical interface only when your workload requires it.
Verify fingerprint
Compare the host fingerprint shown in the console with the result from your first connection, item by item.
Hostname → ED25519 fingerprintConfigure SSH
Import the public key used by your project and confirm that the command-line session and file permissions work correctly.
Key access → Permission verificationStart session
Check the macOS, Xcode, and command-line tool versions before starting work.
Environment verified → Workflow ready
SSH
Device
Session
$ vmdebug device claim --order VD-84A2
✓ dedicated Mac mini assigned
$ ssh-keyscan device-host
ED25519 SHA256:R7vQ...k31 verified
$ ssh build@device-host
✓ macOS session active
$ sw_vers
ProductName: macOS
$ xcodebuild -version
Xcode 16.x
Build version: ready
Input: device information and host fingerprint
Output: verifiable macOS session
Never skip fingerprint verification on first connection
If the host fingerprint does not match the console record, stop the connection and submit a ticket through the console. Never include passwords, private keys, or complete payment details in public email.
Workload scheduling model
Your workload runs on a dedicated resource without competing with other orders for the same device.
Local workflows depend on whether a device is powered on and available; shared resources are also affected by platform queues. VMDebug devices are used by a single order, while your team controls concurrency, cache reuse, and disk cleanup.
Workflow illustration, not a performance guarantee
Local device
Shared resources
Dedicated resources
From job submission to resource readiness
Bar length represents only the number of waiting stages in the workflow, not build time or network performance.
- Local
- Device availability and usage must be coordinated manually
- Shared
- Jobs enter a public scheduling queue
- Dedicated
- The order uses its assigned physical node directly
Two physical resource tiers
Exactly two tiers, with hardware and four term prices listed directly.
Both tiers are dedicated physical cloud Macs, not virtual machines, and can be rented by the day, week, month, or quarter. Pricing for additional storage and Thunderbolt 5 parallel connections is listed separately on the plan page.
Dedicated physical machine
M4-16-256
VMDebug M4
Mac mini M4 · 16GB RAM · 256GB SSD
Ideal for single-project development, automated testing, standard archiving, and light to medium continuous integration workloads.
Daily$19.9
Weekly$53.7
Monthly$99.4
Quarterly$270.4
High-memory workloads
M4PRO-64-2TB
VMDebug M4 Pro
Mac mini M4 Pro · 64GB RAM · 2TB SSD
Ideal for higher-concurrency builds, large caches, AI experiments, local datasets, and remote media processing workflows.
Daily$60.7
Weekly$163.9
Monthly$303.5
Quarterly$825.5
All prices are in USD. Node selection does not change the listed base hardware price; final configuration, add-ons, and amount due are reviewed together before order submission.
View additional storage, parallel options, and node matrixFive nodes
Choose a node when ordering; the full catalog is listed here.
Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West node all support both hardware tiers. The US West node is provided as one complete node, not split into multiple city options.
SG
Singapore
For Southeast Asian workflows; selectable directly when ordering.
AvailableJP
Japan (Tokyo)
For East Asian workflows; selectable directly when ordering.
AvailableKR
South Korea (Seoul)
For Northeast Asian workflows; selectable directly when ordering.
AvailableHK
Hong Kong
For South China and Southeast Asian workflows; selectable directly when ordering.
AvailableUS-W
US West
For North American West Coast workflows, provided as a single node.
Available
Hardware and node availability
Both VMDebug M4 and VMDebug M4 Pro are available in all 5 nodes listed above.
Current availability
Actual availability at checkout is determined by the real-time response from the console.
Service availability target
99.9%
Target availability / service terms definition
Daily status for the past 90 days
Each short bar represents one calendar day and shows the day-by-day structure of the target measurement window. The formal measurement scope, exclusions, claim materials, and results are governed by the service terms.
Year-round operation
All nodes operate normally 365 days a year with continuous availability.
Compensation terms
When the service terms are met, compensation is calculated based on the affected service period.
Claim materials
Submit the order number, device ID, affected time period, and any necessary redacted logs.
Four workload categories
Choose physical resources based on memory, storage, and concurrency needs.
Recommended configurations simplify initial selection but do not replace project-level measurement. Before ordering, review dependency caches, build artifacts, datasets, concurrent jobs, and available disk space.
BUILD
iOS / macOS development
Recommended: VMDebug M4
Suitable for dependency restoration, compilation, unit testing, archiving, signing checks, and artifact downloads. Pin Xcode and dependency versions for long-running projects.
- Configuration
- M4 · 16GB · 256GB
- Resource note
- Reserve enough space for build directories, DerivedData, and archived artifacts
RUNNER
CI/CD runner
Recommended: choose based on concurrency and cache volume
Register a self-hosted runner and isolate its work directory, caches, and secrets. Start single jobs on M4; review M4 Pro first for high concurrency or large caches.
- Configuration
- M4 or M4 Pro
- Resource note
- Limit concurrency and configure cache reclamation and failed-job cleanup
RAM
AI experiments
Recommended: VMDebug M4 Pro
Suitable for experiments requiring more unified memory, local dataset storage, and persistent sessions. Record dependency versions, model files, and baseline outputs first.
- Configuration
- M4 Pro · 64GB · 2TB
- Resource note
- Reserve disk space for datasets, checkpoints, caches, and intermediate results
MEDIA
Remote media toolchain
Recommended: VMDebug M4 Pro
Deploy media import, proxy generation, batch processing, and export to a cloud Mac, while completing final picture and audio review locally.
- Configuration
- M4 Pro · 64GB · 2TB
- Resource note
- Measure media upload time, proxy size, export space, and network latency first
Migration preview
Move from a local Mac to a cloud Mac in three acceptance stages.
Copy only the necessary data first, reproduce the toolchain from a checklist, then connect the cloud Mac to CI. Keep verification points and rollback actions at every stage to avoid migrating the entire environment at once.
View the complete setup path01 / DATA
Data migration
Migrate repositories, build inputs, required caches, and redacted configuration; do not copy obsolete historical artifacts.
- Input
- Repository, resource files, and environment variable list
- Verification
- File checksums and repository workspace status
- Rollback
- Keep a read-only local copy
02 / TOOLCHAIN
Toolchain reproduction
Match Xcode, command-line tools, Git, certificates, Keychain permissions, and dependency versions.
- Input
- Version inventory and project dependency files
- Verification
- Run a no-cache baseline build
- Rollback
- Restore the recorded toolchain versions
03 / CI
CI integration
Register the runner, isolate the work directory, inject secrets, and retain necessary logs for failed jobs.
- Input
- Runner configuration and least-privilege credentials
- Verification
- Testing, archiving, and artifact downloads
- Rollback
- Switch back to the original runner and stop new jobs
Pre-order checklist
Answer four questions about resources, terms, nodes, and payment first.
Review the complete FAQ and service terms for access permissions, system upgrades, data export, renewals, and compensation limits.
View the complete FAQIs the device a virtual machine?
No. VMDebug provides dedicated physical cloud Macs, with device resources assigned to one order and not shared with another order on the same device.
Can I rent by the day?
Yes. Both hardware tiers support daily, weekly, monthly, and quarterly terms. The VMDebug M4 starts at $19.9/day.
Which nodes are available?
Choose from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West—5 nodes in total. Actual availability is returned in real time by the console.
Which payment methods are supported?
Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All orders are billed in USD; the actually available payment gateway is determined by the backend response.
Submit an order runbook
5 nodes, 2 dedicated physical Mac mini tiers.
Choose a hardware tier, node, and daily / weekly / monthly / quarterly term, then verify the configuration and USD amount before submitting. Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported.