Cloud Mac Rental & Usage Terms

By accessing this website, creating or managing an order, paying fees, or starting to use a Cloud Mac delivered by VMRunner, you confirm that you have read and agree to these terms. If you act for a team or organization, you also confirm that you are authorized to accept these rules on its behalf.

VMRunner provides Cloud Mac ordering, node orchestration, delivery information, and support processes. The model, node, rental period, add-ons, and amount confirmed in an order form the service agreement together with these terms. If an order record conflicts with these terms, the specific configuration and amount in the confirmed order prevail; the fair-use, account-security, and legal-responsibility provisions continue to apply.

VMRunner provides dedicated Apple Silicon physical nodes, not virtual machines. Each valid order corresponds to the physical-machine configuration and rental rights listed in that order, without sharing the same running instance with other orders. The exact chip, memory, internal storage, additional storage, rental period, and node city are determined by the order record.

Current available configurations are VMRunner M4 S (M4, 16GB, 256GB), VMRunner M4 X (M4, 24GB, 512GB), and VMRunner M4 Pro X (M4 Pro, 64GB, 2TB). Available nodes are located in Singapore, Tokyo, Seoul, and Hong Kong. Actual model and node availability are determined by the real-time results shown in the Console.

Delivery information typically includes the node address, dedicated credentials, and necessary connection instructions. You may use the macOS graphical interface, command line, and development toolchain as permitted by your order. You are responsible for maintaining software versions, project dependencies, build caches, certificate settings, and working directories for your tasks.

Resource type

Dedicated physical node

Processor platform

Apple Silicon

Service model

Not a virtual machine

Configuration basis

Confirmed order

All orders are priced and settled in US dollars (USD). VMRunner supports only USDT-TRC20 and Visa, Mastercard, and Amex processed through Stripe. The payment gateway actually available is determined by the results shown in the Console.

Before paying, verify the order amount, rental period, model, node, and add-ons. For an on-chain transfer, use the network, address, and amount provided in the order exactly. For a card payment, complete the required verification in the payment flow. If verification is needed because of an incorrect input, a wrong network, or payment to an address not listed in the order, you must provide verifiable transaction details.

An order enters delivery only after the payment flow confirms payment and the system creates a valid record. Unpaid funds, declined payments, or funds that cannot be linked to an order do not activate the service. To verify billing information, submit the order ID, payment method, amount, and redacted transaction evidence. Do not send a full card number, private key, or complete access token.

• USDT-TRC20:Use the network and recipient details shown in the order, and retain the transaction ID for verification.
• Bank cards:Visa, Mastercard, and Amex are supported and processed through Stripe.
• Settlement currency:Bills, orders, and fee records are all denominated in US dollars (USD).

Services are available for daily, weekly, monthly, and quarterly rentals. The start and end status, current configuration, and renewal options for each period are determined by the Console and the confirmed order. Each period has its own listed price; the amount for one period must not be treated as an automatic conversion of another period.

Before the rental period ends, check that your tasks, build artifacts, certificates, caches, and required data have been properly saved. A renewal requires a valid order record in the Console; submitting an inquiry, sending an email, or keeping a remote session open does not automatically extend the rental period.

Changes involving the model, node, storage, or Thunderbolt 5 parallel configuration must be confirmed through a new order record or the change process provided in the Console. Until a change takes effect, the original order continues under its confirmed configuration. To avoid build interruptions, sync data, verify the toolchain, and drain tasks before switching configurations.

Cloud Mac services are intended for lawful development, testing, continuous integration, remote processing, and related engineering tasks. You must not use a node to infringe another party’s systems, data, networks, or intellectual property, or to bypass applicable access controls and security measures.

The following activities are not permitted uses of the service. When VMRunner identifies a clear risk, it may restrict the relevant tasks, suspend affected access, or request necessary information to protect nodes, networks, and other service participants.

• Accessing, scanning, probing, or controlling systems, accounts, network ports, or data without authorization.
• Distributing malware or running tasks intended for credential theft, extortion, destruction, covert control, or denial of service.
• Intentionally generating abnormal network traffic, resource contention, or sustained load that affects core node services or network stability.
• Storing, processing, or distributing infringing content, or using a node for fraud, harassment, or other unlawful activities.
• Circumventing order limits, reselling unauthorized access, or disclosing node credentials to unrelated third parties.
• Interfering with security audits, deleting necessary records directly related to incident investigation, or providing false failure information.

If you are unsure whether a use complies with these terms, you may submit a workload summary through the Contact page before running the task. The summary must not include private keys, certificate passwords, or unredacted configuration.

You are responsible for protecting the credentials used for the website, Console, and node connections, and for orders, configuration changes, and node operations initiated under your account. If credentials may have been exposed, immediately stop sharing them, rotate the relevant keys, and report the affected order ID through a Console ticket.

You are responsible for the legality and backup of repositories, certificates, keys, configuration files, build caches, assets, and artifacts. Important data should not be stored on only one node. Before system changes, disk cleanup, dependency upgrades, or automated scripts, maintain a recoverable backup or a reproducible build process.

Before sending logs to the support team, remove private keys, complete access tokens, certificate passwords, payment credentials, and unnecessary personal information. Support investigations generally need only the order ID, node city, time of occurrence, reproduction steps, redacted logs, and expected result.

Credential protection

User responsibility

Project backups

User responsibility

Node delivery

Platform responsibility

Support channels

Tickets or email

All nodes operate normally 365 days a year. Security incidents, force majeure, upstream network issues, hardware failures, or user actions may still affect access. VMRunner will use the information available to isolate, diagnose, restore, or adjust delivery, and will explain progress through Console tickets or the support email.

Support covers connection failures, verification of node delivery information, basic investigation of build issues, disk requirements, node-selection guidance, and billing-record verification. Project source-code defects, third-party dependency behavior, user-defined scripts, and data not saved as required are not node failures that the platform can directly fix.

When submitting a support request, provide one clear record of the issue and avoid creating multiple tickets for the same event. A complete record should include the order ID, node city, time of failure, reproduction steps, redacted logs, and expected result. Urgent security response may temporarily restrict affected connections to prevent the risk from spreading.

To the extent permitted by applicable law, VMRunner is not liable for indirect, consequential, expected-profit, business-opportunity, or other losses resulting from user configuration, third-party software, external networks, data not backed up by the user, or events beyond the platform’s reasonable control. Any liability assessment must consider the specific order, verifiable records, the actions of both parties, and evidence of direct loss.

These terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first communicate through the support channel about the disputed facts, order records, and proposed resolution. If the dispute cannot be resolved through discussion, it may be submitted to a court with jurisdiction in that jurisdiction.

VMRunner may update these terms to reflect service changes, security requirements, or changes in applicable rules. The updated version will show a new effective date on this page. Changes that materially affect user rights or obligations will be explained through available service channels. Continuing to use the service after a change takes effect means that you accept the updated terms.

For questions about these terms, privacy requests, billing records, or service boundaries, email support@vmrunner.comor sign in to the Console to submit a ticket. Include the necessary order-related information in your request, but do not send private keys, complete access tokens, or certificate passwords.