1. Service
GNUMac provides Mac mini rental and hosting services. Each order covers one dedicated physical machine, not a virtual machine. During the rental period, its CPU, memory and system drive are not shared with other customers. You connect remotely to use macOS through its graphical interface or command line; you do not need to receive or store a physical device.
The available models are GNU Core M4 (M4 · 16GB RAM · 256GB SSD) and GNU Studio M4 (M4 · 24GB RAM · 512GB SSD). The service offers four APAC locations: Singapore, Tokyo, Seoul and Hong Kong. Your confirmed order determines the model, location, rental period and add-ons. Current availability is shown in the console.
Access credentials are provided through the console. Once you receive them, check your order configuration, connection method and instance status. If anything does not match, submit a support ticket with your order number. The rental period begins and ends according to the order record; your first connection or first completed build does not change those times.
You may use the service for lawful purposes such as builds, testing, CI, inference experiments and remote work. You are responsible for obtaining software licences, project signing materials, third-party service permissions and any requirements for connecting external devices. A dedicated machine does not guarantee compatibility with all software, access to every peripheral or a fixed build time. Test critical workloads before relying on them at scale.
2. Accounts and credentials
Provide an account email address that can receive notifications, make sure you are authorised to place orders for yourself or your team, and keep your billing and contact details accurate. Your email account is an important access credential because it receives verification codes, order updates and support messages. Protect it and its recovery methods.
Store your machine password, SSH private key and console login details securely and separately. Never expose credentials in public repositories, chat logs, build logs or screenshots. For team access, define who is authorised and what permissions they have. When someone leaves the team, promptly change passwords, revoke keys and remove access settings from automation tasks.
If you notice an unusual login, leaked credentials or an unauthorised order action, stop the relevant automation promptly and contact us through a console support ticket or at support@gnumac.com. To verify account ownership, we may ask for relevant order records. We will never ask you to send a plain-text password, a complete private key or full payment card details.
You are responsible for managing your own actions and those of anyone you authorise to use your account or machine. Do not resell access credentials, give unknown third parties access to the machine or bypass platform access controls. After reasonably verifying a risk, we may restrict the relevant access and notify you through your account about the action taken and any information needed to appeal.
3. Billing and payments
Choose from four billing periods: daily, weekly, monthly or quarterly. All charges are in US dollars (USD). The listed prices for GNU Core M4 are $21.3/day, $57.5/week, $106.4/month and $289.4/quarter. GNU Studio M4 is listed at $40.6/day, $109.7/week, $203.2/month and $552.7/quarter. Before ordering, check the billing period, start and end times, and total due. Different billing periods are not simply equivalent to the same number of days.
Add-ons are billed separately: +1TB SSD costs $2.7/day, $7.2/week, $13.3/month or $36.2/quarter; +2TB SSD costs $5.4/day, $14.4/week, $26.6/month or $72.4/quarter. Thunderbolt 5 daisy chaining is billed per machine at $1.3/day, $3.4/week, $6.3/month or $17.1/quarter. Check the quantity of each add-on and its billing period before confirming your order.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways are determined by the response from our backend. For USDT-TRC20 payments, check the network, address, amount and status shown on the payment page. On-chain transfers cannot be reversed by the platform once submitted. Card details are processed by Stripe; GNUMac does not store full card numbers.
Submitting a payment does not mean the order has been confirmed as paid. The console is the source of record for payment and order status. If a charge succeeds but your order status has not updated, submit a billing support ticket with your order number and any necessary transaction reference before trying to pay again. Amounts related to cancellations, duplicate payments or delivery disputes are reviewed against actual payment, delivery and usage records; refunds are not automatically calculated from unused time.
4. Renewals, expiry and offboarding
Before continuing to use a machine, check its expiry date in the console, complete the renewal payment and confirm that the order reflects the new rental period. Starting a payment, receiving a payment email or still being able to connect to the machine does not mean the renewal is complete. Renewal options and available billing periods are shown on the relevant order page.
Expiry reminders are intended to help you plan; you remain responsible for managing your rental period. Email filters, delayed notifications or unread messages do not extend an order. We do not offer a standard free grace period. If a specific order explicitly includes a grace period, only the conditions and deadline recorded for that order apply.
If your rental expires without a completed renewal, or you request offboarding and it is confirmed, access to the machine may be stopped and the machine will then be processed for return. This includes erasing the system drive and any rented additional SSD, followed by a reinstall and initialisation. User files cannot be recovered after the return process. Export your code, build artefacts, models, keys and any logs you need before the rental period ends.
Before changing your plan, adding storage or changing location, check with us through the console about the available process, charges and delivery arrangements. Do not assume a running instance can be migrated without interruption. Back up your data and test your migration before making changes. Until a change is confirmed, the original order period and responsibilities remain in effect.
5. Acceptable use
You may use the service only for lawful activities you are authorised to carry out. Do not use the machine to send spam or fraudulent messages, distribute malware, launch network attacks, steal credentials, bypass access controls, or scan, attack or stress-test targets without authorisation.
Do not store or distribute infringing or otherwise illegal content, or use another person's code, models, materials, certificates or personal information without permission. When using development tools, commercial software or third-party APIs, check their licence terms, access permissions and data-processing requirements. You are responsible for the content you put on the machine.
Do not disrupt platform infrastructure, other users or external networks, or attempt to access devices or management interfaces outside your rental. A dedicated physical machine lets you manage your own workloads, but does not give you the right to damage equipment, tamper with billing, bypass security controls or use resources you have not purchased.
If we identify a clear violation or an urgent security risk, we may take necessary steps such as restricting connections, suspending affected tasks or stopping the service. We may retain order and security records related to the incident. You can submit proof of authorisation and an explanation through a console support ticket. We will review the matter against the available facts and limit any action to what is reasonably needed to protect the service and third parties.
6. Availability and incident notifications
All locations operate year-round, 365 days a year. We manage the operation of the physical equipment and platform services we provide, and investigate, restore and, where necessary, service equipment when an incident occurs. This does not guarantee uninterrupted service across every network path on the user's side.
Remote connection quality also depends on your local network, carrier routing, client settings and workload. Build times depend on project size, dependency downloads, cache hits and concurrent tasks. Test the connection from your actual location and allow reasonable delivery time for critical builds.
If you cannot connect, notice an equipment issue or find a configuration mismatch, submit a console support ticket with your order number, location, the time it occurred, the error message and the steps you have already tried. Do not include passwords or private keys in a ticket. We will use the ticket or an account notification to explain the confirmed impact, progress and any action we need you to take.
Responsibility for force majeure events, your own actions and issues with your local network will be determined by the actual cause and what each party could control. If an order includes a specific availability commitment or compensation arrangement, that order's terms apply. This section does not create an availability percentage, recovery time or compensation multiplier that has not been agreed.
7. Liability and risk allocation
GNUMac will provide the service specified in your confirmed order and is responsible for its obligations relating to equipment operation, access delivery and data erasure when a machine is returned. You are responsible for configuring your working environment appropriately, protecting access credentials, confirming software licences, and validating system changes, file deletions and automation tasks you carry out.
Renting a machine does not include a backup service. Keep important data in a separate location under your control and test your recovery process. Before a reinstall, offboarding or system change, export your project files, signing materials and build artefacts. Do not treat a single instance as your only copy.
If a service dispute arises, both parties should first verify the order, payment, delivery and incident records, then address it based on the actual cause, demonstrable losses and each party's responsibility. Project timelines, expected revenue and third-party outcomes are not guaranteed by the platform simply because you use this service. You should have an alternative way to carry out critical work.
Nothing in this section excludes or limits liability that applicable law does not allow to be excluded or limited, or affects any mandatory rights you may have under applicable law. If the parties disagree about liability, the amount involved or an appropriate remedy, they may preserve relevant evidence and follow the process in Section 8. The platform will verify the facts rather than rely on a unilateral interpretation.
8. Changes and disputes
These terms apply to the rental services provided through the GNUMac website and console. We may update them to reflect changes to service processes, payment arrangements or applicable requirements, and publish the updated version on this page. We will explain the scope of any material changes to the rights or responsibilities under existing orders through an account notification or support ticket. We will not assume that a completed transaction is subject to additional charges retroactively.
Read the terms and order details displayed at the time before placing a new order or renewing. If you do not agree to updated terms, contact us before placing a new order or renewing, and arrange to export your data and plan your continued use during the current rental period. See our Privacy Policy for information about how we handle personal data.
For questions about the service, billing or these terms, sign in to the console to submit a support ticket, or email us at support@gnumac.com. Include your order number, what happened, any relevant transaction reference and how you would like the matter handled so both parties can work from the same records.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. The parties should first try to resolve disputes through good-faith discussions. If they cannot reach a resolution, either party may submit the dispute to a court with jurisdiction in that jurisdiction. Any mandatory requirements under applicable law will prevail.