1. Service scope
MiniSSH provides dedicated physical Mac mini (Apple Silicon) servers for rent. During your active rental term, you use the physical node assigned to your order; it is not shared with other customers. This is not a virtual machine service. Use the macOS graphical interface and command line for remote development, builds, and app packaging.
We offer nodes in Singapore, Tokyo, Seoul, and Hong Kong. Available models, locations, and add-ons are listed in the plans and confirmed in your order. Check the console for real-time availability. Before ordering, verify the model specifications, location, term, and total.
Nodes are provisioned on the day you order. Choosing a node and term takes about 1 minute, payment about 1 minute, and physical node allocation and system setup about 2 minutes. The full process typically takes around 4 minutes, but this is not a guaranteed completion time for every order. Once payment is confirmed and the node is ready, you can find its connection credentials in the instance details in the console.
2. Billing and terms
Service is prepaid by the day, week, month, or quarter. Model and add-on prices are listed on the Plans & Pricing. The amount due is shown in your order summary before you submit payment. Check the start and end dates before paying. Each additional node is a separate order and does not automatically share the expiry date of your existing nodes.
You can rent a second node whenever you need one and choose its term separately. Service stops at expiry if you don’t renew. There’s no deactivation fee, and no further rental charges accrue without a renewal. Stopping use, shutting down your own processes, or ending a connection early does not cancel a prepaid term that has already started.
To renew, change a future term, or update your configuration, use the console before expiry and check the confirmation. If an order has already been paid and you believe you were charged twice, provisioning failed, or the amount is incorrect, submit a ticket for review. Whether a refund is due and how it is handled depend on order fulfillment and applicable law.
3. Payments and verification
We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. All payments are processed in US dollars (USD). Available payment gateways are determined by the response from our backend. Follow the network, payment details, and amount shown on the order page. Don’t transfer funds based on an older order.
For a USDT-TRC20 payment review, provide your order number and transaction hash in a console ticket. For a card payment review, provide your order number, payment time, and any error message shown. Never send your full card number, security code, account password, or other sensitive credentials.
After payment, check the order status in the console to confirm it was received. A screenshot on your device alone does not confirm payment. If the status hasn’t updated or you’re concerned about a duplicate charge, keep your proof of payment and submit a ticket. Don’t pay for the same order again until it’s been checked.
4. Uptime and service credits
All nodes run year-round, 365 days a year. Uptime is calculated for each paid node based on its active service time. For example, a 30-day measurement period has 43,200 minutes. Outages attributable to the platform’s node or network that prevent normal use count as downtime.
Uptime commitment: about 43 minutes of downtime allowance per 30 days.
The precise allowance is 43.2 minutes. Downtime beyond this allowance is credited as equivalent service time under these terms.
Submit a console ticket with the node ID, outage start and end times, and time zone.
For active service periods shorter than 30 days, the downtime allowance is prorated based on the actual number of active service minutes. Once verified downtime exceeds that allowance, the excess is credited as an equivalent amount of service time. Credits are not calculated from business revenue, project losses, or estimated labor costs. We’ll share the review result and credit details in the ticket.
Force majeure, shutting down the node or changing its system or network settings yourself, application failures, and issues with your local network or internet provider do not count as platform downtime. When submitting a request, include the connection failure symptoms, relevant logs, and steps to reproduce the issue. We’ll review node records to verify the cause and timing. You do not need to provide private keys or passwords in a ticket.
5. Acceptable use
You must ensure you have the necessary rights to use all software, code, data, and activities on your node. You must not use the service for unauthorized access, malware distribution, cyberattacks, fraud, spam, infringement of others’ rights, or other unlawful activity. You must not attempt to access another customer’s node or credentials, or the platform’s management systems.
Keep builds, uploads, and remote development within your order’s configuration. Do not bypass access controls, probe the platform’s internal network, or disrupt other nodes or networks with unusual connections or sustained attack traffic. A dedicated physical server does not give you permission to misuse shared network infrastructure.
If we detect unusual activity, we may ask you to explain its purpose, stop the relevant task, or correct your configuration. To prevent ongoing attacks, security risks, or unlawful activity, we may first restrict relevant connections or suspend the affected service, then explain the action through an account notice or ticket. You can request a review by providing logs and an explanation of your use. Service will be restored based on the risk being resolved and the review outcome.
6. Expiry and data
You own the code and files you store on your node. Keep your own restorable backups and, before expiry, export any files, build artifacts, and configuration you need to retain to a location you control. Do not treat a single copy on the node as your project’s only backup.
If you don’t renew by expiry, service stops and the node enters the recovery process. Data on the node is erased before it is prepared for reassignment. A brief connection after expiry does not extend your rental term, and you should not assume there is a recoverable data retention period. After service stops, connection credentials and files on the node may no longer be available.
Reinstalling the system may also erase existing data. Back up your data before requesting a reinstall, and specify the node ID and scope of the operation in your ticket. If data has already been lost, you can submit a ticket to explain what happened, but data that has been erased or cleared should not be considered recoverable. See our Privacy Policy.
7. Liability and disputes
We provide the node service specified in your confirmed order and address platform-side provisioning, billing, and connection issues. You are responsible for account and SSH key security, software licensing, application configuration, and data backups. Before deploying production workloads, validate your toolchain and application configuration. Don’t rely on a single node as your only source of data or service.
If a dispute arises, both parties should review order and payment records, node logs, and ticket correspondence to establish the facts. Service credits for platform downtime are handled under Section 4. Other liability for breach is determined based on actual performance, verifiable losses, and applicable law. Nothing in these terms excludes or limits liability or user rights where applicable law does not allow it.
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 console ticket or support@minissh.com . If they cannot reach a resolution, the dispute will be submitted to a court with jurisdiction in that jurisdiction.
8. Changes and effective date
These terms apply from the effective date shown on this page. If we change our service rules, we’ll update this page and its date. We’ll notify you through an account notice or ticket about material changes affecting orders already in effect. We won’t use silent page edits to retroactively add charges to a confirmed rental term.
Read the terms in effect at the time before confirming a new order or renewal. If you have questions about a change, submit a ticket for clarification before adding a new term. Nodes not renewed by expiry stop service and are reclaimed as described in Section 6.
For questions, order checks, service issues, or concerns about these terms, contact us through a console ticket or support@minissh.com . Include your order number or node ID and your time zone so we can check the timing accurately.