Pre-order checklist

Get the key details clear before renting a cloud Mac

This guide covers device characteristics, two configurations, four billing periods, five available locations, access permissions, payment methods, and data handling after service ends. Answers follow the actual ordering journey, making it easy for developers, CI/CD leads, and research teams to verify the details.

2 options Fixed configurations available
5 Available service locations
$20.6/day Current starting price
Device characteristics

Cloud access, dedicated physical resources

MiniRent provides physical Mac minis that are available remotely; shared computing resources are not presented as dedicated devices. To assess fit, first consider whether your workload needs a stable macOS environment, continuous availability, and reproducible configuration.

Does MiniRent provide virtual machines?

No. Every valid order corresponds to one dedicated physical Mac mini. Its processor, memory, and local storage are not shared with other tenants. The service is connected to and managed through the cloud, but the underlying device remains independent rather than a virtual machine instance.

This distinction directly affects environment consistency and troubleshooting. The system resources you see belong to the device assigned to your order and are not shared because another tenant temporarily increases its workload.

Which workloads are a good fit for a cloud Mac?

Common uses include iOS and macOS development, Xcode command-line builds, continuous integration runners, Fastlane automation, remote development, and MLX-based model inference testing. Both the macOS graphical interface and command line are available, making the service suitable for long-running environments and shared team build access.

If a task depends on substantial memory, prolonged parallel builds, or large amounts of local data, choose a configuration based on peak memory, build queue length, and disk growth—not just current idle usage.

Can the device run continuously year-round?

All five locations are organized to run normally 365 days a year. Users should still maintain independent backups of code, certificates, keys, build artifacts, and critical logs rather than treating a single remote device as the only data copy.

Models and options

Two M4 configurations, with no hidden tiers

The current catalog has exactly two Mac Mini M4 options. Choose based primarily on sustained memory usage, concurrent build count, dependency-cache size, and local working-set size.

Core builds and remote development

MiniRent M4 Core

Suitable for single-project development, standard Xcode builds, lightweight CI runners, and everyday remote work.

Chip
M4
Memory
16GB RAM
Local storage
256GB SSD
Concurrent tasks and larger working sets

MiniRent M4 Plus

Suitable for higher memory usage, multitask builds, larger dependency caches, and continuously running research workloads.

Chip
M4
Memory
24GB RAM
Local storage
512GB SSD
How do I choose between the two configurations?

First record peak memory usage, DerivedData size, and dependency-directory usage during a complete local build, then count how many builds must run concurrently. A single project with sequential builds can usually start with MiniRent M4 Core; multiple runners, larger workspaces, or MLX inference workloads are better suited to MiniRent M4 Plus.

Only the two configurations listed above are available. If you need more space, select +1TB SSD or +2TB SSD when ordering; these are storage add-ons, not additional model tiers.

Pricing and billing periods

Four separately priced periods, starting at $20.6/day

Daily, weekly, monthly, and quarterly prices are displayed separately rather than automatically converting one period into another. Confirm the quantity, period, and final amount during checkout.

Full-term pricing for both dedicated physical Mac mini options
Plan Configuration Daily Weekly Monthly Quarterly
MiniRent M4 Core M4 · 16GB · 256GB $20.6/day $55.5/week $102.8/month $279.6/quarter
MiniRent M4 Plus M4 · 24GB · 512GB $41.2/day $111.3/week $206.1/month $560.6/quarter
Which configuration is included in the lowest starting price?

The $20.6/day price applies to MiniRent M4 Core: M4, 16GB RAM, and 256GB SSD. It does not include an additional SSD or Thunderbolt 5 expansion option. The order total is calculated separately for the selected period, quantity, and add-ons.

Can I calculate daily, weekly, monthly, and quarterly rentals myself?

Self-calculating by multiplying days is not recommended. The four periods are independent price options, so select the one that matches your intended usage. For changes, check the permitted actions for the current order in the console and confirm when the change takes effect and the resulting amount; do not replace the order record with simple arithmetic.

Location coverage

Five fixed locations currently available

Choose a location based first on where you connect from every day, then consider your code repository, build-artifact destination, and team distribution. Actual performance over long distances is affected by local carriers and interregional routes.

Singapore

For Southeast Asia connectivity.

Japan (Tokyo)

For teams in Japan and Northeast Asia.

South Korea (Seoul)

For teams in South Korea and nearby regions.

Hong Kong

For connectivity from Hong Kong and nearby regions.

US West Coast

For collaboration across the North American West Coast and the Pacific.

Are both models available in all five locations?

Yes. MiniRent M4 Core and MiniRent M4 Plus are both available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West Coast—a total of 5 locations. The catalog does not split these into additional cities or separate US West Coast listings.

How do I determine which location is best for remote development?

Test from the primary operator’s everyday connection city first, then check the regions hosting your code repository and build-artifact destination. Interactive remote desktops typically prioritize round-trip latency, while batch builds depend more on dependency downloads, repository pulls, and artifact-upload routes. See the Locations and data centers pagefor the selection method and testing criteria.

Availability and delivery

All catalog combinations show “Available”

All combinations of the two models and five locations can be ordered. The page does not use temporary quantity indicators to estimate delivery time; the console returns the live result during checkout.

