1. Service overview
MetalVNC provides Cloud Mac rentals on Apple Silicon M4 Mac mini systems. Each rental is a dedicated physical machine, not a virtual machine. During the rental term, the node’s CPU, memory, and local storage are not shared with other renters. The service includes macOS with a graphical interface and command-line environment, accessible via VNC desktop or SSH.
Our catalog offers two plans: MetalBench 16 (M4 / 16GB / 256GB) and MetalBench 24 (M4 / 24GB / 512GB). The four Asia-Pacific locations are Singapore, Tokyo, Seoul, and Hong Kong. Your order, confirmed before payment, determines the configuration, billing period, and add-ons. Check the Console for real-time availability.
Renting a physical node does not grant licences for third-party software or provide local peripherals or dedicated test devices. Before paying, confirm support for any specific peripherals, toolchain versions, parallel workload sizes, or multi-machine connections you need. We do not guarantee that your projects, scripts, or third-party dependencies will run without modification.
2. Accounts & setup
Register and sign in through the Console. Select a configuration, review the charges, and pay during checkout; delivery details will then appear in the Console. Provide a valid email address that can receive notifications, keep your account credentials secure, and take responsibility for authorised orders, renewals, and configuration changes made through your account. Never expose connection credentials in public code repositories, build logs, or support ticket attachments.
Payment submission, payment confirmation, and machine delivery are separate statuses. Check the order status, instance status, and delivery details shown in the Console to confirm that service is active; a redirect from the payment page alone is not confirmation. Setup time depends on payment confirmation, the selected configuration, and delivery checks. Process descriptions on the site do not guarantee a fixed delivery time for every order.
When you receive your delivery details, check the model, location, rental term, and add-ons, then test your connection promptly. If anything differs from your confirmed order, keep your order number and submit a support ticket through the Console. If you have trouble accessing your account, contact support@metalvnc.comfrom your registered email address, describe the issue, and complete any necessary identity checks.
3. Billing & payment
Service is prepaid by the day, week, month, or quarter. See the plan page for published prices; the amount due is the one shown in your order confirmation before payment. Base configurations and add-ons, including storage upgrades and Thunderbolt 5 daisy-chaining, are priced separately. Check the selected term, quantity, add-ons, and total before paying. Billing continues during the rental term after delivery, even if you do not sign in or run any tasks.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are charged in US dollars (USD). Available payment gateways are determined by the response from our backend. For USDT-TRC20 payments, carefully check the network, address, amount, and order details shown on the payment page. Payment is confirmed by the order status, not by a transfer screenshot.
You can review invoices, order totals, and payment status in the Console. If a charge does not match the order status, you are charged twice, or you dispute an amount, submit your order number and any necessary transaction records. Do not send your full card number, card security code, or account password. Contact us before paying if you have a special billing documentation request.
4. Renewals, upgrades & refunds
Check the expiry time shown in the Console and renew in good time. Keep your notification email address active. Expiry reminders are there to help you manage your rental; you are still responsible for checking your term. Not receiving or reading a reminder does not extend your rental automatically. Confirm successful renewal in the Console; starting a payment is not the same as completing a renewal.
Before upgrading, changing plans, or adjusting add-ons, confirm the target configuration, applicable term, migration requirements, and any impact on existing connections. Any price difference must clearly show the target configuration cost, the remaining service value from the original order that can be credited, and the cost of new add-ons. We will proceed only after you confirm; an unconfirmed estimate will not be used as the final charge. Changing plans does not automatically migrate your existing data or running tasks, so arrange backups and migration in advance.
To cancel an order that has not been set up, submit a support ticket first so we can check whether payment was made, delivery has started, and a refund is available. Refund requests for delivered orders are reviewed individually based on delivery records, actual usage, incident records, and the refund terms that applied before payment. Unused rental time does not automatically qualify for a pro-rated refund. Refund eligibility, amount, process, and expected timing are subject to the applicable order terms and written outcome of our review; these terms do not promise a fixed refund processing time.
5. Uptime commitment
We commit to 99.9% monthly uptime. All locations operate continuously, 365 days a year. Monthly uptime is calculated over the valid service period for that month: total service minutes, less verified minutes of unavailability attributable to the service, divided by total service minutes. For rentals that start or end during the month, only the valid service period is counted.
If monthly uptime falls below 99.9%, we will credit 10 times the verified downtime that qualifies under this commitment as additional service time. This is a service-time credit, not a cash refund. To help us review service logs and the impact, submit a Console support ticket with the instance ID, outage start and end times, and connection error records showing the time zone.
We distinguish service-side failures from issues in your own environment when assessing downtime. Time caused by you shutting down the machine or changing network or security settings, incorrect credentials, local network failures, third-party software issues, or force majeure is not counted as service-side downtime. A failed task or crashed application alone does not mean the node was unavailable. If you disagree with our assessment, provide evidence in the same support ticket for review.
6. Acceptable use
Use the service for authorised development, builds, testing, remote work, or computing experiments, and comply with applicable requirements and Apple’s software licence agreement. Do not use a node for cryptocurrency mining, spam, attacks on others, scanning or accessing systems without authorisation, malware distribution, or any other activity that harms networks or the rights of others.
Ensure you have the necessary rights to use any code, models, data, certificates, or other files you upload. When running a self-hosted runner or accepting external build jobs, restrict job sources and access to credentials; do not expose long-lived keys to untrusted jobs. Check third-party software licences, compatibility, and usage restrictions before deployment.
If we identify abuse, a security incident, or activity that could affect other users or infrastructure, we may take proportionate measures, including restricting connections, isolating an instance, or suspending service, and keep records as necessary. You must cooperate with our investigation and stop the activity in question. If you disagree with our response, submit an explanation and supporting evidence through the Console.
7. Data responsibilities
You are responsible for backing up and testing the recovery of your business data, source code, build artefacts, and important configuration. Renting disk space, adding a data disk, or keeping an instance online does not include a backup service. Keep important backups somewhere separate from the rented node and regularly check that they can be restored. Export any data you need before reinstalling, migrating, changing plans, or deleting it.
Data retention and erasure after expiry follow the timeframe agreed for your order. Check the relevant terms before paying. If your order does not specify a timeframe, confirm it by support ticket rather than assuming a default retention period. Expiry does not mean that accessible storage will continue to be provided, and suspended access does not mean data will be kept indefinitely.
Once the agreed retention period ends or service is terminated under the applicable terms, node data may enter the erasure process. After erasure, you should not expect to recover it. To submit a data-handling request, use the email address on your account or a Console support ticket, and include your instance and order IDs. We will not ask you to share complete business data or secret credentials through public channels for troubleshooting.
8. Liability & termination
We provide access to physical nodes and related support within the scope of your confirmed order. We do not guarantee that your application will pass review, builds will succeed, model outputs will meet your expectations, third-party platforms will be available, or you will achieve specific business results. Remote connection quality also depends on your local network, routing, and client configuration; node availability does not mean every connection route will have the same latency.
If a service dispute arises, responsibility will be assessed based on the order, incident records, actions by both parties, and actual impact. Uptime credits are handled under Section 5. Other refund or loss claims are handled under the applicable order terms and applicable law. These terms do not exclude liability that cannot be limited or waived under applicable law, nor do they replace a review of the specific facts with a blanket provision.
Service may end when the rental term expires without renewal, when you request termination, following a serious breach of the acceptable use requirements, or when termination is legally required. For issues that can be corrected, we will explain what action is needed, taking the level of risk into account. In the event of an urgent security risk, we may first take necessary steps to restrict service and notify you afterward. Fees, opportunities to export data, and erasure after termination are handled according to the order terms and relevant notices.
9. Changes & disputes
Before placing an order, read and save the terms and order confirmation that apply at that time. We will notify you of material changes affecting service scope, fee responsibilities, or user rights through a site notice, a Console notification, or your account email, and explain their scope and effective date. Updates to this page alone will not make new charges apply retroactively to confirmed orders.
These terms are governed by the laws of the jurisdiction where the platform operator is based. If a dispute arises, the parties should first explain the facts, order number, and requested outcome by support ticket or email, and try to resolve it through discussion. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction.
For help interpreting these terms, checking order conditions, or making a formal request, pleasesubmit a support ticket in the Consoleor email support@metalvnc.com. Confirm your configuration and applicable terms before paying. If anything is still unclear, get a written response first.