3 fixed plans

Choose the hardware first, then the rental term

ZoneMini provides three tiers of cloud Mac hosts on dedicated physical machines. Every order includes a fixed processor, memory allocation, and local storage. Hardware resources are not split between tenants, and these are not virtual machines.

Starting at $20.8/day. All daily, weekly, monthly, and quarterly prices shown are original USD amounts, with no conversion or rounding.

3
plans available
5
locations available
4
billing cycles
CORE 01
Light builds

ZoneMini M4 Core

M4 · 16GB · 256GB

$20.8 /day
PLUS 02
Multi-project pipelines

ZoneMini M4 Plus

M4 · 24GB · 512GB

$41.1 /day
PRO 03
High-load parallel work

ZoneMini M4 Pro

M4 Pro · 64GB · 2TB

$61.5 /day
Pricing

Three configurations, four cycles, every price itemized

Choose hardware based on peak memory and local storage needs, then select a billing cycle that matches the project timeline. Every card shows the full price instead of substituting a discount percentage for the amount payable.

Light builds

ZoneMini M4 Core

M4 / 16GB / 256GB

$20.8 /day
  • Daily$20.8/day
  • Weekly$56.1/week
  • Monthly$103.8/month
  • Quarterly$282.3/quarter

Ideal for single-project builds, automated testing, short archive queues, and CI workloads with modest local-cache requirements.

Rent ZoneMini M4 Core
Memory-intensive work

ZoneMini M4 Pro

M4 Pro / 64GB / 2TB

$61.5 /day
  • Daily$61.5/day
  • Weekly$165.9/week
  • Monthly$307.3/month
  • Quarterly$835.9/quarter

Designed for model inference, batch audio and video processing, large-project archiving, and parallel builds that need substantial memory headroom.

Rent ZoneMini M4 Pro
ZoneMini cloud Mac configurations and complete cycle pricing
Plan Processor Memory Local storage Daily Weekly Monthly Quarterly
ZoneMini M4 Core M4 16GB 256GB $20.8/day $56.1/week $103.8/month $282.3/quarter
ZoneMini M4 Plus M4 24GB 512GB $41.1/day $111.1/week $205.7/month $559.5/quarter
ZoneMini M4 Pro M4 Pro 64GB 2TB $61.5/day $165.9/week $307.3/month $835.9/quarter
Choosing hardware

Choose by peak resource demand, not project name

The same iOS project can vary significantly in dependency size, concurrency, caching strategy, and archive frequency. The decision sequence below is more actionable than simply calling a project “light” or “large.”

01
Light builds

ZoneMini M4 Core

Memory
Builds, tests, and dependency installation do not keep memory full at the same time, and the queue is mainly processed sequentially.
Storage
Repositories, DerivedData, dependency caches, and archive outputs can be cleaned regularly within 256GB of local storage.
Duration
Best for short commit-triggered jobs, temporary release validation, or a single fixed runner handling a low-concurrency queue.

Typical outputs: Test reports, single-project archives, and pre-IPA-export checks.

02
Everyday development

ZoneMini M4 Plus

Memory
Keep an IDE, simulator, dependency services, or multiple build processes running together while reducing cleanup between tasks.
Storage
512GB is suited to multiple repositories, CocoaPods or package-manager caches, recent archives, and diagnostic logs.
Duration
Ideal for ongoing weekday development, rotating multi-branch pipelines, and a long-running team CI runner.

Typical outputs: Multi-project test results, signed archives, and iOS build artifacts from cross-platform projects.

03
High-load work

ZoneMini M4 Pro

Memory
Model inference, parallel compilation, or batch workloads need more resident memory, while failed reruns carry a higher time cost.
Storage
2TB of local storage accommodates model files, media, intermediate outputs, and large dependency caches. Long-term archives should still be moved off the working disk.
Duration
Suitable for inference, transcoding, batch testing, or several high-load tasks running in parallel for hours at a time.

Typical outputs: Inference result sets, batch media files, large-project archives, and full performance logs.

Recommended order

Check peaks, then cache, then duration

  1. Record the peak Observe memory usage during one complete build, test, or inference run in your current environment.
  2. Calculate the working set Include repositories, dependency caches, build intermediates, logs, and recent outputs in your local-storage estimate.
  3. Determine concurrency Distinguish sequential single-host tasks from parallel multi-process tasks; do not use average load in place of peak demand.
  4. Match the cycle Once the hardware is set, choose a day, week, month, or quarter based on the actual project boundary.
Add-ons

Expand the working disk or build a faster multi-host workflow

Add-ons use the same billing cycle as the selected plan. Extra SSD storage expands the temporary working set; Thunderbolt 5 linking is billed per host for eligible multi-host workloads.

