1. Service description
XCRent provides dedicated physical Mac mini rentals for iOS and macOS builds, automated packaging, testing and other workloads permitted under these terms. The service provides an entire physical node, not a virtual machine. During the active rental period, each node is assigned to one tenant only. Renting a node does not transfer ownership or grant the right to use it beyond the rental period.
The catalog offers three configurations: XR Build 16 with M4 / 16GB / 256GB, XR Build 24 with M4 / 24GB / 512GB, and XR Build Pro 64 with M4 Pro / 64GB / 2TB. Nodes are available in Singapore, Tokyo, Seoul, Hong Kong, the US East and the US West. All three configurations are offered in these locations; check the console for real-time availability.
Once a node is assigned, tenants can retrieve connection details in the console and use SSH or remote desktop to access the macOS graphical interface and command line. Choose an Xcode version that meets your project requirements. The confirmed order record determines the actual configuration, location, add-ons, rental dates and delivery status. Build times depend on project size, dependency downloads, caching, concurrent workloads and network conditions. Workflow illustrations on the site are not guarantees of build times.
2. Accounts and responsibilities
Create an account using an email address you control, keep it available for order, account and service notifications, and provide accurate information where required. If renting on behalf of a team, the person placing the order must have authorization and establish who is responsible for order approval, payment, renewal and data on the node. Do not impersonate anyone or use another person’s account or payment details without authorization.
Protect account verification codes, passwords, SSH private keys, remote desktop credentials and access tokens used in build pipelines as sensitive information. When team membership changes or credentials may have been exposed, promptly replace the affected credentials, revoke unnecessary access and review jobs and permissions on the node. Never include complete private keys, payment card details or usable secrets in public repositories or support ticket messages.
Tenants are responsible for authorized actions taken through their accounts, including placing orders, changing configurations, reinstalling the system, deleting files and confirming renewals. If you notice a suspicious login, an unauthorized action or cannot access your account, submit a support ticket through the console; if you cannot log in, email support@xcoderent.com. We will verify your identity using account and order information before handling requests involving your account or node.
3. Billing and payment
Billing is available in daily, weekly, monthly and quarterly periods. All prices are in US dollars (USD). XR Build 16 is listed at $21.7/day, $58.5/week, $108.3/month and $294.6/quarter; XR Build 24 at $40.8/day, $110.2/week, $204.1/month and $555.2/quarter; and XR Build Pro 64 at $59.5/day, $160.5/week, $297.3/month and $808.7/quarter. Each billing period has its own listed price; longer periods are not calculated by simply adding shorter-period prices.
Add-ons are billed for the period selected in the order. An additional 1TB SSD costs $2.8/day, $7.7/week, $14.2/month or $38.6/quarter; an additional 2TB SSD costs $5.6/day, $15.4/week, $28.4/month or $77.2/quarter. Thunderbolt 5 daisy-chaining is charged per device at $1.8/day, $5/week, $9.2/month or $25/quarter. Before paying, check whether you selected add-ons, which nodes they apply to and the final amount due.
We accept USDT-TRC20 and Visa / Mastercard / Amex via Stripe only. Actual payment options depend on the gateways returned by the backend. For USDT-TRC20, check the network, receiving address and amount due shown by the gateway. For card payments, complete the verification on the payment page. Payment is complete only when confirmed in the order; a local screenshot, browser redirect or standalone proof of payment does not replace system confirmation. Node assignment and rental dates are determined by the order status in the console.
Before paying, confirm the configuration, location, billing period and add-ons. For duplicate or mistaken payments, an unexpected payment status or a disputed amount, request a review through a console support ticket and include the order number and relevant transaction details. Refunds or billing adjustments are handled based on the service delivered, actual usage, order records and applicable law. Submitting a request does not mean a refund has been issued; payment gateway processing times depend on the gateway.
4. Renewals, expiry and data handling
Check the rental end time in the console and renew before the rental expires. Starting a payment without a successful confirmation does not extend the rental. After renewal, check that the order and node show the updated expiry date; submit a support ticket promptly if they differ. Before upgrading or changing add-ons, confirm the new configuration, charges and whether data migration is involved. Do not assume a configuration change takes effect in place without further checks.
Once the rental period ends, continued access to the node is not covered by the original order. Source code, caches, signing materials, build artifacts and other tenant files on the node remain the tenant’s property. Before expiry, back up anything you need to retain to storage you control and verify that the backup can be read. At the end of the rental, the disk is erased. Data on the original node is not retained as a recoverable backup, so do not rely on exporting it after expiry.
Reinstalling the system, wiping the disk, deleting directories or moving workloads may alter or erase node data. Before proceeding, confirm the scope of the operation, save anything you need and stop build jobs that may continue writing to disk. Node rental does not include backup services for build caches or local disk. If you need help with data or an unexpected operation, provide the node, order and details of what happened. Do not paste sensitive files into support tickets.
5. Uptime commitment and service credits
We commit to 99.9% monthly uptime, with all nodes operating year-round, 365 days a year. Uptime is calculated for the node associated with each order: monthly uptime = (total time service should have been available during the measurement period − verified downtime) ÷ total time service should have been available × 100%. The measurement period covers only the portion of the calendar month when the order is active. Time before the order starts or after it expires is excluded from the denominator.
Downtime means a period when a platform-side node or service failure prevents the tenant from normally accessing and using the rented physical node. Downtime is determined from service records and investigation findings. Failed builds, certificate misconfiguration, inaccessible dependency sources, tenant-initiated shutdowns or reinstalls, and issues caused by the tenant’s own network or actions do not automatically count as platform-side downtime. The impact of events beyond reasonable control is assessed based on the circumstances and applicable law.
If monthly uptime falls below 99.9%, the shortfall is compensated with additional rental time. The calculation is: service credit time = verified downtime − (total time service should have been available during the measurement period × 0.1%). If the result is zero or less, no rental-time credit is due. Credits are applied as an extension to the rental period after verification; the same downtime is not counted more than once.
To request a review, submit a console support ticket with your order number, node, start and end times when access was unavailable, and the time zone used. Include redacted connection errors or task logs. We will review the records to determine the cause, duration and any applicable credit, and explain the outcome in the ticket. If you disagree with the result, you may provide further evidence for review. These credits do not limit any rights you have under applicable law.
6. Acceptable use
Use the node only for lawful workloads you are authorized to run. Do not use it to send spam or unsolicited bulk communications, carry out network attacks, distribute malware, steal credentials, bypass another party’s access controls, or scan or access systems without authorization. Security testing must be explicitly authorized and must not disrupt the platform network or other users’ services.
Do not store, process or distribute content that infringes another person’s intellectual property, privacy or other legal rights. Ensure you have the necessary rights to use source code, dependencies, models, media, signing materials and build artifacts. Do not resell account access, misrepresent your identity as the service, or interfere with node assignment, payment confirmation or service investigations.
If we suspect a violation of these rules, we may request an explanation, restrict the relevant activity or suspend the affected service. In cases of an ongoing attack, exposed credentials or an immediate risk to others, we may first take necessary steps to isolate the issue and then notify the tenant through an available contact channel. Tenants may submit proof of authorization or raise an objection through a support ticket. Any response will be based on the specific risk and evidence and will comply with applicable law.
7. Software licenses
Renting a physical node does not grant unrestricted rights to all software installed on it. You must comply with the Apple software license agreements and the license terms for any tools, dependencies, plugins, models and media you install. Use, deployment and version selection for macOS and Xcode must comply with the applicable licenses and your project requirements. Do not bypass software licensing or copy protection.
We provide macOS environments and Xcode toolchains. You are responsible for checking that the required SDKs, command-line tools, build scripts and dependency versions are available for your project. You must obtain and manage any licenses required for software or paid tools you install. Third-party software compatibility, license scope and results are governed by the relevant license terms and product requirements.
Certificates, private keys and provisioning profiles used for app signing must be provided by a team authorized to use them and managed according to the principle of least privilege. When importing these materials into Keychain or using them in CI, control access, keep them out of public logs, and revoke or remove them when no longer needed. Renting a node does not guarantee app review approval, release or access to third-party services.
8. Limitation of liability and disputes
We provide the physical node rental specified in the confirmed order and handle platform-side service failures and uptime credits under these terms. Tenants are responsible for their business code, job configuration, data backups and authorized actions. If an issue arises, both parties should preserve relevant records, stop actions that may increase the loss and share redacted evidence directly related to the issue through a support ticket.
Responsibility is determined based on the cause of the issue, each party’s actual conduct, order records, demonstrable losses and applicable law. Build failures, release delays, changes to third-party platform rules or data deleted by a tenant should not be attributed to the node service without investigation. Nothing in these terms limits liability that cannot be limited under applicable law or affects any remedies available to tenants by law.
These terms are governed by the laws of the jurisdiction where the platform operator is based. In the event of a dispute, the parties should first review the facts and try to resolve the matter through a console support ticket or support@xcoderent.com . If they cannot reach a resolution, the dispute will be submitted to a court with jurisdiction in that jurisdiction. Mandatory provisions of applicable law take precedence over any conflicting terms here.
9. Changes to these terms
We may update these terms to reflect changes to the service, billing arrangements, security requirements or applicable law. Updates and their effective dates will be posted on this page. We will notify tenants of changes that materially affect their rights or responsibilities through the console or their account email. Keep your contact details current and review the terms in effect before placing a new order, renewing or changing your configuration.
The specifications, charges and rental period for a confirmed order are set out in its order record. An update to these terms does not retroactively change confirmed transaction records. Whether a change applies to an existing order depends on the change notice, any express agreement between the parties and applicable law. If you have questions about a change, confirm its effect through a support ticket before placing a new order or renewing.
To ask about these terms, check an order or report a service issue, pleaselog in to the console and submit a support ticket. If you cannot log in or need clarification about these terms, email support@xcoderent.com. Include a brief summary of the issue and your order number. Do not send full connection credentials or private keys.