Every plan runs on an Apple Silicon dedicated physical node, not a virtual machine. Prices are billed in USD, with daily, weekly, monthly or quarterly terms for short-term builds, continuous integration, remote development and MLX experiments.
Nodes are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the US West; actual availability is returned in real time by the console.
Use a daily or weekly term for short validation, or compare monthly and quarterly terms for ongoing development. Every plan maintains the same physical resource boundary.
Choose memory and storage for your workload first, then compare the four terms. Plan prices exclude optional storage expansion and Thunderbolt 5 device linking.
Ideal for Xcode project validation, remote macOS development, single-pipeline builds and routine automation.
If your work mainly involves code editing, dependency installation, single builds and artifact exports, start by evaluating this plan.
Rent Oak M4Ideal for dependency-heavy projects, fastlane pipelines, multiple development tools running in parallel and continuous artifact delivery.
When you need more dependency cache space and want Xcode and automation tools open together, this plan provides more memory and local storage.
Rent Oak M4 PlusIdeal for large projects, memory-intensive MLX experiments, larger model files and multi-stage builds.
When models, caches, project files and build artifacts must remain available at once, size this plan against peak memory and disk usage.
Rent Oak M4 ProAll three plans use Mac Mini physical devices. Prioritize peak memory and project usage, then account for local storage for caches, models and artifacts.
| Specification | Oak M4 | Oak M4 Plus | Oak M4 Pro |
|---|---|---|---|
| Device | Mac Mini | Mac Mini | Mac Mini |
| Chip | M4 | M4 | M4 Pro |
| Memory | 16GB RAM | 24GB RAM | 64GB RAM |
| Built-in storage | 256GB SSD | 512GB SSD | 2TB SSD |
| Resource boundary | Dedicated physical server | Dedicated physical server | Dedicated physical server |
| Catalog nodes | Available in all five locations | Available in all five locations | Available in all five locations |
If caches, model files and build artifacts will grow together, reserve space for peak workload usage rather than sizing only from the repository's initial size.
Add-ons use the same term as the main plan. Storage expansion suits workloads with larger caches, models and artifacts; device-linking is billed per device.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.3 | $6.1 | $11.3 | $30.7 |
| +2TB SSD | $4.6 | $12.2 | $22.6 | $61.4 |
| Thunderbolt 5 device linking (per device) | $1.1 | $2.9 | $5.4 | $14.7 |
List the project repository, dependency cache, archives, model files, experiment logs and pending artifacts together, then decide whether to add a 1TB or 2TB SSD.
Thunderbolt 5 device linking is billed per device. Before ordering, confirm the number of devices involved, the data handoff method and your team's actual need for a linked setup.
Choose a physical node based on team time zones, access location and project data boundaries. The listed combinations are normally orderable; the console returns real-time availability.
| Plan | Singapore | Japan (Tokyo) | South Korea (Seoul) | Hong Kong | US West |
|---|---|---|---|---|---|
| Oak M4 | Ample | Ample | Ample | Ample | Ample |
| Oak M4 Plus | Ample | Ample | Ample | Ample | Ample |
| Oak M4 Pro | Ample | Ample | Ample | Ample | Ample |
Remote development usually involves fixed team members connecting continuously. Prefer a node closer to the primary operator, then test SSH and graphical access before running production work.
If the workflow includes human review, signing preparation or artifact downloads, consider the node together with team coverage hours rather than using one member's location alone.
Projects may have different requirements for where code, logs, models and build artifacts are handled. Confirm the applicable boundaries with your team and choose the corresponding node before ordering.
Use this checklist to reduce configuration rework. Every item should have a clear answer using numbers, a node name or connection requirements rather than a guess based on the task name.
Specify whether you need Xcode builds, fastlane automation, remote development or MLX experiments, and list the main tools that must run together.
Choose a target location from the five available nodes based on primary access location, team time zone and project data boundaries.
Confirm whether the workload runs daily, weekly, monthly or quarterly, and verify that the main plan and add-ons use the same billing term.
Choose 16GB, 24GB or 64GB of memory and the required storage based on peak memory, dependency caches, model files and artifact size.
Prepare a local SSH client, a working key and a stable network, and confirm that your team can securely store the host fingerprint and connection details.
Choose USDT-TRC20, or use a Visa, Mastercard or Amex processed by Stripe, and confirm settlement in USD.
The marketing site displays the catalog and pricing only; it does not collect complete payment details. Available gateways are returned by the console.
Complete payment at checkout using the details provided by the console, and verify the network, amount and order identifier before submitting. All plans remain priced and settled in USD.
Card payments are processed by Stripe. Complete payment inside the console; the marketing page will not ask for complete card credentials or other sensitive payment data.
Before submitting, recheck the plan, node, term and add-ons. View status, renew and manage the service in the console after ordering.
Choose one of the three plans, review add-ons and the USD total, then pay with USDT-TRC20 or a Visa, Mastercard or Amex processed by Stripe. Manage orders, renewals and services in the console.