Clear rules for node rentals, account responsibilities, and acceptable use

By accessing the OakVM website, creating an account, placing an order, completing payment, or using a node, you confirm that you have read and accepted the currently published Terms of Service. If you act for a company, team, or other organization, you confirm that you are authorized to accept these terms on its behalf and bind members authorized to use the account and nodes.

“User” includes the account registrant, payer, order contact, authorized team members, and anyone accessing nodes through user-configured automated tasks. The account holder must ensure that all such users understand and follow the same rules, and may not avoid account responsibility through shared access, scripts, or third-party integrations.

If you do not agree to the current terms, stop registering or ordering. Orders already in effect remain subject to the rules applicable when they were confirmed, including settlement, data export, and node return.

OakVM provides Cloud Mac and dedicated Apple Silicon physical node rentals. Each valid order corresponds to a dedicated physical machine with a specified configuration. It is not a virtual machine, and its computing resources are not split among unrelated orders.

Available configurations are the base tier (M4, 16GB, 256GB) and Pro tier (M4 Pro, 64GB, 2TB). The model, memory, storage, node region, rental term, and add-ons you receive are determined by the order confirmation and console records. Additional SSD storage and Thunderbolt 5 pooling apply only when expressly listed in the order.

Nodes may be used for the macOS graphical interface, command line, Xcode, automated builds, self-hosted runners, testing, and engineering workflows that comply with these terms. Users configure and validate software versions, project dependencies, signing assets, and task scripts for their own project requirements.

Users must provide genuine, accurate, and reachable account and order details, and update them promptly when an email address, team lead, or payer changes. Incorrect or outdated information may prevent delivery of verification codes, order notices, security alerts, or support replies.

Users must protect account login credentials, node access credentials, SSH keys, automation tokens, and runner registration details. Do not publish them, share them without proper controls, or provide them to unauthorized people. Teams should assign access by role and revoke permissions promptly when a member leaves the project.

Orders, renewals, configuration changes, node connections, ticket submissions, and data operations initiated through a user account are generally treated as actions of the account holder. If you discover an unusual login, unknown order, exposed credential, or unexplained node activity, change the relevant credentials immediately and submit a ticket through the console or email support@oakvm.com.

OakVM may require reasonable identity or order verification to confirm that high-risk actions come from the account holder. Verification is limited to information necessary to make the security determination.

Available rental terms are daily, weekly, monthly, and quarterly. The rental term begins after the order is confirmed and the node is assigned; the console record determines the exact start and end status. Check the model, region, term, additional storage, pooling options, and contact email before confirming an order.

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 regions. Both available configurations can be ordered in these regions; availability is based on the console’s live status. After a region is set, submit a ticket before migration to confirm data handling, network changes, and execution details.

Standard delivery includes payment confirmation, node assignment, access credential generation, and an initial connection check, and takes about 4 minutes overall. This describes the standard process and does not change the actual order status shown in the console. Delivery may wait for additional information if security checks, payment confirmation, or user details require clarification.

After receiving access credentials, users must check the model, memory, storage, region, system time, and network connectivity. If the node does not match the order, submit a ticket before writing project data and include the task ID and necessary redacted information.

All prices and settlements are in US dollars (USD). OakVM supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available gateways are determined by the options returned by the backend at checkout.

Before order confirmation, the selected model, rental term, region, additional SSD, number of Thunderbolt 5 pooling connections, and total amount due are displayed. Review these items before paying; payment confirms the parameters and amount listed for the order.

Payment status must be confirmed by the applicable payment flow. If the transaction ID, payment amount, network type, or card authorization details are incomplete, OakVM may request records sufficient to verify the order. Do not send complete payment credentials, private keys, or other sensitive authentication material through public pages, ordinary email text, or unauthorized channels.

A renewal or new node is a new order action and uses the prices and parameters displayed at submission. A node whose renewal is not completed on time may stop being accessible when the current term ends. Export data, confirm renewal, or wrap up tasks before the rental term expires.

Users may use nodes for lawful software development, building, testing, automation, model validation, and team collaboration. Do not infringe another person’s systems, networks, data, intellectual property, or legal rights, or ask OakVM to help perform unauthorized activities.

Prohibited Activities

• Conducting unlawful activities or storing or distributing content that may not lawfully be handled.
• Accessing another account, device, service, code repository, or network resource without explicit authorization.
• Conducting destructive scans, denial-of-service attacks, malicious traffic amplification, mass vulnerability exploitation, or access-control bypasses.
• Selling, publicly sharing, or abusing account credentials, node credentials, keys, tokens, or payment information.
• Running tasks that continuously affect node hardware, upstream networks, or other users’ normal connectivity.
• Falsifying identity, order records, support materials, or information used for security verification.

