Node delivery record

Rent a dedicated physical Mac mini M4 in Tokyo

Run iOS, macOS, CI/CD, and AI experimentation workflows for East Asia on a cloud Mac built for continuous operation. Each order provides one dedicated physical machine, not a virtual machine; configuration, term, and cost are confirmed before checkout.

Configure a Tokyo node View the complete rental plans

Available configurations: 2 Apple Silicon configurations
Billing cycles: Day, week, month, quarter
Node type: Dedicated physical machine

Catalog combinations available

Tokyo node registration form

MAC · Tokyo

Workload Development, builds, testing, and continuous tasks

Workloads run on the physical Mac assigned to the order. Local compute, memory, and built-in storage are not shared with other tenants.

Coverage East Asia

Average latency reference range

30~60ms

Configuration catalog

SDKMac M4 16GB · 256GB

SDKMac M4 Pro 64GB · 2TB

Delivery stages

Order confirmation01
Node preparation02
Credential generation03
Connection verification04

Operating normally 365 days a year Actual availability is reported in real time by the console

Configuration and term

Choose memory and storage first, then select the rental term

Both plans provide a dedicated physical Mac node. Use daily or weekly billing for short-term compatibility testing, or monthly or quarterly billing for continuous builds and long-term experiments. The total is based on the selected base plan and add-ons, charged in USD.

SDKMac M4

M4 · 16GB RAM · 256GB SSD

Lightweight and standard workloads

$19.3 / day

Suitable for everyday Xcode development, single-repository automation, version checks, remote work, and medium-scale testing. If queue concurrency, persistent processes, or memory usage grows consistently, consider the M4 Pro.

Daily$19.3

Weekly$52.2

Monthly$96.6

Quarterly$262.8

Dedicated M4, 16GB memory, and 256GB built-in SSD
Supports macOS graphical and command-line workflows
A practical starting point for establishing a baseline with small validation tasks

Choose SDKMac M4

SDKMac M4 Pro

M4 Pro · 64GB RAM · 2TB SSD

High-memory and high-concurrency workloads

$60.4 / day

Built for concurrent builds across multiple repositories, large media workloads, long-running experiments, and tasks requiring more persistent memory. The 2TB built-in SSD provides ample local space for caches, artifacts, and media.

Daily$60.4

Weekly$163

Monthly$301.8

Quarterly$820.9

Dedicated M4 Pro, 64GB memory, and 2TB built-in SSD
Ideal for high-concurrency builds and memory-intensive workloads
Handles larger caches, models, and intermediate processing files

Choose SDKMac M4 Pro

Network access facts

Average latency guidance for East Asia: 30~60ms

This figure helps you assess the node region before purchase; it is not a fixed performance guarantee. Actual latency depends on your location, local network, carrier routing, access protocol, interaction frequency, and the location of dependent services. Before deploying a production workflow, run continuous tests from your own office network or Runner environment.

Test the interactive path first

Verify connection setup time, input responsiveness, and session stability separately for remote desktop and SSH. Do not use a single speed test as a substitute for the actual development experience.

Then test dependency paths

Use a small repository to install dependencies, pull code, compile, and upload artifacts. Record the time for each stage and distinguish node compute time from external network dependencies.

Add concurrency last

Establish a single-task baseline first, then gradually add Runners or build tasks. Monitor queues, disk changes, and failure logs so that concurrency congestion is not mistaken for node latency.

Reference metric 30~60ms Average latency reference range for East Asia

Test method Real-world workflow Record connection, dependency, build, and artifact-transfer stages separately

Decision principle Continuous sampling Repeat testing on the network and during the time periods you plan to use

From order to availability

Four steps to deliver a node and complete the first validation

You configure and pay for the order; node preparation and credential generation are recorded by the console. Each step retains the order ID, allowing configuration, connection, or billing discrepancies to be linked directly to the relevant ticket.

01 About 3 minutes

Choose a plan and billing cycle

Select SDKMac M4 or SDKMac M4 Pro based on memory, storage, and concurrency requirements, then choose daily, weekly, monthly, or quarterly billing. Before placing the order, confirm that the chip, memory, and built-in SSD meet your workload requirements.
02 About 2 minutes

Review the order and pay

Check the base plan, term, node, and add-ons, then choose USDT-TRC20 or Visa / Mastercard / Amex via Stripe to settle the order in USD. The console determines the payment result.
03 Displayed in real time by the console

Wait for node preparation

The console records order confirmation, node preparation, and credential generation in sequence. Use the real-time status to determine the estimated duration and availability; there is no need to recreate the same order or change connection settings in advance.
04 About 10 minutes for the first check

Connect and run a validation task

Connect using the delivered host information and credentials. Verify macOS, the chip, memory, storage, and region, then run a small build or test and record duration, disk changes, and network dependencies.

Prepare these three items before ordering

The target toolchain version, expected task concurrency, and local storage required for the project and caches. The more specific the information, the easier it is to make a reliable choice between the two configurations.

Create a cloud Mac order

Pre-purchase questions

Three common questions about Tokyo nodes

These answers focus on node selection, network evaluation, and configuration decisions. After an order is created, the console remains the source of truth for actual availability and delivery status.

When should I prioritize a Tokyo node?

If your team, test targets, or primary dependent services are closer to East Asia, consider Tokyo as a candidate node first. Make the final decision based on continuous connection tests over the network you plan to use, while also validating code pulls, dependency downloads, builds, and artifact uploads.

Will latency from Tokyo to East Asia always remain at 30~60ms?

No. 30~60ms is an average latency reference range before purchase, not a fixed value. Carrier routing, local Wi-Fi, cross-region dependencies, access protocols, and interaction load can all cause variation. Run continuous samples at different times on your team’s actual network.

How should I choose between M4 and M4 Pro on a Tokyo node?

For everyday Xcode development, basic automation, and medium-scale testing, start by evaluating the standard tier (M4, 16GB, 256GB). For high-concurrency builds, memory-intensive experiments, or large media workloads, prioritize the performance tier (M4 Pro, 64GB, 2TB). Both are dedicated physical machines, not virtual machines.

Hand builds and experiments to a continuously operating physical Mac

Choose the right memory and storage from the two configurations, confirm the billing cycle, and create your order. Each order corresponds to a dedicated physical node; delivery status and actual availability are reported in real time by the console.

Rent a cloud Mac now Compare all prices