Two Fixed Plans

Choose the Right Cloud Mac for Your Real Workload

NUMACS offers just two Apple Silicon dedicated physical machines: M4 Core and M4 Plus. Both run without virtualization. Choose based on project size, parallel task count, dependency volume, and local data—not vague “high-spec” labels.

2 Fixed plans available
4 Daily / weekly / monthly / quarterly terms
4 APAC nodes
SELECT / 02

Configuration Decision Runbook

Available in the catalog
01
Project Size

For maintaining and debugging a single app, start by evaluating Core.

02
Parallel Tasks

If simulators, containers, and builds run together, evaluate Plus first.

03
Dependency Volume

Large Pods, package caches, and multiple workspaces continuously consume memory and disk space.

04
Local Data Volume

Count asset libraries, models, archives, and caches toward always-on capacity—not just repository size.

Short-Term Single Project NUMACS M4 Core
More Tasks and Larger Caches NUMACS M4 Plus

Core Specifications

Check the Hardware Before Judging the Experience

Both plans use the same M4 generation chip. The main differences are unified memory, internal storage, and rental price. If your workflow keeps Xcode, simulators, containers, and browser debugging tools open together, the memory difference usually matters more than a single peak build.

NUMACS M4 Core vs. NUMACS M4 Plus: Core Specifications and Term Pricing
Comparison NUMACS M4 Core NUMACS M4 Plus
Processor M4 M4
Unified memory 16GB RAM 24GB RAM
Internal storage 256GB SSD 512GB SSD
Per day $21.7/day $41.6/day
Per week $58.5/week $112.3/week
Per month $108.4/month $207.9/month
Per quarter $294.8/quarter $565.5/quarter
Best for Single-project upkeep, debugging, and short-term builds Continuous integration, multiple workspaces, and larger caches

Build Workloads

Evaluate Tasks on One Timeline

“Can run” and “suited for long-term use” are different conclusions. Record tasks running at the same time instead of checking only whether one archive completes. The four workflows below cover common cases from light upkeep to multi-task builds.

Start with Core

Small-App Upkeep

Ideal for a single repository, stable dependencies, and a few daily commits. A typical flow is pulling code, changing a feature, running unit tests, and creating one archive.

Parallel tasks
1–2 types
Recommended plan
NUMACS M4 Core
Check first
Dependency cache and archive usage
Core First

Everyday Development and Debugging

Suitable for running Xcode, one simulator, a browser, and a few command-line tools together. If you need multiple simulators or containers at once, check memory pressure before deciding whether to upgrade.

Always-on tools
Xcode + Simulator
Recommended plan
NUMACS M4 Core
Upgrade signal
Frequent memory compression or cache cleanup
Plus Is Safer

Continuous Integration Runner

Suitable for a dedicated macOS Runner that repeatedly pulls dependencies, runs tests, archives builds, and exports artifacts. More memory and internal storage leave extra room for build caches and failure logs.

Task profile
Repeated builds and cache reuse
Recommended plan
NUMACS M4 Plus
Check first
Concurrency limits and disk cleanup
Plus First

Multiple Workspaces and Multi-Task Builds

Ideal for team workstations that maintain multiple branches, run simulators and containers, retain large dependency caches, or continue debugging another project during a build.

Parallel tasks
3 or more types
Recommended plan
NUMACS M4 Plus
Check first
Peak memory and local data volume

Memory and Storage

Judge Capacity by Concurrent Usage, Not One Tool

The Xcode project itself is often not the main consumer. Simulator data, container images, derived data, package-manager caches, archives, and asset libraries add up—and determine whether 16GB / 256GB or 24GB / 512GB is right.

MEMORY / STORAGE

Concurrent Usage Checklist

Xcode and indexing

Large workspaces, Swift indexing, and parallel builds continuously consume unified memory.

Memory
Simulators

Multiple OS versions and device images increase memory and disk usage at the same time.

Memory + Storage
Containers and local services

Databases, API services, and image layers compete with build tasks for always-on resources.

Memory + Storage
Dependencies and build caches

Estimate Pods, package caches, DerivedData, and archives at peak usage—not against an empty repository.

Storage
Asset Libraries and Local Models

Reserve space for importing, processing, and exporting audio, video, game assets, and inference models.

Storage
16GB / 256GB

Where Core Fits

Suitable for single-project workflows with controlled concurrency, regular cache cleanup, and project assets stored mainly in an external repository or object storage.

  • Focus on one primary build task at a time
  • Keep only the simulator versions you need
  • Set up DerivedData cleanup rules
  • Export artifacts and configuration before ending the rental
24GB / 512GB

The Practical Value of Plus

