1. Service overview
MergeMac provides dedicated physical Mac mini cloud workstations allocated for a selected rental term. Each node is a physical machine, not a virtual machine. For the duration of your rental, the allocated machine's CPU, GPU, unified memory, and local storage are reserved exclusively for your order and are not shared with other tenants. You can use the macOS graphical interface and command line through the connection method provided to develop, build, test, and run experiments that comply with these terms.
The current catalogue has two configurations: Base M4 (M4, 16GB RAM, 256GB SSD) and Trunk M4 Pro (M4 Pro, 64GB RAM, 2TB SSD). Our five nodes are in Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast. Your confirmed order and console records determine the specific configuration, node, billing period, and add-ons. Availability is shown in real time in the console.
Your rental gives you the right to use a machine; it does not transfer hardware ownership or automatically include commercial licences for your apps, build dependencies, or third-party software. Check that the configuration meets your engineering requirements before ordering. Changing nodes requires a new order, and you should not assume that an existing environment or its data will be migrated automatically.
2. Accounts and eligibility
You must be legally able to enter into and fulfil a service agreement. If you order on behalf of a company or team, you must have authority to accept these terms, pay the charges, and manage the relevant machines. When registering and using an account, provide a valid email address that can receive notifications. Keep your account, order, and support details accurate and up to date.
You are responsible for safeguarding your login details, verification codes, SSH keys, and VNC credentials. Never put verification codes or complete connection passwords in public repositories, build logs, or support emails. To give team members access, use separate machine accounts, keys, and project permissions to limit access appropriately. Avoid sharing a single set of privileged credentials.
If you notice an unusual login, an order you did not place, or exposed credentials, replace the affected credentials immediately and submit a ticket through the console. If you cannot log in, contact support at support@mergemac.com. We may ask for an order number and the information needed to verify account ownership. We will not ask you to email a full card number or a signing private key stored on your machine.
3. Billing and renewals
Machine rentals are available with daily, weekly, monthly, and quarterly billing periods. All charges are in US dollars (USD). Check the machine price, storage upgrades, and Thunderbolt 5 daisy-chaining charges separately before paying. Each of the four billing periods has its own catalogue price; do not calculate another period's price by multiplying the daily rate by the number of days. The amount due is the one shown in your confirmed configuration and order details.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment gateway returned by the backend determines which options are available for your order. For USDT-TRC20 payments, carefully check the network, receiving address, currency, and amount shown in your order. An on-chain transfer does not mean your order has been paid; check the payment confirmation in the console. Card payments are also subject to the order status. Avoid paying more than once by repeating a payment attempt.
Your rental start and end times are determined by the order and instance records in the console, not by the time you first connect to the machine. Renew before your current term ends, and check the new expiry date. Renewals use the same payment method. An unpaid order, opening a payment page, or asking about renewal does not extend your rental. Unless you explicitly authorise automatic billing and the order shows that arrangement, do not assume your rental will renew automatically.
Before changing a machine, node, or add-on during your rental, submit a ticket to confirm what is possible, the cost, and how your data will be handled. Do not assume a change will be seamless or that the unused portion of your term will be credited towards a new order. When you're ready to rent, configure and rent a cloud Mac, then check the final order details again before paying.
4. Refunds and expiry
If there's a payment issue, duplicate charge, mismatch in the delivered configuration, or a service you can't use, sign in to the console and submit a ticket. Include your order number, payment status, when the issue occurred, and the steps you've already tried. We review refund requests against payment records, delivery and usage details, and any consumer rights that apply under the law. Submitting a request does not mean it has been approved.
Ending a task early, disconnecting, or deleting a local client does not cancel your order. Your assigned machine remains reserved for you during the active rental term. If you want to end your rental early, remove an add-on, or discuss unused time, get confirmation from support before taking action. Any approved refund, including its amount and status, will be documented in the ticket. The time it takes to arrive depends on the relevant payment provider.
When your rental expires without a completed renewal, access to the machine ends and the node enters the reclamation and secure disk-erasure process. Before expiry, export your source code, build artefacts, certificates, keys, and configuration, and verify that your backups can be restored. Do not rely on the machine or its data being retained or recoverable after expiry. A new rental does not guarantee the same machine, public IP address, or environment.
5. Acceptable use
You may run lawful development, compilation, automated testing, self-hosted runners, and MLX inference experiments. You are responsible for the programs you deploy, the data you upload, and the network requests you make, and must have the rights to use the relevant content. You must not scan, probe, stress-test, or otherwise interfere with a third-party system without permission.
You must not use the service for mining, spam, cyberattacks, malware distribution, credential theft, fraud, or infringement of another party's intellectual property. You must not bypass account verification, payment verification, or access controls; use a machine to relay unlawful traffic; or interfere with the operation of other nodes, the console, or network infrastructure.
If we suspect misuse, we will investigate based on the risk. To prevent ongoing security harm, we may first restrict relevant network access or suspend the affected service, then notify you using your account contact details. You can request a review by submitting an explanation and supporting evidence in a ticket. When investigating misuse, support staff should use only the information necessary to verify the issue and limit harm.
6. Software licences
When using macOS, Xcode, or other Apple software, you must comply with the applicable Apple software licence agreements and terms of use. Renting a machine does not grant you a sublicense to any software or change third-party licensing requirements for commercial use, user numbers, build distribution, or model use.
Software, dependencies, SDKs, model weights, and plugins that you install must come from trusted sources, and you are responsible for checking the scope of their licences. Obtain any required individual, team, or distribution licences before using the relevant tools. Do not bypass licence restrictions by modifying verification mechanisms or sharing unlicensed keys.
You are responsible for configuring project signing and app distribution and obtaining the necessary authorisations. Keep signing materials separate from ordinary build caches, and limit CI tasks' access to keychains and private keys. Support can help troubleshoot your environment and commands, but cannot obtain permission to use your projects, code, certificates, or distribution materials for you.
7. Uptime and credits
MergeMac commits to 99.9% monthly uptime. All nodes operate year-round, 365 days a year. Uptime applies to the availability of your rented node during your active term. It does not guarantee that every build task will succeed or that every location will have a fixed latency or throughput to a node.
We assess uptime using the affected order, actual service hours, node operating records, and incident records. A failed application build, an unreachable third-party dependency, or a problem with your network does not by itself mean a physical node was unavailable. Outages caused by your actions that damage system or network configuration, and outages caused by force majeure, are not eligible for credits under this commitment. We assess the cause using the available records.
If monthly uptime falls below 99.9%, we provide a renewal-time credit calculated in proportion to the period below the commitment. Submit a console ticket with the instance ID, outage start and recovery times, connection errors, and any relevant logs. We will review the affected period and explain the outcome in the ticket. Credits are applied as additional rental time; do not treat them as cash refunds or deduct them from an outstanding bill yourself.
8. Data and backups
Each node is reset before delivery, and you can also trigger a system reinstall from the console. Reinstallation erases the existing environment and data on the machine, so make an external backup before confirming. Secure disk erasure at the end of a rental is also irreversible; local backups cannot be used after the entire disk has been erased.
You are responsible for backing up and restoring your source code, databases, build artefacts, signing certificates, private keys, and configuration files. We recommend pushing code to a repository you control, encrypting and exporting irreplaceable materials to a location outside the machine, and regularly testing your recovery steps. For long-running runners, restrict access to working directories and avoid writing sensitive information to logs or unprotected caches.
MergeMac does not proactively read source code or files on rented machines. If you need help troubleshooting, share only the necessary, redacted logs and specify the scope of the investigation you authorise. See our Privacy Policy for how we handle account, order, console activity, and ticket information. Do not include complete passwords, private keys, or sensitive payment details in public issue descriptions or regular email messages.
9. Liability and disclaimers
We provide the physical node and related support specified in your confirmed order, and investigate and address service issues. You are responsible for project dependencies, app configuration, licences, access credentials, and data backups. Dedicated hardware isolates computing resources, but does not replace your own project access controls, security updates, or recovery plan.
Build times, test results, model throughput, and remote interaction depend on factors such as project size, tool versions, concurrent workloads, and network routes. Workflow descriptions on this site do not guarantee specific app performance, release dates, or business results. Allow time to validate and retry critical release tasks, and never rely on a single remote machine as your only copy of your data.
Any liability arising from a loss or service dispute will be determined based on the actual cause, each party's conduct, the applicable order, and verifiable records. Issues caused by force majeure or your own actions will be assessed according to their impact. Nothing in these terms excludes liability that we are required by law to accept. Uptime credits do not replace any other obligations that must be fulfilled by law.
10. Changes and disputes
We may update these terms when the service scope, payment process, or legal requirements change, and publish the current version on this page. If a change materially affects the rights or obligations under an existing order, we will notify you and provide details by account email or through the console. Updating this page alone will not retroactively increase charges for confirmed orders. Review the applicable terms before placing a new order or renewing.
If you have a question about billing, refunds, node delivery, credits, or data handling, first sign in to the console and submit a ticket. If you cannot log in, contact support@mergemac.com. Include your order number, what happened, and how you'd like the issue resolved. This helps us identify the relevant records and avoid repeating checks across multiple emails.
These terms are governed by the laws of the jurisdiction where the platform operator is based. The parties will first try to resolve disputes through written discussions. If they cannot reach an agreement, either party may bring the dispute before a court with jurisdiction in that jurisdiction. Any mandatory legal requirements that cannot be excluded will continue to apply.