1. Service
OSXBuild offers dedicated cloud Macs for daily, weekly, monthly, or quarterly rental. You receive an entire physical node, not a virtual machine; throughout your rental period, its CPU, memory, and storage are not shared with other customers. The service is suited to iOS and macOS development, Xcode archiving, automated builds, and inference experiments on Apple Silicon.
Your rental includes the machine configuration and any add-ons listed in your order. You can use the macOS graphical interface and command line to deploy your toolchain. You are responsible for syncing source code, installing dependencies, configuring build scripts and code signing, and distributing artifacts. Renting a machine does not include development or signing services, nor does it guarantee app approval.
The model, node, rental period, and add-ons are those confirmed when you place your order; current availability is shown in real time in the console. When you’re ready to get started,Configure and rent a cloud Macand review the order details again before paying. Don’t rely solely on a previously saved page or quote screenshot.
2. Accounts and orders
Place orders and manage machines through the console. Create your account with an email address that can receive messages, and keep your verification codes, login credentials, and machine access credentials secure. For team use, assign an order owner and grant machine access only as needed. Avoid sharing unmanaged keys among multiple users.
Before placing an order, check the machine model, billing period, node, and configuration options. Use the console records to verify the order number, payment status, service status, and expiration time. A completed payment does not mean the machine has been delivered. Check the instance status and retrieve the host address, port, and initial connection details from the delivery information.
If your order details are incorrect, the payment status hasn’t updated, or the delivery information doesn’t work, sign in to theconsole and submit a support ticketwith your order number and a description of the issue. Don’t make another payment to correct the same order. Never send account passwords, certificate private keys, or complete payment credentials by email or in a support ticket.
3. Billing and payments
All prices are quoted and charged in US dollars (USD). Daily, weekly, monthly, and quarterly rentals are priced separately; don’t calculate the price for one period by multiplying the price for another. Check the rental fee, additional SSD, and Thunderbolt 5 daisy-chain options separately. Before paying, refer to the line items and total shown on the order confirmation page.
We accept USDT-TRC20 and Visa, Mastercard, and Amex via Stripe. Available payment gateways are confirmed by the backend at checkout. For USDT-TRC20, carefully verify the network, recipient details, and amount shown on the payment page. Card payments are processed by Stripe; OSXBuild does not store card numbers.
Keep your order number and transaction records so you can verify payment. View invoices, renewals, and payment status in the console. Submit a support ticket for payment disputes, duplicate charges, or amount discrepancies, and include a transaction ID that can be matched to your order. Cancellations, refunds, and fee adjustments are handled according to applicable law and the rules stated for the specific order, not unconfirmed verbal agreements.
4. Renewals, expiration, and data erasure
Use the expiration time shown in the console to plan your renewal. To keep using the same machine, renew before it expires and confirm that the new rental period is active. Starting a payment, sending an email, or expressing an intention to renew does not complete the renewal. Don’t rely on email notices as your only way to check expiration.
When the rental period ends, the machine enters the recovery process. Its disk is securely erased and the system is reinstalled before the machine is assigned to another customer. The expired machine and its original data are not available as continued storage and should not be treated as a backup. Once erasure is complete, the original data cannot be recovered by placing a new order or paying additional rent.
Before your rental ends, export your source code, build artifacts, required configuration, and signing assets, then verify that your backups work in your own storage. After syncing, remove deployment keys, access tokens, and runner registrations from the machine. Revoke any authorizations for external systems in those systems as well. Before upgrading the configuration, moving to another node, or changing arrangements for multiple machines, confirm the process through a support ticket. Don’t assume data will migrate automatically.
5. Acceptable use
Use the machine only as authorized by law. You may not send spam or fraudulent messages, mine cryptocurrency, distribute malware, attack other systems, launch denial-of-service attacks, or scan, probe, or access other networks or data without authorization. Do not use the machine to bypass access controls, steal credentials, or infringe anyone’s intellectual property or privacy.
You are responsible for the applications, scripts, and network services you deploy on the machine. Open only the ports you need, protect your SSH keys, and promptly address abnormal processes and exposed tokens. Do not make directories containing private keys or sensitive logs publicly downloadable. Obtain the necessary permissions before using customer or team data in build tasks.
If we detect activity that may affect the security of other systems or services, OSXBuild may restrict access, suspend related services, or request an investigation, and will explain the action through your account email or the console. You must cooperate by providing relevant information about tasks and access. Service restoration and any further action will be determined based on the findings, order terms, and applicable law.
6. Software licenses
When using macOS, Xcode, or related development tools, you are responsible for complying with Apple’s software and developer agreements. The rental provides access to hardware; it does not transfer software copyrights, developer credentials, or app distribution rights, nor does it remove your obligation to verify that the software you install is properly licensed.
Commercial software, plugins, model weights, and development dependencies you install must be licensed for your intended use and deployment. Open-source components are subject to their own license terms. Before distributing build artifacts to your team or external testers, check the included files, dependency notices, and distribution scope.
You are responsible for managing signing certificates, provisioning profiles, and API keys. Limit access to signing assets, protect your keychain appropriately, and don’t commit .p12 files or decryption passwords to source repositories. When requesting technical support, provide redacted error details. Never submit secret materials that could be used to sign or publish an app.
7. Availability and incident notices
All nodes operate year-round, 365 days a year, with service provided on a continuous basis. Check machine status and connection details in the console. If you can’t connect, the machine restarts unexpectedly, or a build is interrupted, record the time, node, order number, and error details to help distinguish connection, system configuration, and build-task issues.
For outages or security incidents that affect service, we’ll share confirmed impacts and progress through your account email, console notifications, or the relevant support ticket. Keep your account email accessible. Recovery times depend on the investigation, and unconfirmed timelines are not delivery commitments.
Availability reviews distinguish platform issues and force majeure from impacts caused by your own actions, such as changing network settings, disabling essential services, or deleting system files. Any fee adjustments are based on the order terms and investigation findings. Keep records of incidents; a single build time, indicative network range, or configuration recommendation is not a guaranteed performance level.
8. Liability and dispute resolution
Each party is responsible for matters within its control. OSXBuild is responsible for delivering the agreed machine and handling platform-side services. You are responsible for workloads, software configuration, signing assets, access permissions, and independent backups on the machine. If a loss occurs, both parties should promptly preserve records, take reasonable steps to limit the impact, and determine responsibility based on the cause, actual loss, and applicable law.
Liability and compensation are determined according to applicable law, the service terms expressly stated in the order, and verifiable incident records. No limitation of liability excludes or limits liability that cannot be excluded or limited under applicable law. For data recovery, service suspension, or fee disputes, submit the relevant facts and requested resolution through a console support ticket before repeatedly changing the machine’s state.
These terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first try to resolve disputes through a support ticket or email. If they cannot reach a resolution, either party may submit the dispute to a court with jurisdiction in that jurisdiction. Mandatory rights and procedures under applicable law are not limited by these terms.
9. Changes and effective date
This version takes effect on the date it is published on this page. Read the terms displayed at the time you place an order and keep your order confirmation. We’ll explain material changes affecting billing, rental periods, or data processing through page updates, account email, or console notifications, including when they take effect.
Updates to these terms do not mean that confirmed order prices can be changed retroactively at will. Check the terms agreed to when ordering, subsequent notices, and applicable law to determine how changes affect existing orders and what rights or procedures apply. If you need clarification, ask before continuing or renewing.
For questions about these terms, compliance requests, or disputes, email support@osxbuild.comor sign in to theconsole and submit a support ticket. Specify the relevant terms, order number, and issue. Before attaching logs or files, remove passwords, tokens, and other sensitive information.