1. Service scope
XcodeHost provides Mac mini Apple Silicon rental on dedicated physical machines. You can remotely access the macOS graphical interface and command line for development, compilation, testing and automated builds. This is not a virtual machine. During an active rental period, each machine is assigned to one user and its CPU and memory are not shared with other users.
The available configurations are XcodeHost M4 (M4 / 16GB / 256GB SSD) and the Pro tier (M4 Pro / 64GB / 2TB SSD). The configuration, node, billing period and add-ons selected in your order together define the service. Check the dashboard for real-time availability.
The rental provides a remote computing environment; it does not include project development, dependency compatibility fixes or any guarantee of app review outcomes. Before ordering, confirm that the available tool versions, build workflow and licensing terms meet your project’s needs. Access to a machine does not replace checking your project environment.
2. Billing periods
Service is prepaid by the day, week, month or quarter. All listed prices and payments are in US dollars (USD). Before placing an order, check the configuration, billing period, node, additional storage and Thunderbolt 5 parallel configuration. The amount due is the total shown in the order summary at checkout.
Daily, weekly, monthly and quarterly rates are priced independently. One period’s rate should not be used to calculate another period’s price. Add-ons are charged according to the selected billing period, so the base price for a configuration may not reflect the total order cost. The start and end times of a purchased service are recorded in the dashboard.
Before renewing, check the renewal period and new expiry time, then complete payment. The service stops at expiry if you do not renew; there is no long-term contract. If you have a question about a charge, first review the order details by submitting a support ticket through the dashboard. Payment does not mean a refund or change request has been approved.
3. Payment methods
We accept USDT-TRC20 and Visa / Mastercard / Amex credit cards processed by Stripe. All payments are settled in US dollars (USD). Available payment gateways are determined by the response from the backend; choose an available option at checkout.
For USDT-TRC20 payments, check the network, receiving address and amount due shown on the payment page before sending funds. Do not transfer funds over another network. If you have a payment verification issue, keep your order number, transaction hash and payment time, then submit them through a dashboard support ticket. Never share your private key or wallet recovery phrase.
Stripe processes credit card payment details, and this site does not store full card numbers. You must be authorised to make the payment. For a payment dispute, provide your order number, payment status and any necessary redacted evidence. Do not send full card numbers, security codes or verification codes by email or support ticket.
4. Provisioning and expiry
Service is provisioned for use on the day your order is activated. After your payment is confirmed, check the dashboard for the activation status and connection details. If you cannot access the connection details, or the configuration does not match your order, submit a support ticket with your order number so we can investigate. Do not pay for the same order again.
Your rental period is determined by the start and end times shown in the dashboard. If you do not renew before expiry, the machine will stop running and you will no longer be able to use the remote desktop, command-line connection or build tasks. An ongoing compilation, upload or automated task does not extend the rental period.
After shutdown, data enters the deletion process and is not a backup that can be restored on demand. Data cannot be recovered once deleted. Export your projects, build artefacts, certificates and any other files you need before expiry. Do not use an expired node as storage. If you need to confirm how data for an order is being handled, submit a support ticket for verification; do not assume that renewing will preserve existing data.
5. Uptime commitment
Nodes operate year-round, 365 days a year. We commit to monthly service availability of 99.9%. Over a 30-day period, 0.1% represents approximately 43 minutes of unavailability. This is a service commitment, not a historical uptime report.
For verified outages during an active rental period caused by the platform, any time exceeding the monthly allowance will be credited as service time based on the duration affected. We assess claims using the relevant order, platform operating records and the time period you submit. The same period will not be credited more than once.
To request a review, submit a support ticket through the dashboard with your order number, the start and end times of the outage, the time zone, and redacted connection errors or task records. Force majeure, system failures caused by your own actions, and issues with your local network or project dependencies are not counted as platform downtime. We will confirm the outcome in your support ticket.
6. Acceptable use
You may use a node only for lawful, authorised development, testing, builds and computing tasks. You must not send spam, mine cryptocurrency, distribute unlawful content or malware, gain unauthorised access, or use a node to infringe another person’s systems, privacy or intellectual property.
You must not provide the service to others for these activities or use a node to bypass access restrictions or conceal prohibited conduct. Configure credentials, task permissions and network access carefully for automated builds. Do not scan, attack or disrupt other systems.
If we identify activity that may put the platform or a third party at risk, we may take necessary steps, including restricting access, suspending the relevant service and reviewing the order. We will follow up through the account contact channel. You must cooperate by providing an explanation of your use and any information needed for the review. If you disagree with our decision, you may request a review through a dashboard support ticket.
7. Your responsibilities
You are responsible for ensuring that your developer credentials, signing certificates, provisioning profiles, code and dependencies are lawful and valid. You must have the permissions required to build, distribute and test the relevant apps. Renting a node does not grant additional software licences or guarantee that an app will pass review by a distribution platform.
Once you receive your connection details, keep your access credentials secure and change the initial password promptly. Configure SSH keys and access permissions as needed. Do not put connection passwords, certificate private keys or automation tokens in public code repositories. For team use, the order holder is responsible for authorising team members and their actions.
Back up your own projects and build artefacts. Before your rental ends, export any certificates you need, remove sensitive files from the machine and revoke access tokens you no longer use. When reporting a technical issue, provide only the redacted logs needed to investigate. Do not send full signing materials or customer source code as ordinary attachments.
8. Liability and changes to these terms
Each party is responsible for actions within its control. Platform outages are reviewed and handled under Section 5. Build failures, dependency conflicts and files deleted by mistake must be assessed based on their respective causes; using a cloud Mac does not automatically make an issue a platform outage. Nothing in these terms limits or excludes liability where applicable law does not allow it.
Changes to these terms will be published on this page. Any material changes affecting important rights under purchased services, including billing, expiry or credits, will be communicated through the dashboard or the email address associated with your account. Changes will not retroactively reduce benefits confirmed for an existing order. Review the applicable terms before renewing or placing a new order. If you have questions about a change, contact us by support ticket or email.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. If a dispute arises, the parties will first try to resolve it by support ticket or email. If they cannot reach an agreement, either party may submit the dispute to a court with jurisdiction in that jurisdiction. For questions about these terms, order disputes or compliance matters, contact support@xcodehost.com or sign in to the dashboard to submit a support ticket.