How to Order, Use, and Complete a Cloud Mac Rental

Acceptance and Eligibility

When a user creates an order, completes payment, receives connection credentials, or actually uses an ArmMacs service, they confirm that they have read, understood, and accepted these terms, along with the model, region, rental period, and pricing conditions shown on the order page. If ordering for a team, company, or other organization, the operator confirms they are authorized to accept these terms and manage the order on its behalf.

The purchaser must have the legal capacity to enter into an agreement and provide valid contact details for receiving order notifications and security information. Users must not create orders under a false identity, with an unauthorized payment method, or by circumventing access controls. If order information changes, update it promptly in the console or submit a console ticket describing what needs to be verified.

Service Definition

ArmMacs provides cloud Mac rental services on Mac mini Apple Silicon devices. Each fully allocated order corresponds to a dedicated physical machine and physical node, not a virtual machine. The macOS graphical interface and command line are available, allowing users to configure Xcode, build dependencies, runners, remote desktops, and experimental environments for their projects.

The exact chip, memory, storage, region, add-ons, rental start and end times, and order status are determined by the corresponding order record in the console. Available base models include Pulse M4, Vector M4, and Apex M4 Pro. Inventory is tracked separately by model and node, so availability of another configuration in the same region does not indicate that the target configuration is available.

Orders and Inventory

Creating an order only submits the target model, rental period, node, and add-on configuration; it does not mean that a physical node has been allocated. Actual inventory, payment status, node allocation progress, and delivery outcome are determined by the information returned in the console. Inventory for the target configuration may change during order confirmation, so users should review the order summary again before payment.

Once inventory is available and payment is confirmed, the system begins physical node allocation, credential generation, and connectivity checks. Delivery is complete when the console shows the resource as available and provides connection information. If an order remains pending, under review, or being allocated, retain the order number and relevant timestamps and submit a console ticket for assistance.

1. 1
   Submit Configuration

   Choose the model, node, rental period, storage, and parallel execution options.

2. 2
   Confirm Payment

   The order records the payment result and enters the resource allocation process.

3. 3
   Allocate Node

   The target physical node is configured and connectivity is checked.

4. 4
   Start Rental Period

   The start and end times and availability status shown in the order apply.

Pricing and Payments

All prices, add-ons, and orders are billed in USD. The only supported payment methods are USDT-TRC20 and Visa / Mastercard / Amex through Stripe. The available payment gateway is determined during checkout; verify the amount, network, recipient details, and order number before completing payment.

When paying with USDT-TRC20, use the network and amount specified in the order and retain verifiable transaction records. Card payments are processed by Stripe. If a submission is duplicated, the amount is incorrect, or the order status does not update, do not repeatedly create the same order. Submit a console ticket first with the order number, payment time, and redacted transaction details.

Rental Periods and Renewals

Services can be rented by the day, week, month, or quarter. The exact start time, end time, and current status of each order appear in the console. Use the order timestamps to schedule builds, backups, data export, and renewals. Period names on the page identify billing units and do not replace the specific start and end times shown in the order.

Renewals must be completed through the console before the current rental period ends and take effect only when the renewal order is recorded successfully. Submitting a renewal request, sending an email, or creating a ticket does not automatically extend the rental period. When renewing, verify the model, node, add-ons, period, amount due, and payment result.

After the rental period ends, node access changes according to the order workflow, and the resource may enter recovery and necessary cleanup. Before the end time, stop pipeline jobs, revoke temporary credentials, export code and build artifacts, and verify that exported copies work independently. An order without a completed renewal cannot rely on continued access to the original node.

Acceptable Use

Users may use cloud Macs for lawful software development, automated testing, CI/CD, remote development, model experimentation, graphics work, and other authorized engineering purposes. Users must ensure that their code, data, certificates, dependencies, software licenses, and network activity meet applicable requirements, while controlling resource usage and the scope of external connections.

The following activities are not acceptable use:

