1. Service scope
ArmVNC provides cloud Macs on dedicated physical hosts. Each valid rental order corresponds to one dedicated Apple Silicon physical host running native macOS, not a virtual machine. For the duration of the rental, the host’s compute and storage resources are assigned to that order; they are not replaced by a shared virtual instance.
The service offers two host configurations: Arm Line M4, with M4 / 16GB / 256GB; and Arm Grid M4 Pro, with M4 Pro / 64GB / 2TB. Hosts are available in five locations: Singapore, Tokyo, Seoul, Hong Kong and the eastern United States. Both configurations are offered in all five locations. Check the console for current availability.
Your order includes the resources specified for the selected location, along with the connection details needed for SSH, VNC and macOS Screen Sharing. You can use the macOS desktop and command line for builds, testing and inference. You are responsible for obtaining and managing third-party software licences, project dependencies, signing materials and task configuration. Additional storage and Thunderbolt 5 daisy-chaining must be confirmed separately in the order.
2. Accounts & orders
Choose a host, location, billing period and any add-ons on the order page, then check payment and provisioning status in the console. Before submitting an order, review all selections and the amount due. Payment and host provisioning are separate statuses; rely on the status shown in the console for each. Leaving the payment page or submitting a transfer does not mean provisioning is complete.
Your account email must be accurate, active and able to receive order and service notifications. You are responsible for safeguarding your account verification details, connection passwords, SSH private keys and other access credentials. Change the initial password after your first connection, configure keys and access permissions as needed, and never put sensitive credentials in public repositories or logs.
If you suspect that someone else has accessed your account or host, change the relevant credentials promptly and sign in to the console to open a support ticket. Include your order number, host ID and the time you noticed the issue. If account, billing or provisioning details do not match, raise a ticket to have them checked and avoid duplicate payments or orders.
3. Billing periods & pricing
Billing periods are available by day, week, month or quarter, and all charges are in US dollars (USD). Prices for hosts and add-ons are those shown on the plans page and confirmed in the order details at checkout. The amount due depends on the selected host, billing period and add-ons. Check the location, period dates and each line-item amount before paying.
Billing start and end times are determined by the order record. Not connecting to the host, not running a build, or voluntarily stopping user processes during a rental does not stop billing. Prices for each billing period are listed independently; they are not calculated by adding together prices from other periods. Quotes from previous orders do not apply to new orders unless confirmed.
To change a host, add resources, extend a rental or end it early, first check the available options and charges in the console, then confirm the change. Mid-term upgrades, credits for unused rental time, refunds and renewal arrangements are subject to the terms shown in the relevant order and confirmed by both parties. Nothing on this page automatically approves a change.
Check your renewal status and billing results before the rental expires. A saved payment method or a previous renewal does not mean that the current order has renewed. Whether automatic renewal is enabled, the amount for the next period and the final renewal status are determined by the settings and order records shown in the console.
4. Payment methods
We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. All payments are in USD. Available payment gateways are determined by the backend response. Use the payment details and amount displayed for your current order; do not reuse payment instructions from another order.
For USDT payments, select the TRC20 network and check the address, amount and network fee before sending. Submitting a transfer does not confirm receipt; check the payment status in your order for progress. If a payment is not linked to an order, submit a support ticket with the order number, transaction hash and amount so we can investigate.
Card payments are processed by Stripe. ArmVNC does not store full card numbers. For billing checks, you can provide your order number, transaction reference and a payment receipt with sensitive details redacted. Do not send full card numbers, card security codes or account verification details by email or support ticket.
5. Uptime & service credits
All hosts operate year-round, 365 days a year, with a monthly uptime commitment of 99.9%. Over a 30-day period, this is equivalent to approximately 43 minutes of downtime. This figure describes the commitment; it is not a historical monitoring result or permission for arbitrary service interruptions.
Uptime is calculated based on host availability during the active service period: uptime = (active service time − confirmed affected time) ÷ active service time × 100%. Host unavailability should be distinguished from issues with your local network, client settings or an individual build task. An application error alone does not establish a host outage.
If a host’s monthly uptime falls below 99.9%, service credits are calculated as additional service time based on the confirmed affected period. Sign in to the console and submit a support ticket with your order number, host ID, outage start and recovery times, time zone, connection method and relevant error logs. The support team will review the affected scope and period, then confirm the credit through the ticket.
Downtime caused by events beyond reasonable control or by your own actions is not covered by these credits. Examples include changing network settings, disabling remote access or damaging the system environment. If the cause is unclear, keep the original error messages and timestamps so both parties can review the facts. Service-time credits do not compensate for lost build outputs, business revenue or third-party costs.
6. Acceptable use
You are responsible for the programs you run, the data you store and the network traffic generated on your host. You must have the rights to use the relevant content and software. You may not send unsolicited bulk email, mine cryptocurrency, distribute unlawful content or malware, perform unauthorised scanning or attacks, or engage in activity that infringes another party’s intellectual property or privacy or compromises system security.
Do not use a host to disrupt other users, data centre networks or third-party services, and do not share account credentials with unauthorised people. Batch builds, automation scripts and model workloads must comply with the terms of the software and services they rely on. Automation does not permit you to bypass access controls.
If there is unlawful use, a security incident or an actual risk to the service, ArmVNC may restrict relevant access or suspend the affected service in proportion to the risk, and explain the situation through an available account contact method. You must cooperate with fact-finding, stop the relevant activity and address the risk. If you disagree with the outcome, you can request a review by submitting a support ticket.
7. Data & offboarding
You own and manage the source code, build outputs, caches and user configuration on your host. ArmVNC does not proactively access data on user hosts. If troubleshooting requires you to share logs, provide only information relevant to the issue and redact keys, tokens and other sensitive details.
Keep independent backups; do not treat your rental host as your only copy of your data. Before upgrading or reinstalling the system, migrating or ending your rental, export your source code, signing materials, build outputs and any required configuration, and verify that the backup can be restored. Files that remain accessible on the host are not a separate backup.
When your rental expires or ends, the entire host is erased, and its data will no longer be available for recovery. Export your data before the service ends; do not rely on an additional retention period. Renewal is determined by the order status. An incomplete payment does not delay erasure.
Account, order, payment verification and support-ticket records are handled separately from data on the host. To ask about these records or request deletion, sign in to the console and submit a support ticket, or email support@armvnc.com. Include the information needed to identify your request.
8. Liability & risk allocation
ArmVNC is responsible for providing the physical host resources, connection details and agreed support for confirmed orders, and for reviewing uptime and credits under these terms. You are responsible for your projects, software licences, access permissions, system configuration and data backups. A dedicated physical host does not guarantee that every project will build successfully or that every third-party service will approve or process it.
Build times, model performance, remote display quality and end-to-end transfer speeds depend on factors such as project size, software versions, workload and your network. Validate performance with your own project. Changes to third-party tools, errors in your configuration and issues with your network should be addressed according to their respective causes; they do not automatically count as host uptime incidents.
For issues arising from ArmVNC’s failure to meet its commitments, both parties will determine responsibility based on the order, incident records, actual impact and applicable law. Apply for service-time credits for uptime issues under Section 5. For other disputes, set out the relevant facts and requested resolution separately; estimated losses that have not been verified are not confirmed liabilities.
Nothing in these terms excludes or limits liability where applicable law does not allow it, or reduces rights you have under applicable law. If an event beyond reasonable control occurs, both parties should promptly discuss its impact and take reasonable steps to minimise losses.
9. Changes & disputes
ArmVNC may update these terms in response to changes in the service, billing processes or compliance requirements, and will publish the revised text and details of when it applies. Any material change affecting existing orders will be explained. New orders are subject to the terms and prices displayed and accepted when the order is submitted.
If you have questions about an order, billing, uptime or data handling, first sign in to the console and submit a support ticket, or email support@armvnc.com. Include your order number, the relevant facts and the outcome you are seeking. Keep payment and communications records so both parties can review the matter.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. The parties will first try to resolve disputes through discussion. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction. Mandatory rights under applicable law are not limited by these terms.