Check before adding

  • Extra SSD storage expands the working disk and should not be the sole location for long-term archives.
  • Multi-host workloads require a clear split between inputs, execution stages, and artifact aggregation.
  • Thunderbolt 5 linking depends on the selected location and confirmed configuration.
ZoneMini storage and Thunderbolt 5 add-on prices
Add-on Billing unit Daily Weekly Monthly Quarterly
+1TB SSD Per host $2/day $5.5/week $10.1/month $27.5/quarter
+2TB SSD Per host $4/day $11/week $20.2/month $55/quarter
Thunderbolt 5 linking Per host $1.7/day $4.6/week $8.6/month $23.4/quarter
Locations

Three plans across five available locations

All three plans are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East Coast. Prioritize repository location, your team's network path, and the markets where you publish.

5 locations Available year-round, 365 days a year, with no scheduled downtime.
15 combinations All combinations of the three plans and five locations are generally available to order.
Real-time check Availability at configuration time is confirmed by the portal.
ZoneMini plan availability across five locations
Plan Singapore Japan (Tokyo) South Korea (Seoul) Hong Kong US East Coast
ZoneMini M4 Core M4 / 16GB / 256GB Available Available Available Available Available
ZoneMini M4 Plus M4 / 24GB / 512GB Available Available Available Available Available
ZoneMini M4 Pro M4 Pro / 64GB / 2TB Available Available Available Available Available
Repository location

Shorten code and dependency paths first

Builds frequently read from repositories, dependency sources, and artifact services. Choose a location close to that infrastructure rather than looking only at your team's office.

Team network

Then check the remote access path

If you use a graphical interface frequently, test the connection from your actual office network. For automated runners, repository and artifact destinations matter more.

Release market

Consider artifact delivery last

If build results must be uploaded to a team artifact repository or testing system, include that upload path in your location choice instead of comparing login latency alone.

Billing cycles

Match the cycle to the project, not to discount slogans

This page shows the original amounts for all four billing cycles. Monthly prices are not broken down into daily rates, and quarterly prices are not converted into monthly rates. That keeps budget decisions independent of conversion bases and rounding.

DAY

Daily

Best for a single archive, short compatibility checks, build-script migration, or a temporary high-load task. When the finish time is clear, there is no need to reserve a longer cycle.

Check this Can setup, execution, and artifact export finish within the same rental term?
WEEK

Weekly

Useful for release sprints, concentrated fixes, multiple test rounds, and short team collaborations. Dependency caches can be reused across tasks without committing to a longer cycle.

Check this Does the release plan include rework, retesting, and another archive?
MONTH

Monthly

Designed for CI runners, everyday remote development, and multiple release iterations. A fixed environment preserves dependency caches, tool versions, and automation settings.

Check this Will the work reliably span several weeks, and do the caches need to stay in place?
QUARTER

Quarterly

Suitable for product quarters, long-running build-farm hosts, and ongoing model experiments. Confirm that the hardware covers peak workloads throughout the cycle before choosing it.

Check this Has the team assigned permissions, cleanup, backups, and location ownership?
Before ordering

Confirm these six details before creating an order

Configuration mistakes usually come from unclear project boundaries, not too many options. Use this checklist to settle the workload, location, hardware, cycle, connection method, and payment one by one.

Do not submit sensitive data

Pre-sales discussions do not require signing certificates, repository tokens, SSH private keys, or full passwords. When technical assistance is needed, provide only redacted logs and reproducible steps.

  1. 01

    Define the workload

    Specify whether you need iOS builds, a CI runner, cross-platform builds, model inference, or batch audio and video processing, and note whether a GUI is required.

  2. 02

    Choose a location

    Select from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East Coast, then check the paths to your repository, team, and artifact destination.

  3. 03

    Confirm the plan

    Verify the processor, memory, and local storage individually rather than relying on the plan name. Decide on any extra SSD storage at this stage.

  4. 04

    Choose the cycle

    Select a day, week, month, or quarter based on the actual project boundary and budget using the matching listed price, not a self-converted figure.

  5. 05

    Prepare access

    For automation, prepare SSH and runner configuration. For graphical work, check your local network and a compatible screen-sharing tool in advance.

  6. 06

    Confirm payment

    All orders are settled in USD only. Payment supports USDT-TRC20 and Visa / Mastercard / Amex via Stripe.

Ready to order

Enter the portal with a clear configuration

Prepare your plan, location, billing cycle, extra storage, and access method before ordering. For existing orders or technical issues after activation, sign in to the portal to submit a ticket with your order number and redacted logs.