Suitable for running simulators, containers, Runners, and multiple workspaces in parallel, or retaining larger local dependency caches, assets, and build history.

  • Reduce the operational cost of frequent cache reclamation
  • Leave headroom for parallel tests and continuous integration
  • Accommodate larger dependency and archive directories
  • Support a stable workspace over longer periods

Term Pricing

Choose the Term by Task Duration, Then Compare Plans

Use daily or weekly terms for short-term validation; monthly or quarterly terms suit stable development environments and continuous integration. Evaluate price differences alongside saved migration, cleanup, and waiting time—without adding decision cost for a third plan that does not exist.

Single-Project Starting Point

NUMACS M4 Core

M4, 16GB RAM, 256GB SSD. Suitable for short-term builds, single-project upkeep, and development workflows with controlled concurrency.

$21.7 /day
M4 16GB RAM 256GB SSD
Per week$58.5
Per month$108.4
Per quarter$294.8
Choose NUMACS M4 Core

All prices are charged in USD. Payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex via Stripe; the gateway available to you is confirmed by the console.

Add-ons

Expand Capacity for Storage Pressure; Link Devices for Collaboration

Additional storage does not increase unified memory, and Thunderbolt 5 linking is not a single-device performance upgrade. Identify whether the bottleneck is capacity, memory, or a multi-device workflow before adding the matching option.

Capacity Expansion +1TB SSD

Suitable for retaining more dependency caches, simulator data, archives, and medium-sized asset libraries. If memory is the main constraint, extra storage alone cannot replace Plus.

Per day
$2.9/day
Per week
$7.9/week
Per month
$14.7/month
Per quarter
$40/quarter
Large-Capacity Expansion +2TB SSD

Suitable for large audio and video assets, game resources, local models, long-term archives, and multi-project caches. Estimate space for input data, working files, and exported results before ordering.

Per day
$5.8/day
Per week
$15.8/week
Per month
$29.4/month
Per quarter
$80/quarter
Device Collaboration Thunderbolt 5 Linking

Suitable for workflows that clearly require multiple physical devices to work together, shared peripherals, or high-speed device-to-device connections. Pricing is per device and should not replace an ordinary network connection.

Per day
$1.8/day
Per week
$4.8/week
Per month
$8.8/month
Per quarter
$23.9/quarter

Node Consistency

Both Plans Cover the Same Four APAC Nodes

NUMACS M4 Core and NUMACS M4 Plus both cover Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. All eight model-and-node combinations in the catalog are marked as available; actual availability when you submit a configuration is returned live by the console.

Four-Node Catalog Status for NUMACS Cloud Mac Plans
Model Singapore Japan (Tokyo) South Korea (Seoul) Hong Kong
NUMACS M4 Core Available Available Available Available
NUMACS M4 Plus Available Available Available Available
SG

Singapore

Suitable for development and delivery workflows serving Southeast Asia.

JP

Japan (Tokyo)

Suitable for remote development connections in Japan and nearby regions.

KR

South Korea (Seoul)

Suitable for workflows connecting to South Korea and Northeast Asia.

HK

Hong Kong

Suitable for everyday connections across teams in Asia.

Final Decision

Choose with Four Verifiable Questions

Do not overprovision for peaks that may never occur, but do not overlook recurring cache cleanup and task waiting. Record your answers in the order below; they usually point directly to Core or Plus.

  1. 01

    How many types of primary tasks will run at the same time?

    One Xcode workspace, one simulator, and basic debugging tools can start with Core. For long-term parallel use of simulators, containers, Runners, and multiple workspaces, choose Plus first.

  2. 02

    How much dependency and build data must stay local?

    Add up the repository, dependencies, DerivedData, simulators, archives, logs, and exported artifacts. Choose Core when 256GB is sufficient with a cleanup strategy; choose Plus or add an SSD when you need more always-on space.

  3. 03

    Is this short-term validation or a long-term workspace?

    For a short-term single project, start with Core on a daily or weekly term. For long-term continuous integration and multi-task workspaces, include cleanup frequency, rebuild time, and concurrency needs in your Plus evaluation.

  4. 04

    Will expansion actually solve the current bottleneck?

    Add a +1TB SSD or +2TB SSD when disk space is insufficient. Compare Core and Plus when memory is under pressure. Choose Thunderbolt 5 linking only when multi-device collaboration is clearly required.

Your Configuration Is Clear—Take It into the Order Flow

Choose a model, a daily / weekly / monthly / quarterly term, one of four APAC nodes, and any necessary add-ons. Manage orders, devices, and support requests centrally in the console.

Charged in USD; supports USDT-TRC20 and Visa / Mastercard / Amex via Stripe.