Available catalog

2 models × 5 locations

All combinations: Available
MiniRent M4 CoreAvailable in all 5 locations
MiniRent M4 PlusAvailable in all 5 locations
Delivery status: “Available” means that the model-and-location combination is normally orderable; it does not promise a fixed delivery time in minutes. Actual delivery time, order progress, and device status are returned live by the console.
Where can I check delivery status after ordering?

Sign in to the consoleto view order records, delivery progress, and device information. For order changes or delivery issues, submit a ticket from the relevant order and include the order number and time of occurrence. Do not infer the status of a specific order solely from the catalog page.

Connectivity and permissions

Access details come from the order; credentials are managed per device

After delivery, the connection endpoint and device identifier are associated with the order. Before connecting for the first time, teams should define the key custodian, remote-access sources, and credential-rotation rules.

SSH keys

Use a dedicated key for the device rather than reusing a personal everyday key. Rotate it immediately when team membership changes or exposure is suspected.

Remote desktop

Suitable for graphical-interface work. Sign out after finishing and do not store reusable credentials in a shared terminal.

Administrator access

Use it to install tools and configure the working environment, not to bypass infrastructure controls or affect external device networks.

Where can I find the connection address and initial credentials?

After delivery, retrieve connection details from the relevant order and device details in the console. Do not paste addresses, usernames, keys, or remote-desktop credentials into public repositories, public ticket attachments, or unencrypted team documents.

What can administrator access do, and where are the limits?

Administrator access is primarily for installing development tools, configuring the build environment, managing local services, and maintaining project dependencies. Users must not use it to access other devices, disrupt location networks, evade access controls, or conduct unauthorized scans.

Before making substantial system-level changes, record the original values and rollback method. For SSH, firewall, or remote-desktop changes, keep a verifiable backup connection path first so configuration errors do not lock you out.

When should credentials be rotated?

Rotate them immediately when a team member leaves the project, a key reaches an uncontrolled device, sensitive content appears in logs, the connection source changes, or unusual login activity is detected. Maintain separate owners and update records for SSH credentials, CI tokens, and signing materials rather than sharing one long-lived secret.

For detailed connection and troubleshooting steps, see the Help Center, then check the local network, address resolution, port reachability, key permissions, and device status in that order if you cannot connect.

Payment and settlement

Only two payment paths, all priced in USD

Available gateways are determined by the backend response shown on the payment page. The website will not ask users to complete an order through an unlisted channel.

Digital-asset network

USDT-TRC20

Before submitting, verify the network, address, and order amount. Match on-chain transfer details to the current order and avoid copying an old address or amount from transaction history.

Processed by Stripe

Visa / Mastercard / Amex

Card payments are processed by Stripe. The settlement amount remains displayed in USD; the available gateway and payment steps are determined by the order page.

Which payment methods does MiniRent support?

Only USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe are supported. The backend returns the available gateway at checkout. If someone asks you to use another channel, pause and verify through a console ticket or the support email.

What currency are all orders settled in?

All prices and orders are denominated in USD. Daily, weekly, monthly, and quarterly prices use the dollar sign and are not automatically converted based on language or connection region.

Data and cancellation

Users manage backups; changes start from the order record

A dedicated device is not permanent storage. During the rental period, teams should manage work data, credentials, and export plans, completing necessary backups before service ends.

01

Back up continuously during the rental

Push code to a controlled repository and sync build artifacts, configuration, and critical logs to team-approved storage.

02

Complete exports before the end

Check uncommitted code, certificate copies, dependency-cache requirements, experiment results, and automation configuration. Confirm that no essential data remains solely on the device.

03

Revoke access after recovery

After service ends, device access is revoked and the device enters the data-clearing process. Team keys and temporary tokens used previously should be rotated at the same time.

Who is responsible for backing up code, certificates, and build artifacts on the device?

Users are responsible for organizing, backing up, and exporting work data, including code, configuration, signing materials, keys, model files, build artifacts, and logs. Keep at least one controlled copy separate from the device’s local storage and regularly verify that it can be restored.

Sensitive materials should follow the principle of least privilege and should not be stored unencrypted long-term simply because the device is dedicated. Inject CI tokens per task, sanitize logs before output, and promptly remove temporary files when tasks finish.

What happens to the device after service ends?

At the end of the rental period, access associated with the current order is revoked and the device enters the recovery and data-clearing process. Export your data before service ends; the recovery process is not an extended data-retrieval channel. Teams should also revoke third-party tokens, SSH authorizations, and automation keys used on the device.

How do I change or cancel a billing period?

Sign in to the console, open the relevant order, and review the available change and cancellation options for the current period. Before submitting, confirm the effective time, when device access ends, and any data still awaiting export. If the order status differs from expectations, submit a ticket from that order rather than creating a new order.

Which policies should I read before ordering?

We also recommend reading the Data Protection Notice, Privacy Policy and the Terms of Service. These pages explain access-control recommendations, the scope of personal-data processing, order rules, user responsibilities for data, and the boundaries of device recovery.

Next steps

Create your order after confirming the configuration, location, and billing period

The two Mac Mini M4 options are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West Coast—5 locations in total. Purchases and device management are completed in the console, and all charges are settled in USD.