Starting at $20.8/day. Service stops at expiry unless renewed.
Get a dedicated Mac mini M4—not a virtual machine. Choose your model, location, and rental term, then get started the same day. Add a machine during busy periods and let extra nodes expire when demand drops, with no deactivation fee.
All terms—daily, weekly, monthly, and quarterly—are prepaid. Prices are in USD. Availability is confirmed in real time by the console.
Both models use the M4 chip; they differ in memory and built-in SSD capacity. Switch terms to see the listed price for each rental period. Before ordering, confirm the term, expiry date, and add-ons. Prices are per term, not daily equivalents.
Mac mini M4, 16GB RAM / 256GB SSD
$20.8 / day
A good fit for getting remote development, a single project build, or an app packaging workflow up and running. Not sure how much capacity you need? Start with a daily rental to test your toolchain and connection, then choose a longer term.
Mac mini M4, 24GB RAM / 512GB SSD
$41.2 / day
Ideal for workflows that need more memory headroom and room to keep multiple projects and build artifacts on hand. Both models use the M4 chip, so choose based on your project's actual memory and storage needs—not on memory alone as a proxy for a different chip.
These are base machine prices; storage and Thunderbolt add-ons below are extra. Both models include a macOS desktop and command-line environment, with one dedicated physical node for the rental term.
| Model | Hardware specs | Day | Week | Month | Quarter |
|---|---|---|---|---|---|
| MiniSSH M4 Core | M4 / 16GB RAM / 256GB SSD | $20.8 | $56.1 | $103.9 | $282.6 |
| MiniSSH M4 Plus | M4 / 24GB RAM / 512GB SSD | $41.2 | $111.1 | $205.8 | $559.8 |
Choose a model based on memory and built-in SSD capacity, then decide whether you need extra storage or Thunderbolt 5 daisy chaining. Storage upgrades do not change the machine's memory. Daisy chaining is priced per machine; confirm the setup when you order.
| Add-on | Day | Week | Month | Quarter |
|---|---|---|---|---|
| +1TB SSD | $2.9 | $7.7 | $14.3 | $38.9 |
| +2TB SSD | $5.8 | $15.4 | $28.6 | $77.8 |
| Thunderbolt 5 daisy chaining (per machine) | $1.7 | $4.6 | $8.6 | $23.4 |
If you need more room for dependency caches, archives, or build artifacts, review your retention needs first, then choose a +1TB SSD or +2TB SSD. Storage and memory are separate resources; extra storage will not solve a memory shortage.
Thunderbolt 5 daisy chaining is a separate add-on; it does not combine two machines into one with more memory. If your project requires a particular connection setup, describe your use case before payment and confirm the requirements through a console support ticket.
Both models are listed in Singapore, Tokyo, Seoul, and Hong Kong. “Good availability” means the location is generally orderable; check the console for live availability. This table is not a real-time allocation report.
| Model | Singapore | Tokyo | Seoul | Hong Kong |
|---|---|---|---|---|
| MiniSSH M4 Core | Good availability | Good availability | Good availability | Good availability |
| MiniSSH M4 Plus | Good availability | Good availability | Good availability | Good availability |
Start with the location of your primary users, then consider where build artifacts need to go. Remote desktop work depends on an interactive connection; automated builds also rely on code checkout and artifact uploads. If your team connects across the Pacific, test your own network before choosing a location.
All four locations run 365 days a year. If you encounter connection or system issues, submit a console support ticket with the node ID, time of the issue, and steps to reproduce it. Track updates in the same place.
Plan steady workloads separately from temporary peaks. Keep your everyday environment on a long-term node and use an extra machine for a defined task. You don't need to move the whole team to a new machine for every release.
For ongoing use, choose MiniSSH M4 Core at $282.6/quarter, or M4 Plus at $559.8/quarter. Pick the model that fits your project, then check the expiry date in the console.
Best for: everyday remote development and toolchains you need to keep available.
Need an extra build node? Add MiniSSH M4 Core for $56.1/week, or M4 Plus for $111.1/week. Keep peak workloads separate from everyday work to reduce resource contention on a single machine.
Best for: concentrated builds, multi-branch testing, or release preparation.
For temporary testing, start with MiniSSH M4 Core at $20.8/day, or M4 Plus at $41.2/day . Export the files you need when testing is done. The machine stops at the end of the term unless renewed, with no deactivation fee.
Best for: testing an environment, validating an upgrade, or adding short-term build capacity.
Adding a machine means renting a separate node, not adding memory to your existing one. Check the rental term for each node separately. Before a temporary node expires, back up your code, artifacts, and any configuration you want to keep to a location you control.
First decide whether you need a real macOS physical environment, then consider whether your team wants to handle purchasing, deployment, and on-site management. The comparison below covers how each option works, without relying on unverified performance claims.
| Comparison | MiniSSH rental | Owned hardware | Shared virtual machine |
|---|---|---|---|
| Cost | Pay upfront for your chosen term, starting with a day | One-time purchase + hosting costs | Lower price, shared resources |
| Provisioning | Ready the same day | Time needed to purchase and deploy | Instant, but not a physical Mac |
| Resource access | Dedicated physical machine, not a virtual machine | Dedicated, but self-managed | Shared with others |
| Upgrade flexibility | Change models and add-ons by rental term | Buy another machine | Limited by virtualization |
If you already have suitable hardware, network access, and management in place, buying your own machine can also provide a dedicated environment. Renting mainly reduces upfront hardware costs and on-site administration, while making it easy to add capacity for a clearly defined term.
If your workflow depends on the full macOS desktop, command line, or Xcode toolchain, first check that the environment meets your needs. MiniSSH provides a dedicated physical node, but you still need to configure project dependencies, build settings, and team account permissions for your workflow.
Have your use case, rental term, and connection method ready so you can start configuring your node as soon as it's available. From order to SSH access takes about 4 minutes: choose a location and term (about 1 minute), pay (about 1 minute), then allow about 2 minutes for physical node allocation and system setup. Find your credentials in the node details in the console.
List the projects and tools you need to run. Choose a model based on memory use, project count, and artifact size.
Consider where your primary users are and which time zones your team works across. Test remote desktop access, code checkouts, and artifact transfers.
Machines are prepaid by the day, week, month, or quarter. Short-term rentals stop at expiry unless renewed. Back up any files you want to keep before then.
Decide whether you need a +1TB SSD, +2TB SSD, or Thunderbolt 5 daisy chaining, then check the add-on price for the same rental term.
Have a USDT-TRC20 wallet or a Visa, Mastercard, or Amex card ready. All charges are in USD.
Use your public key for connection setup and keep your private key on your own device. If you run into an authentication issue, include the error details in a support ticket—never send your private key.
Only the two payment methods below are supported, and all charges are in US dollars (USD). Available payment gateways are confirmed by the backend. Before paying, check the model, location, term, and final order total.
Select the corresponding gateway and follow the payment details provided with your order. Check the network, recipient details, and amount carefully. Transfers on other networks are not interchangeable.
To confirm payment: submit your order number and transaction hash in a console support ticket, and keep your original payment record.
Pay by card through Stripe, following the gateway's instructions. Check the order status in the console to confirm payment; don't rely on whether the browser page has closed.
For payment issues, include your order number, error message, and the time it occurred in a support ticket. Never send your full card number or security code.
View renewals, expiry reminders, bills, and invoices in the console. You can add a second machine to match your project schedule, but adding a machine and renewing an existing node are separate actions. Check which node and expiry date each order covers.
Once your machine is ready, submit a console support ticket for connection, reinstallation, or renewal issues, including the node ID and time of the issue. If you haven't settled on a model or term, share your team size, main connection locations, and expected use to help decide on a configuration.
Start with a dedicated Mac mini. Choose the right configuration and location, pay for the time you need, then add capacity when work picks up. Service stops at expiry unless renewed.