Get your questions answered

MiniSSH offers two dedicated physical Mac mini M4 configurations, prepaid by the day, week, month, or quarter. The starting price is $20.8/day. The table below shows base configuration prices, excluding optional storage expansions and Thunderbolt 5 interconnect add-ons. All prices are in USD.

For a short trial, start with a daily rental. If your workload and timeline are clear, compare the weekly, monthly, and quarterly rates. Don’t calculate another period by multiplying the daily rate by the number of days. Before placing an order, check the selected period, add-ons, and total.

If you don’t renew, service and billing stop at the end of your rental, and the node is reclaimed. There’s no deactivation fee. Your machine isn’t paused and held indefinitely after expiry, and a reclaimed node can’t be used to store your files.

Before your rental ends, back up your code, build artifacts, configuration, and any files you need to keep. Make sure the backups are readable. For projects that need to run continuously, check the expiry date in the console and renew in advance. You can let a temporary node expire when an event or project ends.

Data on the node is erased when it’s reclaimed. See the Terms of Service for details about expiry and data handling. Don’t wait until your connection has stopped to plan your backup.

Yes. Place a separate order for the same project and choose the configuration, city, and rental period for the new node. It will be a separate dedicated physical machine with its own rental period, regardless of whether it’s for the same project.

A common setup is to keep a core node for a quarter and add another machine by the week or day during a release rush. When the rush is over, move your artifacts and configuration off the temporary node before letting it expire. A new machine doesn’t automatically share your environment—you’ll need to install your toolchain, project files, and access permissions.

Setup takes about 4 minutes in total: around 1 minute to choose a location and rental period, 1 minute to pay, and 2 minutes to allocate the physical node and prepare the system. Once it’s ready, you can view your SSH credentials and log in. Check the order and node status shown in the console for the latest progress.

Sign in to the console, open the node details for your instance, and check the host address, login username, and connection credentials. Connect using your actual node details; don’t copy the sample address from a guide.

If the status hasn’t updated after payment, keep your order number and payment record, then submit a support ticket in the console. Don’t pay for the same order again just to retry setup.

You rent a dedicated physical Mac mini node, not a virtual machine. It doesn’t share a system account with other tenants. Your order determines the configuration: M4 Core has M4 / 16GB RAM / 256GB SSD; M4 Plus has M4 / 24GB RAM / 512GB SSD.

The macOS graphical interface and command line are both available, making the machine suitable for remote development and builds that need a real Mac environment. If you create multiple user accounts for your team, they still share the resources of the same machine. Dedicated access doesn’t eliminate competition between workloads on that machine.

There are 4 locations: Singapore, Tokyo, Seoul, and Hong Kong. Both M4 Core and M4 Plus are available in all 4. Check the console for current availability when you place your order.

Singapore may be a good fit for teams based in Southeast Asia. If most of your team is in Japan or South Korea, consider Tokyo or Seoul, respectively. Hong Kong may suit teams working with people in Hong Kong, Macau, Taiwan, or southern China. The ranges below are reference figures, not measurements from your current network.

These ranges are for reference only; actual results depend on your connection. Your ISP, cross-region routing, and local network all affect latency. Don’t use these figures to estimate latency from North America to each location.

Tokyo is one option, but its location alone doesn’t guarantee it will be fastest for everyone in North America. First work out who needs to use the remote desktop regularly and who only submits build jobs. Then test from the actual network used by your primary users.

Keep local network conditions consistent while testing SSH interaction, remote desktop responsiveness, and project file transfers. A single round-trip-time measurement won’t tell you whether sustained transfers are stable or how well your actual workflow will perform.

If teammates in Asia-Pacific and North America share one machine, schedule resource-intensive builds around time zones. If several people need to build at once, consider adding a separate node rather than stacking more work on one machine.

All 4 locations run online 365 days a year. As long as your rental is active and the service is operating normally, you can schedule tasks around your team’s time zones rather than waiting for standard business hours.

If you have connection issues, submit a support ticket in the console. Include the node ID, when the issue began and the time zone, any error messages, and the troubleshooting steps you’ve already tried. The service availability commitment is 99.9%. Measurement scope, exclusions, and service-credit terms are set out in the Terms of Service; year-round operation doesn’t mean issues can never occur.

Yes. MiniSSH Mac mini servers provide an always-on macOS environment for remote development, continuous Xcode builds, App Store release builds, and build artifact processing. Use the command line over SSH, or connect to the macOS graphical interface with the help of our connection guide.

First, check how much space your toolchain, build caches, dependencies, and artifacts will need. M4 Core comes with 16GB RAM / 256GB SSD; M4 Plus comes with 24GB RAM / 512GB SSD. Choose based on your actual workload, not just the configuration name.

If your team shares a machine, give each member a separate system account and SSH key, and coordinate build times. You’re responsible for managing signing materials, project access, and artifact backups. Multiple people logging in doesn’t mean you can run unlimited builds in parallel.

Yes. Select the +1TB SSD or +2TB SSD add-on when configuring your order. These are storage expansions on top of a base configuration—not additional base configurations—and they don’t change the memory in your selected machine.

Before ordering, include source code, dependencies, build caches, and archived artifacts in your storage estimate. If you need to change storage on an existing node, confirm the process through a console support ticket and back up your data first. Extra storage doesn’t automatically move existing files or create a backup.

This add-on provides a Thunderbolt 5 interconnect between multiple nodes. It’s charged for each node included in the setup and isn’t part of the base rental. It doesn’t combine multiple machines into one system or pool their memory.

The add-on costs $1.7/day, $4.6/week, $8.6/month, or $23.4/quarter per machine. Before using multiple machines, identify which nodes are involved, how data will move between them, and how the workload will be split. Then confirm the required configuration through a console support ticket.

You don’t need to select it just because you’re doing remote development or a standard build on one machine. The interconnect won’t set up distributed builds, sync your project, or schedule jobs for you.

We accept USDT-TRC20 and Visa / Mastercard / Amex credit cards. Card payments are processed by Stripe. All charges are in USD; available payment gateways are confirmed by the backend when you pay.

For USDT-TRC20, follow the network, address, and amount shown on the order payment page, and keep your transaction hash. For card payments, keep your order number. Never send your full card number, security code, or other sensitive payment details by email or support ticket.

If you’ve paid but your order hasn’t updated, check its status in the console first, then submit a support ticket. For USDT-TRC20, include the transaction hash and order number. For a card payment, include the order number, time of payment, and any message shown on the page. Specify the time zone so we can identify the correct transaction.