Review the rules before starting a continuously running cloud Mac

RunAMac provides dedicated physical Mac mini hosting. During the active term, the renter has exclusive use of the processor, memory, and local storage assigned to the order; the device is a physical node, not a virtual machine shared with other renters.

The service includes order confirmation, node assignment, system initialization, delivery of connection details, term records, billing records, and necessary service support. Users may use the macOS graphical interface or command line for lawful development, builds, testing, and experiments.

Device ownership does not transfer through rental. The user receives usage rights for the agreed term and may not sell, transfer, pledge, or bypass the portal to place order access under the control of an unauthorized party.

Users must have the legal capacity and authorization required to enter into and perform these terms. When ordering for a team or organization, the person submitting the order must confirm their authority to accept these terms and manage the related charges.

When registering, ordering, or submitting a support request, users must provide genuine, accurate information that can reliably receive notifications. Changes to the order number, contact details, node selection, or billing association must be updated in the portal or reported through a ticket without delay.

Users are responsible for protecting login credentials, connection credentials, keys, and session information and must not disclose them to unauthorized persons. Orders, configuration changes, renewals, tickets, and device actions initiated under an account are generally considered actions of the account holder or authorized members.

If you detect an unusual login, exposed credentials, or unauthorized device activity, immediately change the relevant credentials and use a portal ticket or support@runamac.com to provide the order number, time of occurrence, and verifiable details of the incident.

The only currently available configuration is RunAMac M4: Mac Mini M4, 16GB RAM, and 256GB SSD. Storage add-ons or Thunderbolt 5 daisy-chaining are included only when expressly listed in the order; other hardware, peripherals, and software capabilities are not part of the default delivery.

Available regions are limited to Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West. RunAMac M4 is available in all five nodes; live availability is determined by the portal.

• SingaporeSuitable for teams in Southeast Asia and regional collaboration tasks.
• Japan (Tokyo)Suitable for access paths in Japan and Northeast Asia.
• South Korea (Seoul)Suitable for remote development in South Korea and nearby regions.
• Hong KongSuitable for collaboration between South China and Southeast Asia.
• US WestSuitable for US West teams and trans-Pacific release tasks.

Once confirmed, the node becomes part of the order’s delivery terms. To request a regional change, submit a request in the portal first; eligibility, timing, and any required reinitialization are determined by the portal confirmation.

RunAMac M4 supports four fixed rental terms. Base host pricing is $19.6/day, $53/week, $98.1/month, and $266.8/quarter. The selected term begins when the order is confirmed and delivery is completed, as recorded in the portal.

Add-ons are charged separately for the same term: +1TB SSD costs $2.3/day, $6.2/week, $11.4/month, or $31/quarter; +2TB SSD costs $4.6/day, $12.4/week, $22.8/month, or $62/quarter; Thunderbolt 5 daisy-chaining costs $1.9/day, $5/week, $9.3/month, or $25.3/quarter per unit.

The order confirmation page lists the base host, term, node, add-ons, and total amount due in USD. Completing payment confirms the items shown there; this record is the primary basis for verifying fees, delivery contents, and the rental term.

Before confirmation, users should check the plan, region, term, and add-ons. New amounts resulting from a user-initiated configuration change are governed by the change confirmation page, not chat messages, estimates outside screenshots, or unsubmitted selections.

RunAMac accepts USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe. Available gateways are determined by the result returned in real time by the portal during payment.

All plans, add-ons, invoices, and order confirmation amounts are priced in USD. For USDT-TRC20 payments, users must verify the network, recipient details, and amount due shown in the portal; blockchain transfer fees are paid by the sender.

For card payments, Stripe processes the applicable payment information within its processing role. RunAMac does not store complete card details. Payment completion is determined jointly by the payment processor result and the order status shown in the portal.

If payment records and order status differ, retain the verifiable transaction ID, order number, amount, and time, then submit a portal ticket. Do not send full card details, private keys, or other confidential credentials in tickets, email, or screenshots.

1. 01
   Confirm order

   Verify RunAMac M4, the rental term, node, add-ons, and USD amount due.

2. 02
   Assign node

   Match a dedicated physical device to the confirmed region; the typical target time is about 1 minute.

3. 03
   Initialize system

   Initialize the device and complete delivery checks; the typical target time is about 1 minute.

4. 04
   Deliver connection details

   Add the required connection information to the portal; the typical target time is about 1 minute.

Order confirmation typically targets about 1 minute. Including node assignment, initialization, and connection-detail delivery, the normal process targets about 4 minutes in total. Actual completion depends on payment confirmation, profile completeness, and real-time portal processing.

The term begins when the portal marks the device as delivered and provides connection details. After delivery, users should verify the host identity, establish a session, and change initial credentials promptly. Report any mismatch in configuration, node, or connection details through a ticket as soon as possible.

