Choose your workload, memory, storage, and rental term, then select a Singapore, Tokyo, Seoul, or Hong Kong region. After payment, retrieve your connection details from the console and verify the development environment.
Answer these four questions before choosing a configuration to reduce the time spent reorganizing storage, migrating projects, or changing connection methods after activation.
Decide whether you need Xcode builds, continuous integration, TestFlight distribution, MLX inference, remote creative work, or several tasks running in parallel. Record persistent processes and peak concurrency.
Light builds can start with 16GB RAM and a 256GB SSD. For parallel projects, larger dependency caches, or MLX workloads, prioritize 24GB RAM and a 512GB SSD.
Daily terms suit short tests, weekly terms suit milestone delivery, and monthly or quarterly terms suit ongoing development and builds. The term should cover environment setup, execution, artifact verification, and data migration.
Choose Singapore, Tokyo, Seoul, or Hong Kong, then select a primary access method: graphical interface, SSH, controlled file transfer, or automated tasks.
Both options are Apple Silicon cloud Macs. Each order provides a dedicated physical Mac mini, not a shared virtual machine. Choose by memory first, then verify local storage and add-ons.
Light builds, single-project development, and automation tasks
$52.3 / week · $96.9 / month · $263.6 / quarter
Suitable for a single Xcode project, standard command-line tasks, Fastlane workflow validation, and development work that does not keep large models in memory.
Parallel development, larger caches, and MLX inference
$112.2 / week · $207.7 / month · $564.9 / quarter
Suitable for multiple parallel projects, larger dependency and build caches, large model files, or workloads that require monitoring MLX inference memory usage.
Add-ons are billed separately from the base configuration. Confirm the actual size of projects and artifacts first; do not treat short-term caches as long-term storage requirements.
$2.7 / day · $7.2 / week
$13.4 / month · $36.4 / quarter
Suitable for dependency caches, multiple projects, and medium-sized assets.$5.4 / day · $14.4 / week
$26.8 / month · $72.8 / quarter
Suitable for larger models, asset libraries, or archiving multiple batches of artifacts.$1.8 / day · $4.8 / week
$8.9 / month · $24.2 / quarter
Billed per device; suitable when high-speed connections between devices are specifically required.These times describe normal workflow targets and are not fixed delivery commitments. Availability and order processing results are based on the console's real-time response.
Choose either RentMini M4 16 or RentMini M4 24, then select a daily, weekly, monthly, or quarterly term. Use peak memory needs to choose the configuration and the full task lifecycle to choose the term.
Choose Singapore, Tokyo, Seoul, or Hong Kong, then add +1TB SSD, +2TB SSD, or Thunderbolt 5 device linking as needed.
Check the base term, region, SSD add-ons, and device count line by line. All orders are settled in USD; available payment gateways are determined by the backend response.
After the order is processed, read the device name, regional address, port, username, and credential status from the console. Do not copy complete access credentials into public documents or support screenshots.
The base configuration, rental term, add-ons, and device count determine the amount due. The region appears as an order option and should not be included with add-on storage in the calculation.
First confirm the selected model and term price; second confirm the region; third check the quantities of +1TB SSD, +2TB SSD, or Thunderbolt 5 device linking; finally verify the total due and USD billing indicator.
Visa / Mastercard / Amex are supported and processed by Stripe. Available gateways are determined by the backend response.
USDT-TRC20 is supported. Before submitting, verify the network, amount, and recipient details. Do not include payment credentials in a support request.
Do not start a long-running task before confirming the device, system, storage, and input settings. Complete these six checks first so later troubleshooting has a consistent baseline.
Compare it character by character with the console order record to confirm that you are connected to the dedicated physical Mac mini assigned to the target order.
Record the system version and build number as a baseline for assessing Xcode, command-line tools, and project compatibility.
Check free space on the system volume, confirm that the base SSD and selected expansion match the order, and reserve space for build caches and artifacts.
Adjust the time zone to match the time basis used by team logs and automated tasks so build records and trigger times remain easy to correlate.
Check key mapping in local and remote sessions, especially modifier keys, shortcuts, and input-source switching.
Update credentials as required by the connection details and store access materials in a team-approved secure location, never in the code repository.
Check existing versions first, then install only the tools explicitly required by the project. After each step, record the version, configuration location, and verification command for reproducibility and handoff.
Confirm the required version, target platform, and SDK. Open the project once and resolve dependencies before running a full build.
Verify the compiler, Git, shell, and project-script dependencies. Save version output in the delivery record.
Import only the certificates and configuration files required for the task. Private keys must not enter public repositories, logs, screenshots, or standard support email.
Run read-only checks first, then test builds, log archiving, and artifact output paths. Manage keys separately from project configuration.
Confirm the runtime environment, model format, model-file location, and memory-monitoring method. Verify session-persistence behavior before starting a long-running task.
Use least-privilege repository access, verify pull and push boundaries, and avoid writing access materials into project configuration files.
Team members can continue independently only after remote reconnection, artifact export, recovery steps, and support details have been recorded.
Record the region, time of occurrence, exact error text, local network egress, and checks already performed. Do not submit keys, certificate private keys, or complete access credentials.
View the support checklistConfirm that code, build artifacts, model files, logs, and configuration records have been moved to the team-designated location. Complete data migration before the rental term ends.
View connection and transfer methodsBoth configurations support Singapore, Tokyo, Seoul, and Hong Kong regions. Define your workload first, then configure and pay in USD through the console.