1. Service overview
OSXFlow provides cloud Mac rentals. You rent a dedicated physical Mac mini, not a virtual machine. For the duration of your rental, the assigned Mac’s CPU, GPU, unified memory and system storage are not shared with other customers. You get full access to the macOS GUI and command line to configure development, build, testing and inference environments for your permitted use.
Our catalog includes two configurations: Flow M4 (M4 / 16GB / 256GB) and M4 Pro (64GB / 2TB). Both are available in five locations: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the US East Coast. Check the console for real-time availability. Your confirmed order defines the configuration, location, rental term and add-ons included in your service.
Locations operate year-round, 365 days a year. Uptime is calculated as described in Section 5. The estimated four-minute delivery time applies to the standard setup process; it is not a guaranteed completion time for every order. Check the console for the actual status of payment confirmation, system readiness and credential handoff. Application performance also depends on your workload, configuration and network connection. A dedicated Mac does not guarantee build times or model throughput.
2. Accounts & setup
Create an account with an email address that can receive messages, and keep your login details, verification codes and connection credentials secure. Keep your account email up to date to receive order and service notifications. You are responsible for activity carried out using accounts you authorize. If you notice an unfamiliar login or exposed credentials, change the relevant passwords promptly and notify us through a console support ticket.
To get started, create an account, choose a configuration and location, confirm the billing term and any add-ons, pay, then wait for a physical node to be assigned and the system to be ready. You can then retrieve your VNC / SSH credentials. Check your order details before paying. You can use a node only after payment is confirmed and delivery is complete. Opening the payment page does not mean payment has succeeded, and successful payment does not mean the system is ready.
After your first connection, change the default password, configure SSH keys if needed, and grant access only to team members who need it. View and manage credentials only in the console after signing in. Never put them in public repositories, build logs or public support-ticket attachments. When asking us to investigate an issue, provide the order number, node ID, error details and time of occurrence. Do not send passwords, verification codes or private keys.
3. Billing & payments
Pay in advance for a day, week, month or quarter. The price, dates covered by your chosen term, add-ons and total due are shown in the order details you confirm. Monthly billing periods are 30 days. The base configuration, SSD expansion and Thunderbolt 5 bonding are priced separately; check each item when confirming your order. We will not replace the amount due with a prorated price based on another billing term.
We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. All payments are charged in US dollars (USD). Available payment gateways are determined by the response from our backend. For USDT-TRC20, check the network, recipient address and amount, then wait for on-chain confirmation. For card payments, rely on the payment processor’s result and your order status—not just the page you are redirected to.
Do not send payment to an address that is not specified in your order, and do not pay again while your order status is unclear. If you have been charged but your order is unconfirmed, the amount is incorrect, or you paid more than once, keep your order number and transaction records and contact us through a console support ticket. Redact sensitive details from card statements; for USDT-TRC20, you can provide the transaction hash. Any billing adjustment, refund or payment dispute will be reviewed against the order status, service delivered and applicable law. No outcome is guaranteed.
4. Renewals, expiry & data erasure
To renew, confirm the amount and pay in the console. The updated expiry date on your order confirms a successful renewal. Do not assume your rental has been extended based only on a payment action or email notification. To extend your rental or change billing terms, check your current subscription status and the options in the console in advance. Before changing the configuration, location or add-ons, confirm how the change will be made, any fees and when it takes effect, then plan your workload transition.
If your rental expires without a completed renewal, your right to use the service ends and the node may stop accepting connections. After the rental ends, the entire disk is erased before the node is assigned again. We do not guarantee data retention after expiry. Projects, certificates, caches, model files and other user data are not recoverable after erasure. Export anything you need before your rental ends.
You own the data you store on the node and are responsible for deciding what to back up and how often. We do not access your business files unless you authorize us to help troubleshoot an issue; if so, specify the scope in a support ticket. Neither the node nor additional storage should be treated as a standalone backup. Back up source code, essential keys and files that cannot be recreated to another location you control, and verify that you can restore them.
5. Uptime commitment & credits
OSXFlow commits to 99.9% service uptime. Over a 30-day period, that allows for approximately 43 minutes of downtime. This figure explains how the commitment is calculated; it is not a record of past monitoring or scheduled downtime. We assess uptime based on verified records of service unavailability for the affected node. A failed application build, slow access to a particular website or an issue with your local client does not, by itself, mean the node was unavailable.
If verified downtime attributable to our service exceeds that allowance, the excess time is credited as additional service time, not converted into a cash refund. Force majeure events and downtime caused by your own actions are not eligible for credits—for example, disabling a required connection service, changing network settings and losing access, or damaging the system through an operational error. We will explain how we calculated the credit based on the facts of the incident.
Within 7 days after the issue ends, sign in to the console and submit a support ticket with the node ID, order number, outage start and end times and time zone, connection method, and relevant error records. If you do not yet know when the issue will end, report it first and send the remaining details later. After investigating, we will explain the affected scope, eligible downtime and credit in the ticket. The same incident affecting the same node during the same period will not be credited more than once.
6. Prohibited uses
You may not use a node for cryptocurrency mining, bulk unsolicited email, attack scanning, distributing malware, unauthorized system access, or storing or distributing infringing content. You also may not use the service for fraud, data theft, disrupting another party’s systems or any activity that violates applicable law. Having a dedicated physical Mac does not exempt you from authorization requirements, software licenses or network-use restrictions.
You must have the legal right to use your project code, models, datasets, software and certificates. These terms also apply when your team members, automated jobs or third-party programs use a node. You must obtain explicit authorization from the owner of a target system before conducting security testing. Do not use a cloud node to scan or attack unrelated targets.
If we detect suspected violations or activity that threatens the security of the platform or a third party, we may take necessary steps, such as restricting connections, suspending the affected service or stopping the prohibited use. We will explain our actions through your account channels. In urgent situations, we may need to act first. If you believe we have made a mistake, submit a console support ticket or email support@osxflow.com with your order details, an explanation of your intended use and proof of authorization to request a review.
7. Limitation of liability
We are responsible for delivering the dedicated physical node specified in your order, providing account and billing management, and issuing eligible uptime credits under Section 5. You are responsible for the node’s business configuration, lawful use, access permissions and data backups. Before installing dependencies, changing system settings or running batch jobs, assess resource use and recovery options. Keep reproducible steps and necessary data copies for important tasks.
Each party is responsible for its own actions and omissions, as determined by the applicable law. Claims for loss must be supported by evidence of actual loss, causation and reasonable documentation. Liability for indirect losses arising from project revenue, business opportunities or third-party contracts will be determined under applicable law and based on the facts; it is not assumed solely because you rented a node. Uptime credits cover the service time described in Section 5 and are not a guarantee of business outcomes or compensation for business losses.
Nothing in these terms excludes or limits liability that cannot be excluded or limited under applicable law, or affects any mandatory rights you have under that law. If a dispute arises, keep your order, support tickets and incident records, and explain what you want resolved. The parties should first verify the service facts and billing records before discussing a remedy, to avoid repeated actions or additional losses while the evidence is still being reviewed.
8. Changes & governing law
We publish updates to these terms on this page. For significant changes to billing, service scope or data handling, we will explain the changes and when they take effect through your account notification channels. New orders are subject to the terms published when you confirm them. Updates to this page do not retroactively change the terms of an active order. If an adjustment to an existing service is necessary, we will explain its impact and the available options.
These terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first try to resolve disputes through a support ticket or email. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction. If any provision is held invalid, the remaining provisions that can operate independently will remain in effect, unless otherwise required by law.
If you have questions about these terms, your order or how credits are calculated, sign in to the console and submit a support ticket, or email support@osxflow.com. Include your order number and the specific section in question so we can review it. Once you accept these terms, choose a configuration, location and rental term that suit your needs and place your order.