1. Service overview
VPSMerge provides Apple Silicon Mac mini rentals for teams running Xcode builds, automated tests, archiving, macOS CI runners, and remote development. Each rental is a dedicated physical machine, not a virtual machine. Throughout the rental term, each physical node is assigned to one customer and its CPU and memory are not shared with other customers.
Available configurations are Merge M4 S (Apple Silicon M4, 16GB RAM / 256GB SSD) and Merge M4 L (Apple Silicon M4, 24GB RAM / 512GB SSD). Choose from five locations: Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast. Configurations, add-ons, and availability are as shown in the console and confirmed in your order.
Your rental includes remote access to the assigned machine for the duration of the term, with full access to the macOS graphical interface and command line. Dedicated resources do not guarantee a particular build time. Dependencies, project code, concurrent workloads, and toolchain settings all affect results. You are responsible for configuring, testing, and sizing the machine for your own pipelines.
2. Accounts and orders
Create an account, configure orders, and manage instances through the console. Provide an email address that can receive notifications, secure your login verification details and SSH and VNC credentials, and restrict access within your team. Anyone placing an order on behalf of a team must have the necessary authority. Your team should decide who is responsible for renewals, billing, and instance management.
Before ordering, check the model, location, billing period, storage upgrades, and total price. Payment status, physical node assignment, and the start and end of your rental term are determined by the records in the console. Initiating a payment or submitting proof of transfer does not mean the instance has been delivered.
If you suspect your account or credentials have been compromised, change the affected credentials promptly and open a support ticket with the instance ID and the time period when the issue occurred. For issues with an existing instance,open a support ticket in the console; if you’re ready to get started,rent a cloud Mac.
3. Billing and payment
Choose from four billing periods: daily, weekly, monthly, or quarterly. Prices and invoices are in US dollars (USD). Each period is priced separately, so don’t assume the price for one period applies to another. Before paying, check the base configuration, add-ons, rental term, and total amount due in the console.
We accept USDT-TRC20 and Visa, Mastercard, or Amex processed by Stripe. Available payment gateways are determined by the response from our backend. For USDT-TRC20, carefully verify the network, receiving address, and amount shown on the payment page. Card payments are complete only when confirmed by the payment gateway and reflected in your console billing status.
Leaving an instance idle, taking a runner offline, or stopping build jobs does not end a purchased rental term. To change the model, add or remove an add-on, end an order early, or request a refund, open a support ticket so we can review the delivery status and applicable terms. Simply stopping use does not change or cancel an order.
4. Renewals, expiration, and data removal
Keep track of your instance’s expiration date in the console and renew before it expires if you need continued access. Renewal status and the new service term are determined by confirmed payment and instance records. Without a confirmed renewal, don’t assume your existing instance will remain available.
You are responsible for managing and backing up your repositories, certificates, provisioning profiles, build artifacts, caches, and other files. Before your rental ends, copy any data you want to keep to storage managed by your team and make sure the backup is readable. Dedicated instance storage is not a separate backup service.
When an instance expires without renewal, it will be taken out of service under the release process and its disk will be erased. Files will not be retained for recovery. If you have trouble renewing or exporting your data, open a support ticket before expiration with the instance ID, billing reference, and details of the issue. Do not rely on post-expiration recovery as a backup plan.
5. Uptime commitment
All nodes are designed to run 365 days a year, with a monthly service uptime commitment of 99.9%. Uptime is assessed over the monthly service period for the relevant instance. Based on a 30-day month, 0.1% is approximately 43 minutes of allowable downtime. This is an illustration of the commitment, not historical monitoring data.
Any downtime beyond this allowance is credited as service time, calculated according to the duration of the impact.
To request a service credit, sign in to theconsole and open a support ticketwith the instance ID, the start and end times of the impact and the time zone, plus any connection errors or task logs. We’ll review the scope of the impact against the instance status, service records, and materials you provide, then explain our findings and how the service-time credit will be handled in the ticket.
Downtime does not include cases where you shut down the machine, misconfigure the network or system, experience an application failure, or have a problem with your own network connection. Events beyond reasonable control will be assessed based on available evidence and applicable law. Slower builds or a failed individual job do not by themselves mean the entire instance was unavailable; remote connectivity and the status of core services will also be considered.
6. Acceptable use
You must not use the service for cryptocurrency mining, bulk unsolicited email, network attacks, malware distribution, unauthorized access, distribution of infringing content, or any other activity that violates applicable law or the rights of third parties. Do not bypass access controls, disrupt the platform’s infrastructure, or attempt to access instances or data that are not yours.
You are responsible for the actions of your team members, runner scripts, dependencies, and automated jobs. Protect credentials and prevent uncontrolled task execution. If you detect an unusual process or suspicious network activity, stop the relevant jobs promptly, retain necessary logs, and contact us for review.
If there is reasonable evidence that an instance is creating a security risk or causing ongoing harm, we may take necessary and proportionate measures, including restricting connections or suspending the affected service. Where practicable, we’ll explain the reason and next steps. You can request a review by submitting an explanation and evidence of remediation through a support ticket.
7. Software licenses
You are responsible for complying with applicable Apple software license terms, as well as the license terms for any development tools, dependencies, models, plugins, or other software you install or use. Renting a physical machine does not grant additional rights to third-party software or replace your team’s existing licensing obligations.
Check that your Xcode version, SDKs, simulator runtimes, and project dependencies are compatible, and manage signing certificates and permissions carefully. We provide the machine and remote access; you are responsible for your project’s build configuration, signing authorization, artifact distribution, and release compliance.
8. Liability and handling of issues
We provide the dedicated physical node specified in your confirmed order and investigate and address delivery or core service issues attributable to the platform. You are responsible for your code, data backups, access permissions, and task configuration. If an issue arises, both parties should establish the facts using the order, billing records, instance records, and logs, and take reasonable steps to limit further impact.
If uptime falls below the commitment, service-time credits are assessed under Section 5. Other service disputes will be handled based on the services actually provided, the cause of the issue, and any provable direct losses. Credits do not limit or waive rights that cannot be limited or waived under applicable law, or exclude liability that cannot legally be excluded.
If you discover an issue, retain relevant evidence and report it promptly. Avoid deleting key logs before they have been reviewed. We’ll explain the steps we can take. The outcome for an individual issue will be based on the related support ticket and order records and will not automatically change the terms of other orders.
9. Changes and dispute resolution
We may update these terms as our services or compliance requirements change. New versions and their effective dates will be published on this page. We’ll notify you by account email or through the console of material changes affecting the rights associated with confirmed orders. Existing orders will be handled in accordance with applicable law, the original order terms, and the specific notice.
These terms are governed by the laws of the jurisdiction where the platform operator is based. If a dispute arises, both parties should first explain the facts and seek to resolve it through a support ticket or email. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction.
If you have questions about these terms, billing, or service scope, sign in to theconsole and open a support ticketor emailsupport@vpsmerge.com. For existing orders, include the order number or instance ID. Never send passwords, verification codes, private keys, or full payment card details by email or support ticket.