Fixed configuration, flexible rental periods

One Cloud Mac plan with clear pricing and resource limits

VMMini currently offers one Apple Silicon dedicated physical server configuration: VMMini M4. It is built for MLX inference, Mac AI deployment, iOS/macOS build pipelines, and automation that needs to stay online year-round.

Each order provides a dedicated physical node. CPU, memory, and local storage are never shared with other tenants, and this is not a virtual machine. Choose from Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong; actual availability is returned in real time by the console.

1 plan
Fixed configuration
4 options
Rental periods
4
Available nodes
Physical node run Available to order
Configuration ID m4-16-256
Host
Mac Mini M4
Memory
16GB RAM
Local storage
256GB SSD
Resource type
Dedicated physical server
SG JP KR HK
Starting period $20.5/day
Only configuration available

VMMini M4 pricing by rental period

The hardware specification stays the same across all periods. Choose daily, weekly, monthly, or quarterly billing based on the task duration, then select a node and add-ons instead of forcing short experiments and long-running pipelines into the same billing model.

Available across all four nodes

VMMini M4

Mac Mini M4 · 16GB RAM · 256GB SSD

  • One dedicated physical server per order
  • macOS GUI and command line available
  • Suitable for MLX, builds, testing, and remote automation
  • Runs continuously 365 days a year
Daily $20.5 Best for validation and short tasks
Weekly $55.4 Best for sprints and concentrated builds
Monthly $102.6 Best for stable pipelines
Quarterly $279.1 Best for continuous project cycles

All amounts are shown and billed in USD. Additional storage and Thunderbolt 5 parallel-link charges are added separately for the same selected period.

Choose VMMini M4
Choose a period

Match the period to the task—no guessing costs from discount rates

The billing period determines the base charge and add-on pricing tier without changing the host specification. Use task boundaries, delivery cadence, and your exit plan to decide; no currency conversion is applied.

VMMini M4 pricing and recommended workloads by period
Period Base price Best for Confirm before ordering
Daily $20.5/day MLX model compatibility checks, build-script troubleshooting, and one-off automation Can the data be exported before the task ends, and can the environment be reproduced by script?
Weekly $55.4/week Release sprints, short-term contract collaboration, concentrated regression testing, and build peaks Code-freeze timing, artifact archive location, and runner removal steps
Monthly $102.6/month Continuous integration, long-term MLX service validation, and shared team automation runners Log retention, cache cleanup, key rotation, and capacity growth trends
Quarterly $279.1/quarter Cross-version projects, continuous release plans, and experiments requiring a stable physical node Quarterly capacity budget, owner, and final data export plan
Scale capacity

Add-ons are billed independently for the selected period

The base plan always includes a 256GB SSD. Add expansion only when the working set, model files, build caches, or parallel tasks genuinely require it, rather than leaving exportable artifacts on the node long-term.

Storage expansion

+1TB SSD

Ideal for model weights, build caches, and retaining medium-sized artifacts.

Daily
$2.4
Weekly
$6.4
Monthly
$11.8
Quarterly
$32.1
Storage expansion

+2TB SSD

Ideal for large model collections, multi-project caches, and longer artifact-retention periods.

Daily
$4.8
Weekly
$12.8
Monthly
$23.6
Quarterly
$64.2
Billed per host

Thunderbolt 5 parallel link

For workloads that require multiple hosts to work together with a clearly defined physical connection topology.

Daily
$1.3
Weekly
$3.4
Monthly
$6.3
Quarterly
$17.1

Thunderbolt 5 parallel linking is billed per participating host. Before ordering, confirm the number of hosts, connection method, and data-distribution strategy your task requires.

Understand the bill at a glance

How the base period, node, and add-ons determine the total

Here is a monthly example run order: VMMini M4, Hong Kong node, +1TB SSD, and one Thunderbolt 5 parallel link. The node is a deployment choice and adds no separate node fee in this example.

USD sample bill

Monthly run order

M4 / HK
VMMini M4 monthly base period
$102.6
Selected node: Hong Kong
Included
+1TB SSD monthly add-on
$11.8
Thunderbolt 5 parallel link × 1 host
$6.3
Sample order total $120.7 USD
A

The base period starts the bill

After selecting daily, weekly, monthly, or quarterly billing, VMMini M4 and all add-ons use the catalog price for that period.

