1. Service overview
VMFly rents dedicated physical Apple Silicon Mac mini computers, not virtual machines. During the rental term, each physical computer is assigned to a single customer. Customers can use the macOS graphical interface and command line to configure development tools, run builds, and manage their work files. A dedicated computer does not mean exclusive access to the data centre’s upstream network.
Two models are available: Glide M4 with Apple Silicon M4, 16GB of memory, and a 256GB SSD; and Cruise M4 Pro with Apple Silicon M4 Pro, 64GB of memory, and a 2TB SSD. Both models are available in all four data centre locations: Singapore, Tokyo, Seoul, and Hong Kong. Availability at the time of ordering is shown in real time in the dashboard.
The service covers the physical node, rental term, and any add-ons listed in the order. Customers are responsible for project migration, application debugging, build scripts, and third-party software licences. If you need assistance, confirm the scope of work in a support ticket first. Build times and the behaviour of third-party tools should not be taken as a general performance guarantee for every project.
2. Account & setup
When registering, use a valid email address that you or your team are authorised to control and can continue to receive notifications at. Complete the verification and password setup steps. Keep your account details accurate and up to date. Teams should designate an account owner to avoid losing order access if someone leaves, an email account is deactivated, or credentials are not handed over.
Submitting a configuration does not mean a physical computer has been assigned. VMFly begins allocating and initializing the computer after payment is confirmed. The dashboard is the source of record for order status, service dates, and connection details. If payment is still processing, check the billing status first to avoid making duplicate payments.
Keep your account password, node credentials, SSH private keys, and CI/CD access tokens secure. Change the initial access password promptly after receiving your node, and restrict access according to your team’s policies. If you notice an unusual login or a credential leak, replace the affected credentials immediately and report the node ID and issue in a dashboard support ticket. Never paste passwords or private keys into public logs.
3. Billing & payment
Nodes are available for daily, weekly, monthly, or quarterly rental. All prices are charged in US dollars (USD). The model, rental term, node, and any add-ons together make up the order configuration. The amount due, service dates, and renewal price are those shown on the invoice before submission and in the confirmed order. Each rental term has its own listed price; do not calculate prices for other terms by simply multiplying the daily rate.
Payment is accepted only in USDT-TRC20 or by Visa, Mastercard, or Amex processed through Stripe. The payment gateways actually available are determined by the backend response. For USDT-TRC20 payments, check the network, recipient details, and amount shown on the payment page, and keep the transaction hash. For card payments, rely on the payment confirmation in the invoice rather than the browser’s return page alone.
The +1TB SSD, +2TB SSD, and Thunderbolt 5 linking add-ons are billed according to the selected rental term. Thunderbolt 5 linking is charged per computer. Check each add-on’s quantity and term before placing your order. To add or remove an add-on or change models, first confirm the available process and applicable charges in the dashboard. Submitting a question or changing your local configuration does not automatically modify a confirmed order.
4. Renewal, expiry & data
VMFly provides reminders before a rental expires, but you are responsible for checking the expiry date in the dashboard and arranging renewal. Email filters, an inactive account email, or unread reminders do not extend the rental term. If a pipeline is expected to run past the expiry date, confirm that renewal payment has been completed in advance; creating a renewal invoice alone is not enough.
Nodes that are not renewed will stop service after expiry and have their entire disk erased before being assigned to another customer. Before expiry, back up your source code, certificates, build artifacts, environment manifests, and anything else you need to keep somewhere outside the node. Once service has stopped, do not rely on being able to connect to the node, and do not treat an expiry reminder as a promise to retain your data for longer.
A node is not your only backup. Data cannot be recovered by renting the node again after its disk has been erased. Changing models or moving between data centres requires a new node, and customers are responsible for transferring their data. Complete environment checks and build validation before the old node expires. Migration questions, refund requests, and unresolved support tickets do not pause expiry processing. Any extension must be explicitly confirmed.
5. Refunds
Refund requests are reviewed individually, taking into account order delivery, the period of use, the reason for the issue, and verifiable records. You may request a review if you were charged more than once, payment was confirmed but the service was not delivered, or a service fault affected the node’s agreed use. Submitting a request does not mean a refund has been approved. If you paid more than once, first check whether the payments relate to separate orders.
A billing period that has already started is not automatically refundable if you stop your tasks early, your project requirements change, you do not log in to the node, or you do not use an add-on. If you believe the service was not delivered as ordered, provide the time the issue began and was resolved, the node ID, and any relevant error records. We will review the scope and impact of the issue and the steps taken to address it before determining an appropriate resolution. No standard refund percentage is promised before review.
Submit a support ticket in the dashboard. If you cannot log in, email support@vmfly.com with your order number, payment method, amount, reason for the request, and any necessary payment records. For USDT-TRC20 payments, provide the transaction hash, never your private key. For card payments, do not send your full card number. We will provide details about eligibility, amount, process, and expected timing after reviewing your request.
6. Acceptable use
You must use the node lawfully and have the necessary rights to the software you install, the data you upload, and the network activity you initiate. You must not use the service for mining, sending spam, cyberattacks, distributing malware, stealing credentials, scanning other people’s systems without authorization, or any other unlawful purpose. You must not evade these requirements by hiding processes, reselling access credentials, or using other methods.
Build scripts, dependency installation processes, and CI runners may execute external code. Restrict permissions for untrusted jobs, review builds from external contributors, and protect repository tokens, signing materials, and deployment credentials. A dedicated computer does not replace code review, access controls, or dependency security checks, nor does it mean that any third-party program can run without restriction.
If we identify a clear violation or a security risk to the service or other systems, VMFly may take measures based on the risk, including restricting connections, suspending service, or terminating the relevant order. Where practicable, we will explain the reason and next steps. You must cooperate by providing relevant records. If you disagree with our response, you may submit the facts and evidence in a support ticket for review.
7. Availability & fault handling
All nodes run year-round, 365 days a year, with no scheduled downtime. You can run builds and automation continuously, but you should still plan for retries and data backups in case of hardware faults, network issues, events beyond reasonable control, or user error. A successful connection at one point in time does not guarantee that future network requests or build jobs will never be interrupted.
If a node cannot be reached, storage behaves unexpectedly, or a build suggests a hardware issue, save the error details and open a support ticket with the node ID, when the issue first occurred (including the time zone), connection method, and troubleshooting steps already taken. VMFly will check the physical computer and service status. If a hardware fault is confirmed, we will coordinate the replacement computer and provide updated connection details.
Replacing a physical computer does not guarantee that data on the original disk can be transferred. If the original device can be read, we will confirm the data handling options separately. If it cannot be read, you must restore your data from your own backups. We will share fault updates, service changes, and any required actions through dashboard support tickets or your account email. Any fee adjustments or refunds related to a fault will be reviewed under Section 5; no fixed recovery time is promised unless explicitly confirmed.
8. Limitation of liability
You are responsible for your source code, certificates, access tokens, software licences, build artifacts, and the integrity of your backups. You should verify that your backups can be restored. Issues caused by scripts deleting files, changes to system settings, leaked credentials, incompatible software, or unauthorized software will be assessed based on their actual cause and should not automatically be treated as faults in the physical node delivery.
VMFly is responsible for delivering the node as agreed, maintaining billing records, and handling service-side faults. If an issue is caused by a third-party code repository, dependency source, software distribution service, or your network connection, the source of the impact should first be identified. A dedicated computer does not give VMFly control over these third-party systems, nor does it guarantee that a particular app review, signing, release, or model run will succeed.
Both parties should take reasonable steps to limit losses caused by faults, including retaining necessary logs, reporting issues promptly, and avoiding repeated actions that could damage data. Responsibility will be assessed based on the actual cause, verifiable losses, the order terms, and applicable law. Nothing in these terms excludes or limits liability that cannot be excluded or limited under applicable law, and general statements about liability do not replace an investigation of a specific service issue.
9. Changes & contact
VMFly may update these terms to reflect changes to the service scope, billing processes, or compliance requirements. Updated terms and their effective date will be published on this page. We will notify you through the dashboard or your account email of changes that materially affect the rights or obligations under existing orders. The configuration and price of a confirmed order are governed by its order record and applicable terms; updates to this page do not automatically change them.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. For disputes about the service, billing, or interpretation of these terms, the parties should first communicate in writing to review the facts and seek a resolution. If they cannot resolve the dispute, it will be submitted to a court of competent jurisdiction in that jurisdiction.
For account, node, billing, refund, or terms-related matters, log in to the dashboard to submit a support ticket or email support@vmfly.com. Include your order or node ID and a brief description of the issue. Do not send passwords, private keys, or full payment card details. If we need to verify account ownership, please confirm it using your registered email address.