Renting a cloud Mac? Clarify the key details first

No. Each order corresponds to a dedicated physical Mac mini running in the cloud, with its device resources reserved for that order. It is not a virtual machine on a shared host, and its configuration is not created by partitioning compute resources.

“Dedicated” describes how the device is allocated. It does not mean that the network route or upstream services are exclusive to one customer. External networks, code hosting, software licenses, and other third-party services continue to operate under their own rules.

The CPU, memory, and local SSD of the same device are not allocated for concurrent use by multiple orders. The selected chip, memory, and base storage specifications correspond to the actual physical device configuration.

If your workflow needs additional storage or multiple devices connected via Thunderbolt 5, select the relevant add-ons separately when ordering and follow the combination shown on the order confirmation page.

Common use cases include Xcode builds and testing, continuous integration runners, long-running command-line tasks, toolchains that require the macOS graphical interface, and AI experiments with sustained CPU, memory, or local-cache usage.

If a task depends on low-latency local peripherals, real-time color evaluation, or specialized capture hardware, verify the network route and hardware connection requirements first. Remote workflows are well suited to repeatable computation in the cloud, but the experience still depends on the network quality at your access location.

Daily terms suit short validations, issue reproduction, and temporary builds. Weekly terms suit sprint work, release-submission preparation, and focused testing. Monthly terms suit stable development and continuous integration. Quarterly terms suit long-running pipelines with clearly defined capacity needs.

Do not choose a term based only on the duration of a single task. Allow time for dependency downloads, environment setup, cache creation, acceptance testing, and data migration before the order ends.

The base model prices are fixed, but an order may include add-ons such as 1TB SSD, 2TB SSD, or Thunderbolt 5 connectivity. The confirmation page summarizes the base plan, term, location, and selected add-ons; review each item before submitting.

All prices are based on the plan pageand the order confirmation page. Do not assume discounts, taxes, or services not listed.

Complete renewals in the console according to the rules available for the current order. Before proceeding, check the order end time, renewal term, amount, and device status; do not infer that an order was extended from a local calendar reminder alone.

If the order information in the console differs from your expectations, sign in and submit a ticket with the order number and requested resolution.

All plans, add-ons, and orders are billed in USD. The “$” symbol on the page means US dollars; prices are not converted to other currencies.

You generally only need to provide the console order number, issue type, payment status, and redacted error details. Do not include wallet private keys, full card numbers, card security codes, account passwords, or other sensitive authentication data in email or tickets.

Card transactions are processed by Stripe; the site support process does not require complete card details. The payment gateway available to you is determined by the console.

Customers are responsible for application-data backups and recovery verification. Do not use the device’s local SSD as the only copy of code, keys, media, or build artifacts, and do not treat renewal as a backup mechanism.

Keep at least a version-controlled code repository, dependency list, build scripts, redacted configuration, and key artifacts, and regularly verify that these materials can be restored on another device.

Complete checks for uncommitted code, migrate projects and artifacts, rotate keys, stop automation jobs, unbind external callbacks, and perform sample recovery validation. Device access may stop after the order ends; do not make last-minute data copying your standard process.

Handle cancellation and renewal through the current order flow provided in the console. The service-level target is 99.9%; when the service terms are met, credits are calculated according to the affected service period. Measurement rules, exclusions, claim materials, and processing conditions are governed by theservice terms.

When submitting a service issue, provide the order number, device identifier, time of occurrence, duration, reproducible symptoms, and troubleshooting steps already completed so the impact can be assessed.

For pre-sales selection and general questions, email support@vmdebug.com. For existing orders, device connections, or billing issues, sign in to theconsole and submit a ticketwith the order number and necessary redacted information.

Before contacting support, review theengineering guideandgetting-started processto narrow the issue down by connection, environment, network, or order.