1. Service overview
VpsKeep provides cloud Mac rentals. Each delivered instance is a dedicated physical Mac mini, not a virtual machine. During your rental, that physical node is not shared with other users as a compute instance. You can access the macOS graphical interface and command line remotely. After signing in, find the connection address, port and credentials in the portal. Public pages do not provide credentials that can be used to connect directly.
Three models are available: Keep M4 S (M4 / 16GB / 256GB), Keep M4 L (M4 / 24GB / 512GB) and Keep M4 Pro (M4 Pro / 64GB / 2TB). All three models are available in four locations: Singapore, Japan (Tokyo), South Korea (Seoul) and Hong Kong. The model, location, billing period and add-ons actually supplied are those shown in your confirmed order and the service record returned in the portal. Availability is based on the portal's live status.
Before ordering, check that the available memory, storage and software environment meet your workload's needs. Renting a machine does not grant licences for third-party software or guarantee approval or publication by any external platform. Before scheduling builds, tests, inference or editing tasks that require commercial software, a specific runtime or team tools, confirm the relevant licences and compatibility requirements.
2. Accounts & responsibilities
Provide an email address where you can receive notices, and keep your account password, verification codes and recovery information secure. Orders, invoices, renewals and support tickets are managed through your account. If your email address changes or you can no longer receive messages, update your details in the portal or contact support promptly so that you do not miss expiry notices or information about an issue. Do not forward verification codes or stay signed in on a public device.
Connection credentials provide access to your rented machine and must be treated as sensitive information. Limit team members' access to what they need, and promptly replace the relevant passwords and keys when someone leaves a project, credentials are sent to the wrong person or you suspect a leak. Do not put private keys, access tokens or full connection passwords in public repositories, build logs or public forums. When reporting an issue, share redacted error details wherever possible.
The account holder is responsible for authorising members' actions on the rented instance, including installing software, changing network settings, deleting files and running automation. If you notice an unusual login, an order you did not place or an unauthorised action, stop the suspicious access immediately and report it through a portal support ticket or at support@vpskeep.com. Support will investigate using account verification and service records; public chat logs are not accepted as proof of account ownership.
3. Billing & payments
Choose from four billing periods: daily, weekly, monthly or quarterly. The minimum rental period is 1 day. All listed prices and charges are in US dollars (USD). Each billing period has its own price; do not estimate weekly, monthly or quarterly pricing by multiplying the daily rate by the number of days. When confirming your order, check the amount for the selected period, the service start and end times, and any add-ons.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways are determined by the response from the backend. For USDT-TRC20 payments, check the network, receiving address and amount shown on the payment page. Card payments are verified by the payment processor. We will never ask you to send a full card number, card security code or wallet private key by email or support ticket.
When adding +1TB SSD, +2TB SSD or Thunderbolt 5 daisy-chaining, check the quantity of each add-on and its price for the selected billing period. The items and total shown on the order confirmation page are the reference for your payment. After paying, check the payment and delivery status in the portal. A payment screenshot or a record that a blockchain transaction was sent does not confirm that the order has been approved or the machine delivered.
If you are charged twice, the amount is incorrect or the order status has not updated after payment, submit your order number and payment method, along with the transaction hash or Stripe receipt number. Support will check the payment and order records and let you know the outcome. Do not submit another payment to try to refresh the status, or send additional funds to an address from an old order or one you have not verified.
4. Renewals, expiry & refunds
To keep using your machine, sign in to the portal before expiry, review the renewal options, check the new billing period, amount and expiry date, and complete payment. Do not assume that an expiry reminder, a saved payment method or a running task means your rental has renewed automatically. A renewal is confirmed by the order status and updated service term shown in the portal. Until a new service term is confirmed, plan your work around the original expiry date.
To change your billing period, upgrade your model, switch locations or add storage, use the available option in the portal or confirm the change through a support ticket. These changes may require a new delivery, file transfer or environment rebuild. Any price difference, processing time and data transfer method will be based on the order details shown for your confirmation or a plan agreed after review. Do not calculate a payment yourself from the listed prices of two models and transfer that amount.
Access to the service may stop after expiry. Export any code, certificates, assets, build outputs and model files you need to keep before your rental ends. Data retention and deletion are governed by the order notice and information in the portal. These terms do not promise a standard grace period after expiry, and storage on an expired machine is not a long-term backup. Verify your backups before expiry rather than waiting until you can no longer sign in to request recovery.
Submit cancellation or refund requests through a portal support ticket, including your order number, reason for the request and whether the machine has been delivered or used. Duplicate charges, payment issues, delivery problems and service faults will be reviewed against the available records. We will tell you the refundable amount, handling process and expected timeframe after the review. Stopping use early does not automatically change the confirmed billing period or trigger an hourly refund. Before ordering, choose a period that suits your project.
5. Acceptable use
Use the instance for lawful, authorised development, testing, automation, inference or media processing, and comply with the licences for any software you use. Do not send bulk unsolicited email, mine cryptocurrency, conduct attacks, distribute malware, steal credentials or scan networks without authorisation. Do not use a rented machine to bypass access controls, infringe another party's data or intellectual property, or engage in activity that violates Apple's software licence terms.
Security testing requires a clearly defined scope and authorisation from the target. Renting a dedicated physical machine does not grant permission to test external systems. If you use external APIs, datasets, commercial assets or team code, you are responsible for confirming that you have the required access and rights. Software and automation scripts you install must follow these rules too; do not leave compliance entirely to unattended tasks.
If we identify activity that could put service security or other users' interests at risk, we may take necessary steps, such as restricting the activity, suspending access or asking for further information. We will explain the reasons we can disclose by account notification or support ticket. You must cooperate with the review, stop the activity in question and correct the configuration. If you disagree with our assessment, you may provide authorisation documents, a task description and relevant logs for review. Do not resume a task that you have been asked to stop until the review is complete.
6. Availability & issue handling
All nodes operate normally year-round, 365 days a year, with no fixed recurring downtime. Remote access still depends on node hardware, network connectivity, your local connection and software configuration. Distinguish between a connection failure, an application error and a machine fault: a failed build or an inability to connect over your local network does not necessarily mean the entire physical node is unavailable.
If you cannot connect, experience an unexpected restart or have a persistent operational issue, submit a support ticket in the portal with your instance or order number, location, the time and time zone when the issue occurred, connection method, error details and steps already tried. Save any available logs first. Do not repeatedly delete your environment or reset critical settings while troubleshooting. Support will review the service records, assess the impact and explain the next steps for diagnosis or recovery.
Force majeure events, actions taken by you, software you install and issues with your own network will be assessed according to the actual cause. Any adjustment to the service term, charge or delivery will be based on verified impact records and the outcome of the review. Compensation will not be calculated using unverified estimates of downtime. Before carrying out any migration or reinitialisation, confirm how your data will be handled.
7. Data & backups
You retain ownership of code, project materials, assets and other business data stored on your machine. We do not routinely access your business files. If delivery or troubleshooting requires access to your environment, it will be limited to what is needed to address the issue. When submitting a support ticket, use redacted logs and reproducible steps wherever possible, and avoid including unrelated personal information or confidential business data.
You are responsible for maintaining independent backups and regularly checking that they can be restored. Before important builds, system changes, model upgrades or ending your rental, export critical files to storage that you manage. Adding an SSD expands the storage capacity of your rented machine; it is not an independent backup. These terms do not promise default snapshots, version history or recovery of accidentally deleted files.
Before ending your rental, export any files you need to keep, revoke project access tokens, remove sensitive credentials and delete business data you no longer need. Data after expiry will be handled as described in your order notice and the portal; do not assume the original machine will be kept indefinitely. If you need help with a transfer or want to confirm the deletion process, submit a support ticket before expiry. Once deletion is complete, you should not expect the original files to be recoverable.
8. Liability & remedies
We are responsible for providing the agreed physical node and rental term in line with your confirmed order, and for handling account, payment, delivery and service fault reports. You are responsible for authorising your workloads, configuring software, operating your business and backing up your data. When resolving an issue, both parties should rely on order records, payment records, fault details and actual impact rather than unverified assumptions.
Machine specifications do not guarantee a particular build time, model inference speed, third-party approval outcome or business revenue. Test your own projects to confirm resource requirements and workflows before scheduling production tasks with deadlines. If the service does not match your order, submit a support ticket promptly and specify which configuration, term or payment item needs to be checked so we can determine an appropriate correction or billing remedy.
Claims involving loss or liability will be handled based on the cause, evidence, each party's obligations and applicable law. These terms do not exclude or limit rights or liabilities that cannot be excluded or limited under applicable law. Both parties should take reasonable steps to prevent losses from increasing, such as stopping a task, making backups or reporting an issue promptly. We will explain the verified findings and available next steps.
9. Changes & disputes
Updates to these terms will be published on this page. We will notify you through your account or another service notification channel where available about significant changes to billing, usage rules or data handling. Read the current terms before placing a new order or renewing. Check the order record for the configuration, amount and term of an order you have already confirmed; page updates do not change those details automatically.
If you have a question or dispute about a bill, delivery, service handling or the meaning of these terms, first contact support through a portal ticket or at support@vpskeep.com. Include your order number, the issue, relevant supporting documents and the outcome you are seeking. We will review the relevant records and respond. Any additional materials should relate to the dispute; do not send full payment credentials or unrelated sensitive information.
These terms are governed by the laws of the jurisdiction in which the platform operator is established. Any dispute that remains unresolved after the parties have attempted to resolve it will be submitted to a court of competent jurisdiction in that jurisdiction. User rights that apply by law and cannot be excluded by agreement remain in force. The location of a node does not change this governing-law and jurisdiction provision.