B

The node is recorded for deployment

Singapore, Tokyo, Seoul, or Hong Kong is recorded in the order and delivery details to identify the physical node location.

C

Add-ons are totaled item by item

SSD expansion is charged once for the selected capacity; Thunderbolt 5 parallel linking is charged by the number of participating hosts.

Before submitting an order

Six checks to reduce rework after creation

Turn your use case, network path, capacity, and exit plan into verifiable requirements before opening the configurator. Each item should have a clear owner or validation method.

The use case is clear

Specify whether this is for MLX inference, Mac AI deployment, continuous integration, automation, or a combination, and define the completion criteria.

The node is selected

Choose one of the four nodes based on team location, code-source location, end-user network path, and actual network testing.

The period covers the full task

Include environment setup, production runs, contingency time, artifact export, and cleanup in the selected period.

Storage add-ons are verified

Separate source code, dependency caches, model weights, logs, and artifacts. Confirm whether 256GB is enough and which data can be moved off the node.

Connection details are ready

Prepare an SSH public key, permitted source ranges, and the email address for order information. Never submit a password or private key.

Data export is planned

Define the artifact archive location, log-retention scope, runner removal steps, and ownership for node cleanup after the task ends.

Four-node catalog

VMMini M4 can be ordered in all four nodes

Every combination in the catalog is marked “Available.” Choose a node based on your team, code source, and service access path—not just geographic distance. The console returns actual availability in real time.

VMMini M4 four-node availability matrix
Configuration Singapore Japan (Tokyo) South Korea (Seoul) Hong Kong
VMMini M4
M4 · 16GB · 256GB
Available Available Available Available
USD billing

Order, payment, and ongoing management

Payment supports USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. All plans and add-ons are shown and billed in USD; the checkout interface determines the payment gateway currently available.

When buying, open the configurator to select VMMini M4, a period, node, and add-ons. Check expiration details, billing, and support requests for existing orders in the console.

01

Confirm the run order

Review the configuration, period, node, SSD expansion, and parallel-link quantity.

02

Complete USD payment

Complete payment using one of the two payment methods currently offered in checkout.

03

Receive and manage the order

Verify the node, period, delivery details, and subsequent billing records in the console.

Plan FAQ

The resource and billing boundaries most often checked before ordering

For questions about an existing order, node events, or billing records, sign in to the console to submit a ticket with the order ID and sanitized troubleshooting details.

Is VMMini M4 a dedicated physical node?

Yes. Each order provides one dedicated Mac Mini M4 physical server. Its CPU, 16GB memory, and 256GB local SSD are not shared with other tenants. Select additional SSD and Thunderbolt 5 parallel linking based on the actual task when creating the order.

Is this a virtual machine plan?

No. VMMini provides Cloud Mac physical nodes rather than presenting shared compute instances as dedicated resources. You receive usage rights to a fixed-spec physical host; still follow least-privilege practices when managing code, keys, and runtime logs.

How should I choose between daily, weekly, monthly, and quarterly billing?

Daily suits compatibility checks and one-off tasks; weekly suits release sprints and concentrated testing; monthly suits continuous integration and stable experiments; quarterly suits cross-version projects. Choose a period that covers environment setup, production runs, artifact export, and cleanup.

How is additional storage billed?

+1TB SSD and +2TB SSD each use separate daily, weekly, monthly, and quarterly catalog prices, matching the base plan’s selected period. Estimate peak capacity for model weights, dependency caches, logs, and build artifacts before ordering so exportable files do not occupy local space long-term.

Can I switch nodes directly after ordering?

Node location is not a setting that can be switched freely at any time. It is part of the order and physical delivery details. To change location, submit a ticket in the console to review the current order, data export, and new-node arrangements, then create the appropriate configuration based on the outcome.

How should I choose among the four nodes?

Consider team location, code-source location, dependency download paths, and end-user access at the same time. Singapore suits Southeast Asian network paths; Japan (Tokyo) and South Korea (Seoul) suit Northeast Asian teams; Hong Kong suits South China and Southeast Asia routes. Base the final decision on actual network testing.

Prepare to create a run order

Choose the period, node, and add-ons, then launch VMMini M4

Choose daily, weekly, monthly, or quarterly billing for the task. All orders are billed in USD. If you are still evaluating connectivity or data migration, read the deployment steps first.