1. Service scope
XcodeNet provides cloud Macs on dedicated physical machines, not virtual machines. During your rental, the CPU, GPU, and unified memory of your assigned node are not shared with other customers. You can use the macOS graphical interface and command line for development, builds, and testing. The confirmed order determines the hardware, storage expansions, and service period.
Two configurations are available: XN Core M4 with an M4 chip, 16GB of unified memory, and a 256GB SSD; and XN Pro M4P with an M4 Pro chip, 64GB of unified memory, and a 2TB SSD. The service covers 6 node regions: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the US East, and the US West. Both configurations are available across these regions. Check the console for real-time availability.
Nodes provide remote computing environments; they do not replace your project management, code review, or acceptance testing. The estimate of around 4 minutes to connect is a guide to the usual provisioning process, not a guaranteed completion time for every order. Payment confirmation, node assignment, and your network connection can all affect the time it takes to connect for the first time.
2. Accounts and orders
When you register, use an email address that you control and can access to receive verification codes and service notifications, and provide accurate account details. If you place an order on behalf of a team or another entity, you must have the necessary authority to do so. Keep your sign-in codes, password, and instance credentials secure, and do not share them with unauthorised people. If you notice suspicious sign-in activity or exposed credentials, update them promptly and report the issue through a console support ticket.
Place and confirm orders through the console. Before paying, check the model, node region, rental period, add-ons, and total in USD. Email enquiries, verbal discussions, and examples on this page do not constitute a confirmed order. Payment status, service activation, and the start and end of your rental are determined by the payment and order records in the console.
After payment, check the order details for the result rather than relying solely on a redirect from the payment page. If you have been charged but the order status has not updated, keep your order number and payment receipt, then sign in to the console and submit a support ticket. Do not pay repeatedly for the same issue. To place your first order, use the cloud Mac order page. For help with an existing order, check it in the console.
3. Billing and payment
Services are prepaid by the day, week, month, or quarter. Hourly billing is not available. Your order total depends on the model, rental period, and any add-ons; package pricing is not simply the daily rate multiplied by the number of days. The listed prices for XN Core M4 are $21.4/day, $57.7/week, $106.8/month, and $290.5/quarter. For XN Pro M4P, they are $59.3/day, $160.1/week, $296.4/month, and $806.2/quarter. Check the itemised total on the order confirmation page before paying.
All payments are charged in US dollars (USD). We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment options available for your order are determined by the payment gateway response. If you pay with USDT-TRC20, follow the network, recipient, and amount shown on the payment page; confirmation time depends on blockchain processing. For card payments, the gateway response and console records determine whether payment is complete.
Additional SSD storage is an external storage expansion and does not change the standard internal storage of your selected model. Thunderbolt 5 daisy-chaining is charged according to the number of units selected and the rental period. Only add-ons listed in the order details and confirmed by you are included in your purchase. Keep your invoices and transaction records. If you have a question about an amount, payment status, or duplicate charge, request a review through a console support ticket. Do not send your full card number or security code by email.
4. Renewals, upgrades, and refunds
If you want to keep using the service, check your renewal order in the console before your rental expires. Confirm the coverage period, configuration, and amount before paying. Renewals with the same configuration use the original order price. If you change the model, add-ons, or other settings, review and confirm the updated order details first. Service notifications do not replace your responsibility to track the expiry date, and submitting a renewal request does not mean the renewal has been paid for.
Mid-term upgrades are calculated based on the remaining rental period. Confirm the available options and any additional amount in the console or through a support ticket before proceeding. A change request does not mean that migration is complete, and changing a model or node does not automatically copy your files, environment, or network settings. Back up your data before making changes, and check the credentials, paths, and development environment on the new instance.
Refund requests are assessed against the details of the order. If you were charged more than once, service was not delivered after payment, or the delivered configuration differs from what you confirmed, provide your order number, payment record, and a description of the issue. Whether a refund is due, the amount, and how it is handled depend on the delivery status, the refund terms confirmed in your order, and applicable law. Do not assume that used time, cancelling an add-on separately, or ending a rental early at your request automatically qualifies for a full refund. This page does not promise a universal unconditional refund period or a fixed pro-rata rate.
Before ordering, check the order or console for specific details on how long data is retained and when it is deleted after your rental ends. If no such details are shown, confirm them through a support ticket rather than assuming there is a default retention period. Export your data before expiry. A refund, upgrade, or migration request does not automatically extend your rental or replace the need to back up your data.
5. Acceptable use
You must use the node and network only with proper legal authorisation. You must not send unsolicited bulk email, carry out network attacks, scan or access systems without permission, steal credentials, distribute malware, mine cryptocurrency, or create, store, or distribute unlawful content. You must not use the service to bypass access controls, infringe intellectual property rights, or disrupt other users or the network.
Security testing is permitted only on assets you own or are explicitly authorised to test, and you must keep the scope and traffic under control. Self-hosted build jobs, automation scripts, and file distribution must also use appropriate permissions. Keep secrets out of logs and build artefacts. Having a dedicated physical node does not entitle you to use the network without limits or engage in unauthorised activity.
If we identify suspected misuse or an immediate security risk, we may take necessary steps based on the risk, such as restricting access, suspending the affected service, or requesting further information. Where permitted by law and where doing so would not increase the risk, we will notify you. To request service restoration, explain the purpose, scope of authorisation, and corrective steps in a console support ticket. Any decision to terminate an order and handle subsequent charges will depend on the findings and applicable law.
6. Software licences
Renting a node gives you the right to use the agreed computing environment for the rental period. It does not grant any additional licence to Apple software or software from other third parties. Before installing, running, or distributing software, check that its terms allow your use case, remote access method, team usage, and commercial use, and obtain any required licences.
When using Xcode, command-line tools, Homebrew, Fastlane, model weights, or audio and video software, you must still comply with the relevant licence and distribution terms. Check the instance to confirm whether software is preinstalled, whether you can switch versions, and whether a particular plugin will run. Providing a macOS environment does not guarantee that every third-party app, driver, or workflow will work out of the box.
You are responsible for managing repository credentials, signing certificates, deployment keys, and third-party service tokens. For shared team build jobs, define who has access and what permissions they have. Do not place sensitive files in public directories or build logs. Before your rental ends, revoke tokens you no longer need, remove certificates and credentials, and confirm in your own systems that access has been disabled.
7. Availability and support
All nodes are provided for normal operation throughout the year, 365 days a year. Remote access still depends on your local network, client settings, access rules, and node status. Changes you make to the system, firewall, or connection settings may also temporarily prevent access to your instance. Normal operations do not amount to a performance guarantee for every network route, third-party service, or build result.
If you experience a connection interruption, instance issue, or delivery problem, sign in to the console and submit a support ticket. Include your order number, node region, model, when the issue occurred and the time zone, any error messages, and the troubleshooting steps you have already tried. Do not include your full password, private keys, or verification codes in public posts or emails. We will investigate based on the issue and provide updates and any steps we need you to take through the ticket or your account email.
If an issue involves force majeure, your own actions, or a third-party network, the impact and responsibility will be assessed based on the circumstances. If you need us to access or operate your instance, specify the scope of your authorisation in the support ticket. Requests for service remedies or billing adjustments will be assessed based on the findings, the confirmed order terms, and applicable law. This page does not promise a fixed repair time or compensation multiplier.
8. Liability and data backups
You are responsible for backing up important code, build artefacts, project files, certificates, and configuration. We recommend syncing important changes to storage you control and verifying that your backups can be restored. Neither the instance's internal drive nor an external expansion drive should be the only copy of important data. More storage does not include backup, snapshot, or disaster recovery services.
Before reinstalling the system, changing models, migrating nodes, or ending your rental, check the impact of the action and export your data. Do not assume your instance data will be kept just because the console is accessible, a support ticket is being handled, or a renewal request has been submitted. Whether data can be recovered after deletion depends on its actual status; do not assume we can retrieve files that have been deleted.
You are responsible for the legality of uploaded content, your software configuration and authorised use, and your own actions. We are responsible for our service delivery and handling as required by applicable law. The scope of liability depends on the cause of the issue, its actual impact, each party's contribution, and the order terms. Nothing in this section limits liability that cannot be excluded or restricted under applicable law, or releases us from any responsibility imposed on us by law because you are responsible for backups.
9. Changes and disputes
When these terms are updated, we will update the version and effective date on this page. We will notify you through the console or your account email of changes that materially affect your use of the service or existing rights. How a new version applies to existing orders is subject to the confirmed order terms and applicable law. Keep your email address able to receive notifications, and read the terms in effect before placing a new order or confirming a configuration change.
If you disagree with how these terms are interpreted, the delivery outcome, or a bill, first submit a support ticket through the console. Include your order number, what happened, relevant evidence, and the outcome you are seeking. If you cannot sign in, email support@xcodenet.com. Use this address for business, compliance, and security enquiries as well; no other public contact channel is provided.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. The parties will first try to resolve disputes through the channels above. If they cannot reach an agreement, the dispute will be submitted to a court of competent jurisdiction in that jurisdiction. Any mandatory provisions of applicable law that cannot be excluded will continue to apply.