Confirm the boundaries before issuing a remote session

VMOak offers Apple Silicon dedicated physical workstations for daily, weekly, monthly, or quarterly rental, together with remote desktop, SSH, and order management capabilities. During the active service term, each device is assigned to one order and its computing resources are not shared with other orders.

The rental relationship grants only the right to use the device and access it remotely during the agreed term; it does not constitute a sale, finance lease, or transfer of ownership. Ownership of the device, underlying network, and management systems remains with the operator or its lawful resource providers.

Users choose the model, service node, rental term, and add-ons suited to their project and are responsible for confirming the licensing terms of development tools, third-party software, repository services, and project dependencies. The workstation rental fee does not automatically include third-party software licenses, project subscriptions, or external service fees.

Users must provide account and order information that is genuine, accurate, complete, and reachable, and update it promptly when it changes. Anyone placing an order must have authority to accept these terms, configure the service, and complete payment for themselves or their organization.

Users are responsible for securing console accounts, email verification codes, device accounts, temporary credentials, SSH keys, and repository tokens. After first receiving access information, users should promptly update temporary credentials and configure automation permissions according to the principle of least privilege.

Orders, configuration changes, renewals, tickets, and device operations initiated under an account are generally treated as actions of the account holder or an authorized member. After discovering an unusual login, credential leak, or unauthorized operation, users must immediately update the relevant credentials and submit a ticket through the console.

• Do not share complete private keys, complete access credentials, or sensitive tokens that could directly take over a project.
• When a team member leaves a project, promptly revoke their access to devices, repositories, and automation.
• Support staff will never ask users to submit complete private keys or unredacted business data.

An order is governed by the model, node, rental term, storage add-ons, and Thunderbolt 5 parallel connection option ultimately confirmed by the user. If the page, communications, and order details differ, the order details displayed and confirmed by the user before checkout govern.

The current catalog includes only two tiers: VMOak M4 Branch and VMOak M4 Pro Canopy. The six nodes in Singapore, Tokyo, South Korea, Hong Kong, the US East, and the US West are all within the catalog; the specific order result is subject to the real-time response from the console.

Before delivery, we check the device boot status, network connectivity, agreed storage capacity, and access account. Once the access address, account name, and temporary credentials are available through the delivery channel and can be used to establish a remote session, the order is considered delivered.

For a standard order, the process from confirming the configuration and selecting a node to assigning and checking the physical node and generating access details usually takes about four minutes in total. Delivery may take longer if order information requires manual review, a security risk needs confirmation, or the device requires an urgent check.

Order confirmed

Model, node, term, and add-ons fully displayed

Device checked

Boot, network, storage capacity, and access account passed inspection

Delivery complete

Access details are available and can be used to connect to the corresponding physical node

All prices are billed in US dollars (USD). Charges for the model, term, and add-ons are governed by the details shown when the order is confirmed and cannot be replaced by verbal descriptions, estimates, or unsubmitted configuration drafts.

Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported for payment. The gateway actually available is determined by the backend response when the order is submitted. Stripe processes card payments, and VMOak avoids storing complete card details; USDT-TRC20 orders are verified using the corresponding transaction ID.

Before paying, users should verify the currency, amount, term, and add-ons. Network fees for on-chain transfers, charges from card issuers, and the user’s own foreign-exchange arrangements are not included in the order amount shown by VMOak.

View complete plans and configuration details

Users may use Cloud Mac for lawful software development, builds, testing, continuous integration, AI experiments, audio and video production, project collaboration, and remote desktop work. Users must ensure that their code, media, models, datasets, and third-party tools have the necessary usage rights.

The following activities are not permitted. Depending on the level of risk, VMOak may restrict the relevant session, suspend access, and ask the user to explain the situation:

• Unauthorized access to, scanning of, interference with, or control of other accounts, devices, networks, or services.
• Creating, running, or distributing malicious code, stealing credentials, extortion, fraud, or evading security controls.
• Using a node to send abusive traffic, carry out denial-of-service attacks, perform credential stuffing, or continuously consume abnormal network or system resources.
• Processing, storing, or distributing content that violates applicable law, third-party rights, or contractual obligations.
• Bypassing billing, identity verification, access controls, node isolation, or order restrictions.
• Reselling unauthorized device access or exposing complete connection credentials to unmanaged third parties.