Automated tasks must use reasonable concurrency, timeout, retry, and logging settings. Avoid infinite loops, uncontrolled retries, unbounded disk writes, and unrestricted network requests, and stop affected tasks promptly when abnormal resource usage is detected.

Users are responsible for data they upload, generate, or sync to a node, including source code, dependency caches, certificates, private keys, provisioning profiles, environment variables, build logs, archives, and exported artifacts. Users must ensure they have the authorization required to process this data and follow project, client, and team security rules.

A node must not be the only copy of code or artifacts. Back up critical repositories, signing materials, build configuration, and release artifacts to a secure location under your control, and regularly verify that backups can be restored. Export data before the rental term ends, an order is terminated, the user reinstalls the system, or cleanup is performed.

For team collaboration, manage shared directories, personal workspaces, build caches, and signing assets separately. Redact tokens, keys, user data, and payment information before submitting support requests. Rotate or revoke the keys, automation tokens, and runner registration details of departing members promptly.

Users can learn how account details, order records, access logs, and support information are handled from the Privacy Notice. Submit privacy requests and service-data issues through the same support email, identifying the request type in the subject for verification and routing.

OakVM nodes are provided for normal operation 365 days a year. Users may run builds, tests, and remote tasks throughout their rental term, but should maintain recoverable procedures for network fluctuations, hardware faults, upstream service failures, and errors in their own scripts.

In response to security incidents, hardware failures, network issues, attack traffic, data risks, or legal obligations, OakVM may take necessary measures such as isolating the network, limiting abnormal tasks, resetting affected credentials, moving a node, or temporarily restricting access. Measures should match the risk, with progress communicated through account notices, order status, or ticket updates where practicable.

Support covers order checks, node delivery, basic connectivity, hardware status, regional networking, and platform-function issues. Project code errors, dependency conflicts, third-party tool behavior, signing configuration, build-script design, and software installed by the user generally require the user to diagnose the project first; OakVM may help identify service boundaries using redacted logs.

When service changes are needed because of hardware generations, regional capacity, network architecture, security requirements, or legal obligations, OakVM will make reasonable efforts to provide advance information about material effects on user tasks. Changes involving models, regions, prices, or order parameters take effect through explicit order confirmation and not through vague notices.

OakVM may suspend access to an account, order, task, or node when a rental term expires without renewal, payment status is abnormal, acceptable-use rules are breached, an account or node presents a clear security risk, necessary verification is refused, or legal obligations require action. Where a narrower measure can control the risk, OakVM should first limit the affected part.

For issues that can be corrected, users may provide the requested information, stop prohibited tasks, rotate credentials, or complete payment verification as specified in the ticket. OakVM may terminate the relevant services in cases of serious unlawful conduct, ongoing attacks, repeated credential abuse, deliberate disruption of network stability, or refusal to eliminate a material risk.

Users may choose not to renew and must stop tasks, export data, revoke credentials, and complete team handover before the current rental term ends. Access may close after service ends, so last-minute data export should not be treated as a routine backup method.

To the extent permitted by applicable law, each party is responsible for direct losses caused by its own breach of these terms, infringement of another person’s rights, failure to protect credentials properly, or failure to perform its obligations. Liability should be assessed in light of the order, foreseeable risks, each party’s actual control, and reasonable remedial measures taken.

Impacts caused by force majeure, the user’s own actions, failures in the user’s project or dependencies, unauthorized third-party conduct, or the user’s failure to follow security instructions must be allocated according to the actual cause and scope of control. No liability limitation excludes obligations that applicable law does not permit to be limited.

OakVM may update these terms to reflect service features, order processes, security requirements, or legal obligations. New versions will state their version status; changes that materially affect user rights or obligations will receive reasonable notice through the website, account notifications, or the order process.

Updated terms apply to subsequent access, registration, orders, and renewals from the stated effective point. For confirmed orders, the model, rental term, region, and amount paid remain governed by the order record, except where legal or security requirements must apply immediately.

These terms are governed by the law of the jurisdiction where the platform operator is based. In a dispute, the parties should first use a support ticket or formal email to state the order number, dispute, desired resolution, and relevant evidence, and communicate in good faith. If negotiation does not resolve the matter, proceedings may be brought before a court with jurisdiction in that jurisdiction.

Terms, orders, payment matters, security reports, privacy requests, and formal notices may all be sent to support@oakvm.com. Users with an existing account may also sign in tothe console to submit a ticketand include the task ID, time of occurrence, node region, and redacted logs.