• Conducting unlawful activities or storing, processing, or distributing unlawful content.
• Accessing accounts, systems, networks, code repositories, or other nodes without authorization.
• Creating, deploying, or distributing malicious code, or using a node for network attacks, scanning, spoofing, or disruption.
• Infringing intellectual property, trade secrets, privacy rights, or other lawful rights and interests.
• Circumventing access controls, interfering with platform scheduling, or affecting the normal operation of other physical nodes or infrastructure.
• Deliberately concealing the source of an attack, tampering with audit information, or continuing to increase risk after receiving a security notice.

When high-risk activity is detected, the platform may restrict related access based on security records and order status and may require the user to cooperate with verification. Users must provide the necessary order number, node, time, and redacted logs so the scope of impact and next steps can be confirmed.

Account and Security Responsibilities

Users are responsible for protecting console credentials, node connection details, development certificates, private keys, access tokens, environment variables, and local remote-connection devices. Configure sensitive information with the least privileges necessary; do not place it in public code repositories, build logs, ordinary chat messages, or unprotected scripts.

After the first connection, users should verify the node identity, change initial security settings, restrict remote-access sources, and review existing processes and task configurations. For collaborative work, clearly define who may view orders, connect to nodes, modify pipelines, and perform data cleanup. Do not allow multiple people to share the same personal credentials indefinitely.

If you detect an unusual login, unknown process, leaked credential, certificate misuse, or unauthorized build task, immediately stop the relevant tasks, rotate affected keys, and submit a console ticket. Include the order number, model, node, discovery time, reproduction steps, and redacted logs. Do not submit passwords, private keys, or unredacted certificates.

Data Export and Termination

Users are responsible for managing the code, certificates, keys, models, datasets, caches, build logs, and build artifacts they bring to a cloud Mac, and must export them before the rental period ends. Data on a node must not be treated as the only copy; important projects should have verified external backups that can be restored.

After the rental period ends, the order is terminated, or access is restricted for security reasons, the node enters resource recovery and necessary cleanup according to the order and data policies. Use the end time shown in the console to reserve time for export and verification. Temporary access after the end time must not be treated as a promise to retain data.

Pre-Expiration Checklist

• Export code, models, data, and build artifacts, then verify file integrity.
• Stop runners, scheduled tasks, automated deployments, and background experiments.
• Revoke temporary tokens and rotate keys and certificates used on the node.
• Clean work directories, logs, caches, and configuration files containing sensitive information.
• Check the order end time and confirm whether the renewal order has been recorded successfully.

Service Scope and Responsibilities

ArmMacs is responsible for delivering the physical node with the specifications confirmed in the order, providing console status records, and handling tickets related to node allocation, connection credentials, and service-side incidents. All nodes operate continuously 365 days a year.

Remote use still depends on the user’s local network, cross-region links, code repositories, dependency sources, CI/CD platforms, and other third-party toolchains. Users are responsible for their local connectivity, software configuration, build scripts, licenses, certificate permissions, dependency versions, and project data. Incidents should be assigned based on where and when they occurred, network paths, node status, and build logs.

In cases involving force majeure, external network failures, user actions, unauthorized access, or user configuration changes, both parties should confirm the scope of impact using verifiable records. Users should first preserve relevant information and stop tasks that could increase the impact; the platform will use order records, node records, and ticket materials to investigate, control access, or restore service.

Changes and Contact

These terms are versioned by the effective date shown on the page. When updated, the current text will be published on this page; important changes to how existing orders are handled will be accompanied by relevant information based on order status. Continuing to create orders, make payments, or use the service after an update takes effect constitutes acceptance of the updated terms.

The formation, interpretation, performance, and dispute handling of these terms are governed by the laws of the jurisdiction where the platform operator is based. In a dispute, the parties should first communicate using the order, payment, node-status, and ticket records. Any unresolved dispute may be submitted to a court with jurisdiction in that jurisdiction.

For order or active-rental issues, log in to the console first and submit a ticket with the order number, node, timestamp, reproduction steps, and redacted logs. For general questions about these terms, email support@armmacs.com. Do not send passwords, private keys, or unredacted certificates by email or ticket.