Know the service boundaries before placing an order

By accessing the OpsVM website, creating an account, submitting an order, paying fees, or starting to use Cloud Mac services, the user confirms that they have read and accepted the Terms of Service, Privacy Policy, and order confirmation in effect when the order is created. Anyone acting for a team, company, or other organization must be authorized to accept these terms and manage its orders.

The order confirmation records the selected model, node region, rental period, add-ons, amount due, and billing status. Together with these terms, it forms the service agreement. If specific transaction details conflict with general information, the configuration and amount stated in that order control.

Users who do not accept these rules must not place an order or continue using the service. Continued use of the physical node after an order is created constitutes acceptance of the terms applicable to that order.

OpsVM provides Mac dedicated physical machines deployed on cloud nodes. Each valid order grants use of the physical node identified in that order; underlying resources are not split among multiple users as virtual machines. Users may use the macOS graphical interface, command line, Xcode, and compatible development toolchains.

The current catalog includes OpsVM M4 Core, OpsVM M4 Plus, and OpsVM M4 Pro. Available regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the US East Coast, and the US West Coast—a total of 6 node locations. All tiers support these regions; actual availability is subject to the real-time result returned by the console.

The service scope is defined by the model, memory, SSD, additional storage, Thunderbolt 5 parallel-connection options, node region, and rental period in the order. Expansion capacity, parallel devices, migration work, and managed operations not listed in the order are not included automatically.

Users must provide accurate, reachable account information consistent with the order’s purpose and update it promptly when details change. Order creation, configuration selection, payment confirmation, support-ticket submission, and node activity performed through an account are treated as actions by the account holder or an authorized member.

Users are responsible for securely protecting account passwords, SSH private keys, node credentials, host fingerprint records, and recovery information. Credentials must not be published, embedded in public code repositories, or shared with anyone without node access rights. For team access, use an auditable member-authorization method and revoke permissions promptly when a member leaves the project.

If you detect an unusual login, unknown order, credential leak, or unauthorized node activity, immediately replace the affected credentials and submit a ticket through the console. Include the order identifier, node region, time of the incident, and steps already taken. Do not submit private keys, account passwords, or unsanitized signing materials.

All three available models can be rented by the day, week, month, or quarter. Each period is an independent pricing unit; longer-period fees are not automatically derived from shorter-period prices, and unused time is not automatically converted into another period. Before ordering, confirm that the selected period covers your expected build, testing, release, and data migration schedule.

The table below lists the standard prices for the base models. Additional storage and Thunderbolt 5 parallel-connection fees are added separately to the order; complete add-on pricing is determined by theplan pageand order confirmation.

An order becomes active after payment is confirmed and node processing is complete. Check the model, region, period, and add-ons before paying. If the order details do not match your expectations, stop and submit a console ticket with the order identifier and the fields requiring review.

Prices shown on the page and amounts in order confirmations are quoted in USD. Taxes, payment-processing details, and any other legally required items, if applicable, are shown separately during order confirmation and are not concealed by changing the model name.

OpsVM supports only two payment methods: USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are billed in USD. The payment gateway actually available is determined by the result returned during checkout.

When using USDT-TRC20, verify the network, recipient details, amount due, and transaction record carefully. If an incorrect network, recipient detail, or duplicate transaction requires investigation, provide the order identifier, transaction time, USD amount, and verifiable transaction record.

For Visa / Mastercard / Amex (via Stripe), authorization, verification, and processing status are returned through checkout. Submitting payment does not mean the order is complete; the confirmed result shown in the console controls.

Users may use the physical node for lawful software development, automated builds, testing, artifact handling, local model inference, audio and video encoding, and other tasks consistent with the ordered resources. Use must not harm the node, platform, network, other users, or third parties’ lawful rights.

The following activities are prohibited on OpsVM services:

• Unauthorized access:Scanning, attempting to access, or controlling accounts, systems, ports, networks, or data without authorization.
• Malware distribution:Creating, hosting, delivering, or running code intended to steal, damage, extort, covertly control, or expand an attack surface.
• Resource abuse:Continuously consuming resources to disrupt node delivery, network stability, security checks, or other normal service processes.
• Control circumvention:Bypassing authentication, access restrictions, order boundaries, traffic controls, security records, or protections implemented by the platform.
• Infringing others’ rights:Processing protected content, trade secrets, personal information, or other legally protected material without permission.
• Unlawful use:Using the node for activities that violate applicable law, valid orders, or the user’s own contractual obligations.

When investigating unusual use, the platform may ask the user to explain the task purpose, process sources, network behavior, and data-processing scope. Provide sanitized information sufficient to locate the risk; do not submit private keys, passwords, or complete signing materials.

All nodes operate normally 365 days a year, with no fixed interruption period. If there is a security risk, hardware fault, legal requirement, or infrastructure event requiring immediate action, the platform may make necessary changes. Where conditions permit and doing so will not increase risk, it will explain the impact and required user steps through account notifications or tickets.

Users are responsible for maintaining recoverable copies of repositories, signing materials, build caches, artifacts, databases, and business files. A physical node should not be the sole storage location for important data. Before updating macOS, switching Xcode versions, upgrading dependencies, adjusting disks, or changing automation scripts, verify compatibility and complete a recoverable backup.

Before the service period ends, users must migrate their code, configuration, artifacts, and necessary logs and confirm that the destination can read them. After service ends, the node may enter a cleanup and reconfiguration process, and the original connection details will no longer serve as a long-term data-access route.

Necessary restrictions may be applied to an account, order, network access, or node activity when payment remains overdue, acceptable-use rules are violated, the account or node presents a significant security risk, a platform investigation is obstructed, or the platform must comply with a valid legal requirement.

Measures must be proportionate to the risk. They may include requesting additional verification, restricting specific connections, suspending node access, blocking new orders, or terminating the affected service. For urgent security risks, the platform may first restrict the risky activity and then explain the information required and the next steps.

If the user believes the basis for a measure, order status, or risk assessment is incorrect, they may sign in to the console and appeal by ticket. Include the order identifier, node region, time, relevant actions, completed remediation steps, and sanitized evidence. The platform will review the matter using order records, payment status, system logs, and the user’s supplementary materials.

Service termination does not release obligations for payments incurred before termination, data migration, credential protection, or measures arising from violations. Users should export necessary data promptly while access remains available.

The platform is responsible for providing the physical node, configuration, region, and rental period specified in the valid order, and for handling account, billing, and support matters directly related to delivery. Users are responsible for their own code, data, toolchain, authorized users, network environment, automated tasks, and the results of activity on the node.

Users are responsible for losses caused by configuration errors, credential leaks, missing backups, incompatible upgrades, third-party code defects, local network issues, or actions by authorized personnel. If performance is affected by natural disasters, widespread infrastructure failures, government action, war, severe cyberattacks, or other events beyond reasonable control, both parties must take reasonable steps to reduce the impact and restore performance of their obligations.

To the extent permitted by applicable law, liability is allocated based on direct, provable losses causally connected to a specific breach. No limitation of liability affects responsibility that cannot legally be excluded or limited, nor does it change the user’s responsibility for managing their data, credentials, and use.

These terms are governed by the law of the jurisdiction where the platform operator is based. For disputes arising from these terms, an order, or service use, the parties should first review the matter through support tickets and written materials. If consultation does not resolve it, the dispute will be submitted to a competent court in that jurisdiction.

When the terms change because of service processes, security requirements, or legal obligations, the updated version will state how it takes effect. Updates that materially affect existing orders will be communicated through account notifications or another recordable method. Continuing to place orders or use the service after an update takes effect constitutes acceptance of the updated terms.