Confirm the service scope before ordering a Cloud Mac

Service Definition

VMKeep provides Cloud Mac dedicated physical machines rented for specified periods. Each valid order corresponds to the Apple Silicon physical node, configuration, region, and rental period listed in the order. Running instances are not shared with other tenants, and the service is not virtualized.

The service includes the node details required for remote access, use of the machine during the rental period, and console features for viewing orders, rental periods, and instance status. SSH is suitable for command-line work, automation, and continuous integration; graphical remote access is suitable for workflows requiring the full macOS desktop experience.

Ownership of the machine does not transfer with the rental. The user receives only a right to use it during the order period, subject to these terms. Users may not dismantle equipment, resell nodes, transfer account control, or package the service as a resale product not approved by VMKeep.

Accounts and Orders

Users must provide accurate, complete information that can be used to contact them about the service, and keep their email address and console access methods valid. Users must protect login credentials, SSH keys, remote access passwords, automation tokens, and team-member permissions, and must not disclose them to unauthorized parties.

Orders created, confirmed, or paid for through a user account are considered authorized by that user. When a machine is shared by multiple team members, the account holder must establish least-privilege access, offboarding access revocation, and key-rotation procedures, and is responsible for configuration changes, data processing, and task execution under the account.

If a user detects an unusual login, compromised credentials, or an unauthorized order operation, they must immediately change the relevant credentials and, through a console ticket or contact the service teamsubmit the order number, node region, time of occurrence, and redacted evidence. The platform may temporarily restrict high-risk operations to protect the account and node.

• Accurate information:Keep contact details, order purpose, and team authorization relationships current.
• Credential separation:Store personal login information separately from automation keys, and never keep them in public repositories.
• Traceable operations:Retain records of configuration changes, build jobs, and critical data migrations.

Configurations and Regions

Orders are limited to the three available machine configurations listed below. The model, memory, and system-disk capacity are determined by the combination shown on the order confirmation page; out-of-catalog configurations cannot be requested through notes.

The five available regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East Coast. All three configurations can be ordered in these five regions; actual availability is based on the console’s real-time status. Once a region enters the delivery process, any change requires prior confirmation of data migration, network routes, and the new order arrangement.

Users should choose a region based on repository location, team-member locations, external service routes, and data-processing requirements. Region names indicate the delivery area and do not guarantee fixed network latency or a specific route.

View the complete configuration and region catalog

Pricing and Billing

Orders are priced according to the model, period, region, and add-ons shown on the page when the user confirms the order. Daily, weekly, monthly, and quarterly rentals are supported, and all amounts are billed in USD. Each period has its own catalog price and is not calculated by simple multiplication.

Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. Actual gateway availability is determined by the checkout interface. Order amounts, billing records, and refund or credit records are all recorded in USD.

Before payment, users must verify the model, region, rental period, add-ons, and final amount. Payment completion does not waive security verification or delivery checks. If payment details do not match the order status, submit the order number and payment record through a console ticket; do not provide complete payment credentials in ordinary text.

Add-ons

Expanded storage and Thunderbolt 5 interconnect are separately priced add-ons. They are included in an order only after appearing in the order interface and being confirmed. An add-on’s period must match the associated host order and cannot be used independently of a valid machine rental.

Storage expansion does not replace the user’s own backups. Thunderbolt 5 interconnect is provided only as the add-on capability explicitly listed in the order. Users remain responsible for designing task distribution, data consistency between nodes, failure retries, and result-archiving workflows.

Acceptable Use

Users may not use the service for unlawful activity, unauthorized access, malware distribution, credential theft, network attacks, access-control evasion, intellectual-property infringement, infringement of other third-party rights, or similar conduct. Users may not affect nodes, networks, or other services through sustained abnormal loads, destructive scripts, or unauthorized scanning.

Users must ensure that their code, models, datasets, build materials, and automation tasks have lawful sources and the necessary authorizations. For team workflows, account holders should establish code review, dependency-source checks, secret scanning, and artifact access controls, and avoid using nodes for tasks whose responsible party cannot be identified.

If the platform detects suspected violations or an urgent security risk, it may ask the user to explain the purpose, stop related tasks, rotate credentials, or move risky content off the service. If the risk persists, the user refuses to cooperate, or the conduct clearly violates these terms, the platform may restrict or suspend the relevant service and retain necessary records for investigation and compliance.

Data and End of Rental

Users are responsible for the legality, integrity, and backup of their data, code, models, build artifacts, keys, tokens, and signing materials. A Cloud Mac should not be treated as the user’s sole data copy; critical repositories, model files, configuration manifests, and build results should be synchronized to secure storage controlled by the user.

Before the rental ends, users should export data, archive build artifacts, disable automation tasks, and review team permissions. They should revoke deployment keys, repository tokens, runner registrations, and any other credentials that can still access external systems. Users should also confirm that no files on the machine are still needed before ending use.

1. 01

   Archive reproducible materials

   Export code versions, dependency lockfiles, environment documentation, model parameters, and critical logs.

2. 02

   Migrate business data

   Verify the destination for repositories, build artifacts, caches, model files, and shared team directories.

3. 03

   Revoke external credentials

   Remove keys and tokens, unregister runners, and terminate automation tasks that are no longer needed.

After the rental ends, continued access to the original node may not be available. Users are responsible for risks arising from failing to migrate data on time, failing to verify backups, or leaving external credentials on the machine. To extend use, users should review the order details in the console and complete the required action before the current rental ends.

Changes, Suspension, and Liability

The platform may update service rules based on service security, the product catalog, pricing structure, payment-processing requirements, or legal obligations. Changes that materially affect user rights or obligations will be announced through the website, console, or a valid contact method provided by the user. Updated terms apply to services created or continued after they take effect.

In the event of hardware failures, network incidents, security risks, prohibited use, force majeure, or other events beyond reasonable control, the platform may take necessary measures such as diagnosis, connection restrictions, task termination, node isolation, migration assistance, or service suspension. Measures will consider the urgency of the risk, scope of impact, recoverability, and user cooperation.

To the extent permitted by applicable rules, the platform is not liable for indirect losses, lost anticipated profits, lost business opportunities, or losses caused by the user’s failure to back up data, credential disclosure, incorrect automation configuration, or failure to migrate data promptly, beyond the amount paid for the relevant order. Any liability that cannot legally be excluded or limited will be handled under the applicable rules.

These terms are governed by the laws of the jurisdiction where the platform’s operating entity is located. The parties should first negotiate in good faith through a console ticket or contact the service teamIf the dispute cannot be resolved through negotiation, it may be submitted to a court with jurisdiction in that jurisdiction.