1. Service Overview
VpsHold provides dedicated physical Mac mini servers in the cloud. Each rental is a real physical server, not a virtual machine. For the duration of your rental, its CPU, memory and storage are not shared with other customers. Use the macOS desktop or command line for development, builds, testing and other software work permitted under these terms.
Our plans include three configurations: Hold 16 with M4, 16 GB memory and 256 GB SSD; Hold 24 with M4, 24 GB memory and 512 GB SSD; and Hold Pro 64 with M4 Pro, 64 GB memory and 2 TB SSD. Choose from five server regions: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the US East Coast. Your confirmed order specifies the model, region, add-ons and rental period. Check the Console for real-time availability.
Choose a rental period of a day, week, month or quarter. The Console order record determines the exact start and end times. The estimated provisioning time of about 4 minutes is a general estimate, not a guaranteed deadline for every order. Payment confirmation, server assignment and initialization progress are shown in your order status. The service does not manage your code, certificates, third-party accounts or applications.
2. Accounts & Orders
Use theConsoleto create and sign in to your account, and manage orders, invoices and support tickets. Provide a valid email address that you own or are authorized to use, and keep it able to receive verification codes, service notices and expiry reminders. If ordering on behalf of a team, you must be authorized to make the rental and payment decisions.
Before placing an order, check the model, region, billing period, storage upgrades and other add-ons. If the listed price differs from the amount shown at checkout, pause payment and contact support to verify it. After payment is received and confirmed by our system, the Console will show the order status. The server is considered provisioned when the instance and connection details are actually available.
Keep your account password, verification codes and server connection credentials secure. Do not publish them or share them with anyone who is not authorized. If team members use the same server, create separate system accounts and assign appropriate permissions. If you notice an unfamiliar sign-in, exposed credentials or an order you do not recognize, change the relevant credentials promptly and report it through a Console support ticket or to support@vpshold.com.
3. Pricing & Payments
Prices for server models and add-ons are those shown on theplans pageand in the order details confirmed before payment. All charges are in US dollars (USD). Day, week, month and quarter plans are priced separately; a rate for one period does not apply to another. Before paying, check whether add-ons are included in the total and review the service start and end times shown in your order.
We accept USDT-TRC20 and Visa, Mastercard or Amex cards via Stripe. Available payment gateways are determined by the response from our backend. For USDT-TRC20, verify the network, recipient details and exact amount due. For card payments, rely on the result confirmed in the payment interface. A transfer screenshot or browser redirect alone does not confirm that an order has been paid.
Check order totals, payment status and renewal records in the Console. For a duplicate charge, an order still awaiting confirmation after payment, or a receipt correction, provide your order number. For USDT-TRC20 payments, you may include the transaction hash; for card payments, include the transaction reference from your payment record. Never send your full card number, security code, password or verification code.
Submit requests to change a plan, cancel early or obtain a refund through a support ticket so we can confirm what can be done and the outcome. Submitting a request does not mean it has been approved, and unused time is not automatically refundable credit. For order changes, wait until the fees and handling have been confirmed before proceeding.
4. Renewals, Expiry & Cancellations
Expiry reminders help you plan renewals and migrations; they do not replace the expiry time shown in the Console. Check your order term, notification email and payment status. To keep your server, renew before expiry and confirm the new end time. A payment that has been initiated but not confirmed does not extend your rental.
Do not assume that you can continue using the server after expiry. If an order includes a grace period, its duration, access restrictions and reclamation time will be stated in the order notice. If no such arrangement is shown, plan to stop your tasks and export your data by the original expiry time. After renewal, check the Console to see whether your existing server and connection details remain in place; old credentials alone do not confirm service status.
Before expiry or cancellation, export your projects, build artifacts, certificates and any configuration you need to keep. Deregister self-hosted runners and revoke access tokens for external systems. Once expiry or cancellation triggers reclamation, we will erase the disk before assigning the server again. The order status and reclamation notice determine the timing. We do not guarantee that data will be retained after expiry.
To change your rental period, resolve an accidental cancellation or check the progress of data reclamation, submit a Console support ticket as soon as possible. Once disk erasure begins, do not rely on the server as a source for recovery. For our data handling practices, see thePrivacy Policy. Keep an independent backup during your rental and check that it can be restored.
5. Uptime Commitment & Credits
Dedicated physical servers run 365 days a year, with a monthly uptime commitment of 99.9%. Uptime is calculated for each calendar month during your active rental, based on the time the service is scheduled to be available: scheduled service time minus verified downtime, divided by scheduled service time. Rentals spanning multiple months are assessed separately for each month. Marketing figures do not replace the service records for your order.
Downtime must result from a service-side issue that prevents the server from providing remote access or the agreed computing service. If you encounter an issue, submit the server ID, incident start time and time zone, error details, and checks already performed. We will verify the start and end times against server records and ticket details. A single failed connection, client configuration issue or application crash does not by itself mean the entire server was unavailable.
If monthly uptime falls below 99.9% , we will extend the service by the verified downtime. Credits apply to the affected order and must be requested and confirmed through a Console support ticket. They are not calculated from hypothetical business losses or a fixed multiplier. We will record the findings, extension and revised expiry time in the order or ticket.
Issues caused by force majeure, your own shutdowns or changes to network and security settings, software you run, your local network or third-party systems do not count as service-side downtime. We will assess causes using the available records. If you disagree with the attribution or duration, provide supporting evidence in a ticket and request a review.
6. Acceptable Use
Use the server only for lawful, authorized work that does not harm others. Do not send bulk unsolicited email, mine cryptocurrency, launch network attacks, distribute malware, steal credentials, host infringing content or use the service to evade lawful access controls. Security testing must be limited to systems you own or have explicit permission to test, and must not affect other users or public networks.
You must have the necessary rights to any code, models, media and data you upload, store, run or publish. Do not use the server for unauthorized scanning, password guessing or traffic attacks, and do not share connection credentials publicly to provide uncontrolled access. Set appropriate permissions, concurrency limits and logging for automated tasks to help prevent accidental data exposure.
If we identify a policy violation or an immediate risk to service security, we may restrict access or suspend the affected service and explain why through an account notice or support ticket. For urgent risks, we may take necessary protective action before notifying you. You must cooperate with our investigation, stop the prohibited activity and provide relevant information. Service can be restored once the risk has been addressed and our review is complete.
7. Software Licensing
Renting a physical server does not grant you additional licenses for the software on it. You are responsible for complying with Apple’s software license terms and the licensing requirements for any software, development tools, models and dependencies you install or use. Before using tools that require a separate purchase, subscription or license, confirm that the license covers remote physical servers and your team members.
You may use the macOS desktop and command line for the agreed development work, subject to the terms that apply to Xcode, simulators, builds and code signing. Preinstalled tools do not guarantee compatibility with every third-party plugin, project dependency or specific version. Before changing toolchains or importing certificates, record your versions, make a backup and test a small, repeatable build.
You are responsible for managing certificates, private keys, provisioning profiles and software license credentials. Do not put them in public repositories or unprotected ticket attachments. When you cancel, a team member leaves or credentials are exposed, promptly revoke the relevant tokens and access permissions. For help troubleshooting or migrating your environment, seeConnection & Development Support.
8. Liability & Risk
Each party is responsible for matters within its control. We are responsible for provisioning the agreed physical server and handling service-side operations. You are responsible for your account security, system configuration, application behavior, data backups and software licenses. If a hardware failure requires a replacement server, the arrangements and connection details will be confirmed in a support ticket. Your applications and projects should be recoverable from independent backups.
Dedicated hardware does not guarantee a particular build speed or the performance of third-party apps, external code repositories or your local network. For critical releases, signing, training or batch jobs, verify your toolchain and resource requirements first, and keep backups of your outputs. Responsibility for an incident will be assessed based on its cause, actual impact and verifiable evidence—not on either party’s estimate alone.
If service-side uptime falls below the commitment, service-time credits are handled under Section 5. Other claims for loss should be assessed based on direct impact, causation and each party’s reasonable obligations. Nothing in these terms limits liability that applicable law does not allow to be limited or excludes rights you have under applicable law. Keep a record of any dispute in a support ticket and try to resolve it together first.
9. Changes, Governing Law & Disputes
These terms take effect on the date of publication. We will announce important changes affecting pricing, service scope or user rights on our website and through appropriate account notifications, with details of their scope and effective date. Orders already confirmed remain subject to the terms in effect when confirmed. Before confirming a renewal or new order, review the terms then in effect; updates to this page do not automatically change existing confirmed orders retroactively.
These terms are governed by the laws of the jurisdiction where the platform operator is based. If a dispute arises, both parties should first try to resolve it based on order, payment and support ticket records. If they cannot reach an agreement, either party may submit the dispute to a court with jurisdiction in that jurisdiction. Mandatory rights and procedures under applicable law remain in effect.
For questions about these terms, order disputes, compliance document requests or other service issues, sign in to theConsole and submit a support ticketor email support@vpshold.com. Include your order number, a brief summary of the issue and what you would like us to do. Do not include passwords, verification codes or sensitive information that has not been redacted.