To protect other systems and service infrastructure, VMOak may impose necessary restrictions on clearly malicious traffic, unusual port exposure, or persistent resource abuse. When taking action, we will retain operational records within a reasonable scope and update the status through the console or the contact details associated with the order.

Each order has a clearly defined service term. Users who need continued access must confirm renewal and complete payment before the current term ends. Renewal takes effect only when the new term and billing status appear in the console.

When the term ends without a confirmed renewal, access to the relevant device may stop, and remote sessions, automation tasks, and external connections may be interrupted. The node may then be released for subsequent orders; users should not treat continued access after expiration as a new service term.

Before service ends, users should stop runners, build tasks, and background processes; download necessary artifacts; migrate work data; revoke repository tokens; and remove project materials that are no longer needed. Data recovery requests made after expiration may be impossible if the node has entered subsequent processing.

Cancellation requests must be submitted through a console ticket and include the order number, reason, and preferred handling. Started terms, completed device assignments, add-on resource usage already incurred, and on-chain payments are handled based on the order status and actual performance.

All service nodes are designed to operate normally 365 days a year with no scheduled downtime. VMOak continuously checks the underlying network, device status, storage capacity, and access path, and takes reasonable recovery measures when an issue is found.

If hardware anomalies, security risks, network failures, or upstream service interruptions occur, VMOak may perform emergency checks, isolate sessions, restart services, adjust routes, or replace equipment. We will update the status based on verifiable information during handling, but recovery time depends on the incident type, scope of impact, and required verification steps.

Issues caused by the user’s local network, client configuration, incorrect firewall rules, invalid credentials, intentional shutdown, project processes exhausting resources, or third-party service failures do not mean that the physical node itself is unavailable. Users should first complete the basic checks in the support guide, then submit a ticket containing a timeline and redacted logs.

Force majeure, widespread public-network failures, infrastructure-provider incidents, and other events beyond reasonable control may affect access continuity. VMOak will, where feasible, confirm the impact, isolate risks, restore service, and update the outcome.

View connection and troubleshooting guide

Users are responsible for backing up their work data, source code, repository credentials, model files, media assets, build caches, and final artifacts. Cloud Mac remote access does not replace project-level backups, version control, or disaster recovery arrangements.

Users should maintain at least one independent copy based on the importance of the project and verify that it can be read and restored. Continuous integration jobs should return final artifacts to storage controlled by the user rather than retaining them only in a temporary work directory or on a single device.

Before service ends, users should complete data migration, clean sensitive files, revoke repository tokens, and deregister automation tasks. If the user authorizes team members to operate the device, the user must also ensure that all members follow the same backup, permission, and exit requirements.

During support troubleshooting, VMOak processes only the minimum information needed to resolve the issue. Before submitting logs, screenshots, or configuration snippets, users should remove private keys, complete access credentials, personal identity information, and unredacted business data. Personal information is handled according to the Privacy Policy.

• Code and configurationmust be placed under version control, and the remote copy must be confirmed readable.
• Build artifactsmust be returned to user-controlled storage and verified.
• Keys and tokensmust be issued with least privilege and revoked immediately upon expiration or project departure.
• Work directorymust be migrated as needed and sensitive content removed before service ends.

VMOak is contractually responsible for providing the agreed model, node, term, add-ons, and remote access capability for confirmed orders. Users are responsible for their own code, data, permission settings, choice of third-party tools, software licenses, and operations performed on the device.

Losses caused by user misconfiguration, credential leaks, failure to back up promptly, third-party software defects, or external repository or network-service failures will be assessed according to each party’s actual control over and contribution to the event. Anyone asserting a loss must provide the order number, timeline, relevant logs, and evidence establishing causation.

To the extent permitted by applicable law, VMOak is not liable for unforeseeable indirect losses, lost profits, lost business opportunities, or consequences caused solely by third-party tools. For events beyond control, our approach is to confirm the impact, protect the node, restore service reasonably, and provide timely updates.

For disputes concerning an order, billing, access interruption, or data processing, users should first submit a console ticket stating the order number, time of the issue, desired outcome, and necessary evidence. The parties should first review and discuss the matter based on the order details, operation records, and communications.

These terms are governed by the laws of the jurisdiction where the platform operator is based. Disputes that cannot be resolved through discussion may be submitted to a court with jurisdiction in that jurisdiction.

Updates to these terms will be presented through appropriate channels. Updates that materially affect user rights, billing, or liability boundaries will receive reasonable notice before taking effect; confirmed orders remain governed by the order details and applicable rules in effect when confirmed.