Renewal does not occur automatically merely because the device remains in use. Before the current term ends, users must review the renewal term, configuration, and amount due and complete the confirmation and payment required by the portal. After successful renewal, the new term appears in the order details.

When the term ends without renewal confirmation, RunAMac may stop access to the device assigned to the order and begin expiration processing. Users should move code, certificates, build artifacts, and other data they need to retain before the term ends.

Typical permitted uses include automated iOS builds, macOS software development, continuous integration, small-scale AI experiments, script debugging, testing, build-artifact archiving, and authorized remote collaboration.

Users must ensure that code, dependencies, data, certificates, automation scripts, and network access have lawful sources and the necessary authorization, and must follow rules applicable to their business and content.

• Do not infringe third-party rightsThis includes unauthorized access to, copying, distribution, or processing of another party’s code, data, content, or credentials.
• Do not disrupt the serviceDo not conduct malicious scanning, attacks, resource abuse, or activity that affects the normal operation of other nodes or networks.
• Do not bypass security controlsDo not circumvent access restrictions, authentication, billing controls, logging mechanisms, or node isolation measures.
• Do not conceal unlawful activityDo not use the device for fraud, malware distribution, unlawful data processing, or other activities prohibited by applicable rules.
• Do not resell unauthorized accessWithout written confirmation from RunAMac, do not split device connectivity and provide it to unspecified third parties.

If suspected risky activity is detected, RunAMac may request additional details about the use case, restrict relevant sessions, or take necessary security measures. Users must cooperate by providing the order number, task context, and verifiable technical information.

Users are responsible for managing code, dependency caches, keys, certificates, configuration files, test data, model files, logs, and build artifacts on the device. For team handoffs, define member permissions clearly and promptly revoke access that is no longer needed.

Users should maintain independent backups according to task importance, keeping verifiable copies of source code, signing materials, critical configuration, and irreplaceable artifacts at minimum. Keeping the only copy locally on the rental device is not a reasonable data-protection arrangement.

Before submitting a support request, remove passwords, tokens, private keys, complete payment details, and other confidential credentials from logs, command output, and screenshots. When access troubleshooting requires evidence, provide only the minimum relevant, revocable information.

Before a term expires, an order ends, the device is reinitialized, or the user clears the environment, the user must migrate necessary data. RunAMac is not responsible for deciding which files should be retained, restoring unbacked-up content, or rebuilding an undocumented development environment.

All nodes are designed to operate normally 365 days a year. Users may continuously run development, build, testing, and experimental tasks that comply with these terms during the active term.

Actual connection quality may still be affected by the user’s local link, cross-region networks, carrier routing, code repositories, dependency sources, payment processing, software defects, and other third-party service conditions. Choose a node based on team location, interaction frequency, and where build artifacts will be delivered.

When a connection issue occurs, first save the timestamp, node, error output, reproduction steps, and local network test results, then submit a portal ticket. RunAMac will investigate using available logs and device status and take recovery or alternative measures within a reasonable scope.

To the extent permitted by applicable law, RunAMac is not liable beyond legally mandatory requirements for indirect losses, loss of anticipated profits, loss of business opportunities, or losses directly caused by the user’s configuration, credential management, scripts, data, third-party dependencies, or events beyond reasonable control.

Any liability assessment must consider the confirmed order, amount actually paid, cause of the event, whether the user provided timely notice, and verifiable records held by both parties. These terms do not exclude or limit liability that cannot be excluded or limited under applicable law.

RunAMac may update these terms based on the service catalog, security requirements, payment processing, or legal obligations. Material changes will be announced through the website, portal, or contact information provided by the user and will include a new effective date.

Updated terms apply to orders and renewals newly confirmed after their effective date. For a fixed term already in progress, if an update materially changes the confirmed configuration, term, or amount, the order confirmation and any subsequent express agreement between the parties control.

If a user breaches these terms, threatens service security, infringes third-party rights, or refuses necessary verification, RunAMac may require remediation, restrict relevant access, or terminate the service according to the risk. Any action will consider the urgency, available evidence, and applicable legal requirements.

Users wishing to end future use should stop initiating renewals and migrate necessary data before the term ends. Handling of a confirmed order is governed by its status, payment records, actual delivery, and mandatory requirements of applicable law.

If you dispute configuration, billing, delivery, or use restrictions, first use a portal ticket or support@runamac.com to provide the order number, relevant amount, timestamp, issue description, and verifiable supporting material. Both parties should first try to resolve the matter based on the records.

These terms are governed by the laws of the jurisdiction where the platform operator is based. Disputes that cannot be resolved through negotiation must be submitted to a court with jurisdiction in that jurisdiction, unless mandatory rules of applicable law provide otherwise.