Compare prices upfront, then choose your workstation
One Workstation, Four Rental Terms
Get an entire Mac mini M4 to yourself, rented by the day and billed in USD. Choose a term based on your project timeline, then decide whether to add storage—no need to guess between a long list of models.
Dedicated physical machine, not a VM · 1 configuration · 6 locations at the same price · From $21.7/day
Same machine, your choice of term
Desk M4 is the only configuration available. All four terms include the same M4, 16GB memory, and 256GB SSD, with dedicated access to the physical machine regardless of term length. Prices below cover the base workstation and exclude optional add-ons.
Dedicated Workstation
Desk M4
Mac mini M4 · 16GB RAM · 256GB SSD
Chip
M4
Unified memory
16GB
Base storage
256GB SSD
A dedicated cloud Mac for builds, scripts, and development toolchains. Use the full macOS graphical interface and command line; choose the remote access method that fits your workflow.
Choose a billing term to see its base price
$21.7/day
Rent by the day to test connectivity, your toolchain, and a complete build.
Don't decide based only on the upfront payment. If your work spans multiple iterations, estimate how long you need the environment and compare the matching term. The prices above aren't calculated by multiplying the daily rate, and terms don't switch automatically.
Add storage as needed without changing the base machine
Plan for disk space before scheduling work
Project source code is rarely the biggest disk user. Simulator images, DerivedData, dependency caches, and model weights can keep growing. The +1TB SSD and +2TB SSD are storage add-ons, not separate machines, and they don't increase the 16GB of unified memory.
Add-on prices by term in USD; Thunderbolt 5 linking is priced per machine
Add-on
Daily
Weekly
Monthly
Quarterly
+1TB SSD
$2.3
$6.2
$11.4
$31
+2TB SSD
$4.6
$12.4
$22.8
$62
Thunderbolt 5 linking (per machine)
$1.3
$3.5
$6.4
$17.4
SSD: Store caches and model weights
Estimate the space needed for projects, build artifacts, and regenerable caches. Keep essential project copies, and move large downloads and reusable data to the expansion drive. Extra capacity is not a substitute for a separate backup.
Link machines only when your workload can be split
Thunderbolt 5 linking is for setups that need multiple machines. It doesn't automatically combine them into one pool of unified memory or guarantee that a single build will run proportionally faster. Choose only after defining how data will move and how tasks will be divided.
Choose a setup based on your workload
These are starting points, not performance guarantees. For iOS builds, consider project size and concurrency; for inference, check the model's actual memory use. Running a representative workload is more reliable than judging by parameter count or project count alone.
Choose a Desk M4 term, storage upgrade, and validation task for your workload
Workload
Suggested starting configuration
Suggested term
What to validate first
Light builds
Base Desk M4; single-app builds and TestFlight uploads
Daily
Confirm that dependency installation, signing credentials, archiving, and upload all work end to end
Disk growth, cache hit rates, and memory pressure when running multiple tasks
LLM inference experiments
Desk M4 +2TB SSD; quantized 7B–8B models with MLX / llama.cpp. Consider Thunderbolt 5 linking if you need multiple machines
Quarterly, after an initial short-term test
Quantization quality, context length, runtime overhead, and peak memory; an SSD upgrade does not add memory
If a task is already close to the memory limit, reduce concurrent tasks, shorten the context, or adjust quantization first. More disk space won't solve a memory shortage. If your team needs multiple machines, consider assigning builds, tests, and inference to separate workstations.
Choose by project duration, not habit
Debug today or keep it running long term?
Decide how long you need the environment before choosing a term. Short-term work is about validation; ongoing work benefits from avoiding repeated installs and cache rebuilds. All four terms use the same dedicated physical workstation.
For quick debugging, choose daily
Base price: $21.7/day. Ideal for testing remote access, fixing a build issue, or checking that dependencies install correctly. Prepare your project and build commands first so you don't spend your rental time gathering materials.
Goal: complete one repeatable build.
For a focused sprint, choose weekly
Base price: $58.6/week. Ideal for concentrated fixes, testing, and delivery. Keeping dependency caches on the same machine can save you from rebuilding the environment between tasks; actual build speed still depends on your project and caching strategy.
Goal: run the same workflow reliably, repeatedly.
For always-on CI, choose monthly or quarterly
Base price: $108.6/month or $295.4/quarter. A good fit for a Runner that receives ongoing jobs. Pinning toolchain versions and managing concurrency and disk cleanup matter more than fixing the environment at the last minute before every release.
Goal: establish a long-running workflow with backups.
Quarterly equivalent: $295.4 ÷ 3, or about $98.5/month. This is for comparing term costs, not a separately selectable monthly plan; the monthly base price remains $108.6.
Six locations, one base price
Desk M4 is available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the US East Coast, and the US West Coast, all from $21.7/day. Consider your team's usual network and where jobs are triggered, then test the actual connection. There's no need to recalculate the base price by location.
All listed locations show “Available.” Check the console for real-time availability. Every location operates year-round, 365 days a year; confirm your rental term and instance status separately in the console.
Singapore
A good option for workflows involving teams across Southeast Asia. Test repository access, dependency downloads, and artifact transfers—not just whether you can connect.
A good fit for development with teams across East Asia. Test remote desktop responsiveness for interactive work; for automated builds, focus on repository and artifact transfers.
Worth testing first for workflows with teams in South China and Southeast Asia. Actual performance depends on local carriers and routing, so test a complete workflow.
A location to consider for collaboration across eastern North America and Western Europe. For CI, check where your repository, package sources, and result destinations are hosted.
A location to consider for teams on North America's West Coast. Interactive work and background builds have different network needs, so test your primary workload.
This checklist doesn't collect any information. Use it to confirm your setup and prepare what you need, then verify the final order on the checkout page. If you can't answer one of these questions yet, write it down clearly before contacting support.
Your use case is clear: you know which build command, CI workflow, or inference experiment you'll run, and have a sample ready to validate the results.
Your location is chosen: base your choice on your team's main network and time zone. Plan to test repository access, remote connectivity, and artifact transfers instead of relying on geographic distance alone.
Your term is clear: you know whether you've chosen daily, weekly, monthly, or quarterly billing, and will check the order status and expiry date in the console.
Your storage needs are estimated: check whether the base 256GB SSD is enough, whether you need +1TB SSD or +2TB SSD, and how you'll clean up regenerable caches.
Your payment method is ready: use USDT-TRC20 or Visa / Mastercard / Amex (via Stripe). Before paying, confirm the USD amount and the payment gateway available to you.
You know how to access the console: sign in from this site's “Console” link to check your order, connection details, and renewal status. For instance-related help, submit a support ticket after logging in.
All listed prices are charged in US dollars (USD). Before paying, check the base workstation, add-ons, billing term, and location. After submitting your order, confirm its status in the console; completing payment doesn't replace checking that your instance is active.
Two payment options
We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment gateways available to you are determined by the backend. For USDT, use the network, address, and amount shown on your order; don't switch networks.
Keep your order number and transaction receipt for reference.
Check the date and status before renewing
If you need to keep using the service, check the expiry date and renewal status in the console ahead of time. Don't assume that starting a payment means your renewal succeeded, or that year-round operation at a location automatically extends your order.
Check your order status in the console to confirm renewal.
Export your data before expiry
If you don't plan to renew, export your code, build artifacts, and essential configuration ahead of time. After expiry, service suspension, resource release, and disk erasure follow the service terms and order status. Don't assume you'll still be able to connect or recover data after expiry.
Include add-on SSDs in your backup and offboarding checks.
See the full policy for payment processing, refunds, and expiry. If the payment status doesn't match what happened, contact support through a console ticket or at support@macminivps.com with your order number, transaction receipt, and a description of the issue. Never send passwords or private keys by email.
Start with the billing and connectivity FAQs. For multiple workstations, storage planning, or a team workflow, tell us about your workload, term, and location needs. We'll review each item against the published prices so you don't have to guess at a configuration.