1. Service and Eligibility
“Cloud Mac” means an Apple Silicon physical node provided by ArmMesh with remote access. Each valid order includes the dedicated physical resources listed on its confirmation page. The processor, memory and primary storage are not shared with other customers; the service is not virtualized.
A “physical node” includes the specified model, fixed hardware resources, installed macOS environment, network connectivity and remote management capabilities. You receive the right to use the node for the agreed rental period, not ownership of the device. You may not request its transfer, removal or disposal.
You must have the legal capacity to enter into and perform these terms, and provide account and order information that is verifiable, accurate and kept up to date. If you order on behalf of an organization, you confirm that you are authorized to bind it to these terms.
Accounts are for authorized users and their team members only. You may not sell an account, rent out access credentials, circumvent identity or security checks, or use multiple accounts to bypass service limits or outstanding payments.
2. Orders and Delivery
The order confirmation page lists the selected model, node region, rental period, base storage, storage add-ons and any Thunderbolt 5 clustering requirements. Check all configurations before paying. After payment, the scope of delivery is determined by the confirmation saved in the order system.
Available configurations include the M4 with 16GB memory and 256GB storage, and the M4 Pro with 64GB memory and 2TB storage. Both models can be ordered in Singapore, Tokyo, Seoul, Hong Kong, the eastern United States and the western United States. Check the console for current availability.
Once an order is confirmed, the system assigns a physical node, checks the system and generates connection details. Delivery is complete when the console shows the node as available and provides connection information. Delays caused by incomplete information, unfinished security checks or unconfirmed payment do not count as completed delivery.
Manage orders and nodes, renew rentals, view invoices and contact support through the console. Connection details are sensitive information; share them only with authorized team members who need access for their work.
3. Pricing and Billing
All prices are charged and settled in US dollars (USD). The amount due for each model, rental period and add-on is shown on the order confirmation page. Once you confirm an order, the confirmed amount applies for that rental period.
Base models are priced by the day, week, month or quarter. Published prices are shown below. Each rental period has its own listed price; prices are not calculated by simple multiples and do not automatically carry over to another period.
| Model | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| ArmMesh M4 | $19.5 | $52.7 | $97.5 | $265.2 |
| ArmMesh M4 Pro | $61.3 | $165.5 | $306.4 | $833.4 |
Add-ons are charged separately for the selected rental period and included in the order total along with the base model. An add-on applies only when it is listed on the order confirmation page.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.4 | $6.4 | $11.9 | $32.4 |
| +2TB SSD | $4.8 | $12.8 | $23.8 | $64.8 |
| Thunderbolt 5 clustering (per device) | $1.2 | $3.2 | $5.9 | $16 |
Any taxes, payment processing fees or on-chain transfer costs required by law or the payment provider’s rules will be shown before payment or listed separately by the relevant payment provider. Check the currency, amount, recipient details and order number before paying.
4. Payment Methods
ArmMesh accepts USDT-TRC20 and Visa, Mastercard or Amex (via Stripe). All orders are settled in US dollars (USD). Available payment gateways are shown in real time by the order system.
For digital asset payments, use the network, address and amount shown on the order page. Choosing the wrong network, entering the wrong address, underpaying or paying twice may prevent automatic order matching. Submit the transaction ID and order number in a console support ticket so we can investigate.
Card authorization, verification and payment results are provided by the relevant payment flow. Payment is complete only when the order system shows “Paid.” A charge notification, authorization hold or screenshot from your side does not replace the order system’s final record.
If a payment needs manual review, keep your order number, payment time, amount and verifiable transaction details. ArmMesh will never ask you to submit your full card number, security code or account credentials in a support ticket.
5. Renewal, Expiry and Resource Release
Confirm renewals in the console before your current rental period ends. The renewal order’s model, region, period, add-ons and payment status determine whether the renewal is complete. Creating a renewal request, submitting a support ticket or discussing renewal verbally does not complete it.
The system may send an expiry reminder as your rental period nears its end, but you are responsible for tracking your order’s expiry date. If you do not confirm a renewal, access stops when the order expires, associated credentials become invalid and the node enters the resource release process.
Before your rental period ends, migrate and back up project files, build artifacts, models, keys, signing certificates and business logs. Once node access ends, ArmMesh does not guarantee that you will still be able to access the system to export data or that unmigrated content can be recovered.
After resources are released, the device goes through secure cleanup and reconfiguration. Order, payment and necessary security records are retained as needed for service delivery, auditing and compliance. Work data managed by you on the node is not retained as long-term storage.
6. Acceptable Use
You may not use the service for activities that violate applicable laws, regulatory requirements or orders from competent authorities. You may not store, process or distribute content you know to be unlawful, or help others use a node for unlawful activity.
Unauthorized access to, scanning of, probing of or interference with any account, system, network or data is prohibited. You may not distribute malware, launch denial-of-service attacks, bypass access controls, impersonate others or use a node to access data that does not belong to you.
You may not abuse processor, memory, storage, network or remote management resources through sustained abnormal traffic, destructive workloads, cryptocurrency mining, malicious automation or other means. Standard development builds, automated testing, media processing and MLX inference are not inherently abusive just because they use substantial resources, but must stay within your ordered resources and lawful purposes.
You must respect third-party copyrights, trademarks, trade secrets, privacy and other legal rights. If ArmMesh receives a reasonably substantiated report of infringement or abuse, we may ask you to respond, stop the relevant activity or remove the content in question.
7. Your Security Responsibilities
You are responsible for protecting your account, email, verification codes, access keys, remote connection credentials and host fingerprint records. Update initial credentials promptly after your first connection, prefer key-based authentication and grant access according to the principle of least privilege.
You are responsible for managing signing certificates, project keys, source code repository credentials, model access tokens and other business secrets. Do not expose sensitive information in public repositories, unredacted logs, shared documents or uncontrolled automation scripts.
Keep an accurate list of team members, promptly remove anyone who has left the team or no longer needs access, and properly end remote sessions. Account holders are responsible for actions taken through shared accounts. For traceable work, we recommend separate system users, keys and log scopes.
Set up a backup strategy suited to your workloads, and verify that you can restore your data before upgrading toolchains, changing system permissions, deleting caches or migrating data. ArmMesh provides compute nodes, not a replacement for code repositories, artifact registries or dedicated backup systems.
8. Service Continuity, Emergency Response and Changes
All available nodes are designed to run year-round, 365 days a year. Service may be affected by events beyond our control, upstream network outages, sudden hardware failures, security incidents or your own actions.
If hardware issues, security risks or faults that could escalate occur, ArmMesh may isolate a node, limit traffic, reset credentials, inspect equipment or replace hardware. During response, we prioritize the security of the node, customer data boundaries and other systems, and share available status updates through the console.
If a device needs replacing, ArmMesh will provide equivalent resources based on your order configuration or confirm an acceptable alternative with you. If the region, network route or remote connection details change, check the new address, host fingerprint and access permissions against the notice you receive.
ArmMesh may change service features to address security, legal requirements, infrastructure capabilities or product improvements, but will not switch a valid order to a model outside the catalog without your confirmation. We will notify you through the console, your account email or an updated version of these terms of any change that materially affects your rights or continued use.
9. Liability and Indemnity
To the extent permitted by applicable law, ArmMesh is not liable for indirect or incidental losses, lost anticipated profits, loss of goodwill or business opportunities, or losses caused by your failure to back up or migrate data in time.
The party responsible bears responsibility for interruptions, failures or data changes caused by your configuration errors, scripts, access permissions, key management, third-party software, code repositories, artifact storage, network providers or other services outside ArmMesh’s control.
If ArmMesh is legally liable for a specific event, its liability will be based on the valid order directly involved and the proven direct losses, subject to any limits permitted by applicable law. This section does not exclude or limit liability where exclusion or limitation is prohibited by law.
If ArmMesh incurs a claim, investigation, reasonable expense or loss because you breached these terms, infringed a third party’s rights, engaged in unlawful activity or failed to secure your account, you must provide appropriate compensation and assistance to the extent permitted by applicable law.
10. Suspension, Termination, Updates and Disputes
ArmMesh may suspend access to an account, order or node if payment is incomplete, an account is at security risk, acceptable use rules are clearly breached, a competent authority requires it, or ongoing harm to systems or other users is possible. Where the risk allows, we will explain the reason and available next steps through the console or your account email.
ArmMesh may terminate the service if you seriously or repeatedly breach these terms, refuse to stop unlawful activity, provide false identity or transaction information, bypass security controls, or fail to remedy a breach within a reasonable time. Termination does not affect payment obligations or liability incurred before termination, or any terms that by their nature continue to apply.
These terms may be updated in response to changes in service capabilities, legal requirements or risk controls. Updated versions will show their effective date. We will notify you through the console or your account email of any update that materially affects your rights or obligations. Continued use of the service after an update means you accept the terms then in effect.
These terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first seek to resolve disputes through written communication. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction. For questions about these terms, email support@armmesh.comor sign in to the console and submit a support ticket.