1. Service overview
OSXPort rents dedicated physical Apple Silicon Mac mini computers for iOS builds, automated packaging, testing, and other macOS workflows permitted under these terms. During the rental period, the entire physical node is assigned to one customer. It is not a virtual machine, and its build resources are not shared with other customers. A dedicated node does not prevent multiple tasks running on that node from affecting one another; parallel tasks you schedule will still compete for its CPU, unified memory, and storage.
The available catalog has three configurations: Port M4 Base with Apple Silicon M4, 16GB unified memory, and 256GB SSD; Port M4 Plus with Apple Silicon M4, 24GB unified memory, and 512GB SSD; and Port M4 Pro with Apple Silicon M4 Pro, 64GB unified memory, and 2TB SSD. Available regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West Coast. Check the portal at checkout for current availability.
The service provides a remotely accessible physical computing environment. It does not include writing your build pipeline, managing your code repository, or guaranteeing that a particular project will build successfully. You are responsible for your project dependencies, build scripts, signing materials, and the proper licensing of the software you use. Teams that build occasionally and already have an idle Mac may want to compare the costs of running their own hardware. Teams building several times a day that would rather not manage power, networking, and cooling may find a dedicated hosted node a better fit.
2. Accounts and setup
You must create an account using an email address that can receive messages, and keep your sign-in verification codes, account credentials, and node connection details secure. Contact and order information must be accurate and complete. If a team will use the account, an authorized team representative must place the order and decide which members can access the node, billing information, and support tickets. Do not use another person’s identity to open an account or transfer an account to evade usage restrictions.
When ordering, check the model, region, billing period, and any add-ons, then pay the amount shown on the confirmation page. An order, its payment status, and node provisioning are separate steps: initiating payment or returning from a payment page does not mean the node is ready to connect to. Check the order and instance details in the portal for provisioning status, the node address, and connection credentials. If the status does not update after payment, keep your order number and payment receipt and contact support through a ticket.
Use the ordering page to select and pay for a node, and the portal to sign in, view orders, manage instances, and submit support tickets. Do not post complete connection passwords on public pages, in code repositories, or in email messages. Once you’re ready, rent a build node. For questions about an existing order, sign in to the portal to view your orders.
3. Billing and payment
Nodes are available with daily, weekly, monthly, and quarterly billing, all charged in US dollars (USD). The node rental fee and any add-ons, such as SSD upgrades or Thunderbolt 5 daisy-chaining, are itemized in the order. Before paying, check the final amount, selected billing period, and corresponding service term on the order confirmation page. The price shown for one billing period does not indicate the price for another period, and prices are not necessarily calculated at the same daily rate across periods.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways are determined by the response from our backend. For USDT-TRC20 payments, verify the recipient details, network, and amount due, and keep the transaction hash. For card payments, confirm the result with both the payment gateway and the billing status in the portal. Do not make another payment based only on a browser redirect.
If the amount charged is incorrect, you are charged twice, the payment status does not match, or you need to cancel an order, provide the order number, payment method, and relevant proof of payment. Requests involving cancellation, refunds, or unused time will be reviewed in light of order fulfillment and applicable law. Do not assume that simply leaving a node unused cancels the order. Any confirmed billing adjustment will be documented and available for review. Nothing in these terms limits your right to a refund or other remedy under applicable law.
4. Availability
Nodes run in data centers 365 days a year, with no scheduled downtime. The hosted environment provides power, networking, and cooling, so you don’t need to monitor equipment in your office. Year-round operation describes how the service runs; it is not an absolute guarantee that every build will succeed, every network path will remain available, or service will never be interrupted. Project configuration, external dependencies, user actions, and hardware issues can still affect your work.
If you cannot connect to a node or suspect a hardware issue, sign in to the portal and submit a support ticket. Include the instance ID, an approximate start time, connection method, error details, and any checks you have already performed. We will review the node’s status and the scope of the issue, then discuss next steps with you through the ticket. We will obtain your explicit permission before troubleshooting that requires access to your environment. Remove passwords, tokens, and signing private keys from logs.
If a hardware replacement is needed, we will use the support ticket to explain the replacement plan, any changes to connection details, and what you need to do. A replacement node does not mean that all files and environments on the original node will be restored automatically. You should redeploy your build tools, certificates, configuration, and artifacts from independent backups. If the issue affects your purchased service, request a review and resolution in the same ticket. Next steps will be based on the order record and review findings; this page does not promise a fixed compensation percentage or recovery time.
5. Acceptable use
You may use a node only for lawful purposes for which you have authorization. Do not use the service for unauthorized access, credential theft, malware distribution, network attacks, fraud, distributing infringing content, or any other activity that harms third-party systems or rights. Do not scan, break into, or stress-test targets you do not own or have authorization to test. You must also have the necessary rights to use any code, data, software, and models required for your builds and tests.
A dedicated physical machine does not let you bypass the service’s limits. Configure task concurrency, storage growth, and network activity responsibly to avoid security risks or disruption to the infrastructure. You may collaborate with your own team, but must control access and are responsible for authorized members’ activity on the account and node. If you are unsure about a use case, permissions, or software license, ask us before running it.
If we receive a credible abuse report, discover exposed credentials, or identify an active security risk, we may take proportionate steps to limit the risk, including suspending the affected connection or service and, where appropriate, asking you for an explanation or corrective action. In an emergency, we may need to apply a restriction before notifying you. You can provide information and evidence through a support ticket. If our review finds no violation or the risk has been resolved, we will consider restoring access based on the circumstances. Serious or repeated violations may result in termination of the service.
6. Data and backups
You or the relevant rights holder retain ownership of source code, signing certificates, configuration, build caches, and build artifacts that you place on a node. Hosting the service does not transfer ownership of that content. We will not access business content on your node unless you explicitly authorize us to troubleshoot through a support ticket or we are required to do so by law. Any authorization should state the purpose and scope of the investigation; do not grant more access than necessary.
You are responsible for creating and verifying independent backups, especially of signing certificates, private keys, pipeline configuration, and artifacts that cannot be regenerated. Do not rely on DerivedData, dependency caches, or files on the local SSD as your only copy. We recommend keeping reproducible environment configuration under version control and storing sensitive materials outside the node using controlled access. You must verify that backups can actually be restored, not just that files have been copied.
Hardware replacement, system reinstallation, service expiration, or termination may result in node data being erased. Transfer anything you need before the relevant operation or the end of your rental period. Do not assume that data will be retained for a default period or migrated automatically. If you suspect that someone else may have accessed your data, revoke the relevant credentials promptly and submit a support ticket, specifying what you would like us to investigate.
7. Renewal, expiration, and termination
Check the relevant order or subscription record in the portal for the service term and expiration date. If you need a node to keep running nightly builds, release jobs, or other ongoing tasks, confirm your renewal status and complete any required renewal steps before expiration. Not receiving a reminder email does not extend your rental period. Do not assume that every order renews automatically or that a payment you have initiated but not yet confirmed completes a renewal.
If you do not renew before expiration, access to the node and running tasks may stop, and the node will enter the reclamation and data-erasure process. Export certificates, configuration, and artifacts in advance, stop any scheduled tasks you no longer need, and remove the relevant runner from your pipeline. Check with us through the portal to see whether access or the original environment can be restored after expiration; do not rely on an unpromised grace period.
To end a rental early, change models or regions, or close an account, submit a support ticket with the order details and the action you want us to take. For a hardware change or environment migration, confirm your data-transfer and job-switching plan before making changes. If we terminate a service for a violation of these terms, any fees and next steps will be reviewed based on the service provided, the specific circumstances, and applicable law. Stopping use, removing a local runner, or deleting connection tools does not itself constitute a request to terminate the service.
8. Liability and dispute resolution
Each party is responsible for matters within its control. We are responsible for providing the node service specified in the order and reviewing and addressing service issues. You are responsible for your project code, dependencies, task scheduling, access permissions, and independent backups. Issues caused by events beyond reasonable control, your actions, or external systems managed by you should be assessed based on their actual cause and impact, as well as each party’s reasonable steps to limit the harm. A failed task alone does not establish that one party is responsible for all resulting losses.
If you experience a loss or dispute a charge, keep the order details, payment records, support tickets, and relevant logs so we can review the cause and impact. Liability and available remedies are determined under applicable law, the order, and the facts established during the review. These terms do not exclude or limit liability where the law does not allow it, or waive any rights you have under applicable law. Estimated returns or build times that have not been confirmed do not, by themselves, constitute a service commitment or a basis for calculating losses.
These terms are governed by the laws of the jurisdiction in which the platform operator is located. Please first raise any dispute through a support ticket or the designated email address, identifying the order, relevant facts, and the remedy you are seeking. If the parties cannot resolve the dispute through discussion, it will be handled by a court with jurisdiction in that jurisdiction. Mandatory provisions of applicable law that cannot be excluded by contract remain in force.
9. Changes to these terms and contact
We may update these terms in response to changes in service capabilities, business processes, or legal requirements. Updated terms will be posted on this page. We will provide notice and details of material changes affecting existing orders in accordance with applicable law and the relevant order. Updated terms do not automatically apply retroactively to orders already completed. If you have questions about changes to an ongoing service, ask us to clarify before placing a new order or renewing.
For connection, hardware, billing, or renewal questions about an existing node, please sign in to the portal and submit a support ticket so we can link it to your order and instance. For presales, terms, business, or security inquiries, contact support@osxport.com. The only public contact channels are this email address and portal support tickets.
When submitting a request, describe the issue, include the relevant order number and the action you want us to take, and provide any necessary error details. Do not send full card numbers, node passwords, signing private keys, or other sensitive information that is not relevant to your request. To ask for information about the platform operator responsible for your order, or to request related documentation, use one of the channels above and keep a record of your correspondence.