Choose your workload, then your rental term

A cloud Mac built for developers

Every plan includes a dedicated physical Mac mini, not a virtual machine.
Choose from two configurations and rent by the day, week, month or quarter. All prices are in USD.

Base M4 from $20.3/day. Review the included specs and add-on costs, then confirm the full price at checkout.

One Mac, four rental terms

Choose a billing term that fits your work

Rent by the day for a one-off build, or compare weekly, monthly and quarterly rates for ongoing work. Switching terms only changes the displayed prices; it won’t create an order or charge you.

Daily pricing is shown. All four term prices remain listed on each plan card.

For single-app and everyday builds

Base M4

Mac mini M4. Run builds, scripts and everyday development on a dedicated workstation.

ChipM4
Memory16GB RAM
Storage256GB SSD

$20.3/day

Daily
$20.3
Weekly
$54.8
Monthly
$101.5
Quarterly
$276.1

Ideal for getting an archive workflow running, building a single app or moving long-running tasks off your local machine. If simulators, compilation and indexing run together, check memory pressure before increasing concurrency.

Choose from 5 locations:Singapore, Tokyo, Seoul, Hong Kong and the US East Coast. Live availability is shown in the console.

Rent Base M4
For parallel CI and MLX experiments

Trunk M4 Pro

Mac mini M4 Pro. More room for larger projects and memory-intensive workloads.

ChipM4 Pro
Memory64GB RAM
Storage2TB SSD

$60/day

Daily
$60
Weekly
$161.9
Monthly
$299.8
Quarterly
$815.5

Built for large Swift projects, multi-target builds and MLX inference experiments. The 64GB of unified memory is shared by the CPU and GPU, so budget for model weights, context and other running processes too.

Choose from 5 locations:Singapore, Tokyo, Seoul, Hong Kong and the US East Coast. Live availability is shown in the console.

Rent Trunk M4 Pro

The base rental price covers the full setup listed on each card and excludes the add-ons below. Use the page to compare prices; confirm the model, term, location and add-ons at checkout. Your submitted order details are authoritative.

Add only what you need

Storage and multi-Mac connectivity, priced separately

Estimate your source code, dependency caches, simulator images and build artifacts before deciding what to upgrade. Each of the three add-ons has prices for all four terms and is not included in the base rental price.

+1TB SSD

Add storage for dependency caches, multiple Xcode toolchains and archive artifacts. This is an add-on and does not change the base model’s chip or memory.

Daily
$2.6
Weekly
$7.1
Monthly
$13.2
Quarterly
$35.9

+2TB SSD

For workloads that keep more simulator runtimes, model files or build artifacts on disk. Extra storage adds capacity, not unified memory.

Daily
$5.2
Weekly
$14.2
Monthly
$26.4
Quarterly
$71.8

Thunderbolt 5 linking

For direct multi-Mac experiments; priced per machine. Check your model and connectivity requirements first. Linking multiple machines does not combine their memory into a shared pool.

Daily / machine
$1.2
Weekly / machine
$3.1
Monthly / machine
$5.8
Quarterly / machine
$15.8

Before checkout, check the quantity, eligible model and term for each add-on. For multi-Mac experiments, account for both the rental price and connectivity add-on for every machine—not just the linking fee.

Choose a setup based on your workload

Find the bottleneck first

Check memory first, then disk, then concurrency. A single build’s duration won’t tell you how much throughput multiple tasks can deliver. Run your own project rather than relying on someone else’s build benchmarks.

Workload and recommended setup. For choosing a plan only; not a performance guarantee.
Workload Recommended setup What to check first
Light builds, single-app builds Base M4 Run one archive build first and record its duration and memory pressure.
Everyday development, multiple simulators Base M4; add +1TB SSD for larger projects Check whether the constraint is memory or disk. An SSD upgrade does not add RAM.
Parallel multi-target CI, large Swift projects Trunk M4 Pro Give each task its own build directory and check for resource contention under load.
Local LLM inference, MLX experiments Trunk M4 Pro, 64GB unified memory Include model weights, inference caches and system usage in your memory budget.
Multi-Mac distributed experiments Trunk M4 Pro + Thunderbolt 5 linking Check that your framework supports multiple machines and meets the topology requirements before deciding how many to use.

If you don’t have baseline data yet, test the same codebase and toolchain on a short-term plan. Keep build logs, peak memory and disk usage, then choose a longer term. Changing models is no substitute for diagnosing your project.

Compare the two plans

The difference is capacity—not exclusivity

Both plans include a dedicated physical node, with CPU, GPU, memory and storage reserved for you. The table compares the two setups, line by line.

Suggested starting points for testing—not benchmark results or task limits.
Base M4 Trunk M4 Pro
ChipM4 ChipM4 Pro
Unified memory16GB RAM Unified memory64GB RAM
Base storage256GB SSD Base storage2TB SSD
Suggested parallel buildsStart with 1 build task, then add more once you have a baseline. Suggested parallel buildsTest 2 parallel tasks and compare their duration and peak memory with a serial run.
Best suited to project sizeSingle apps, standard builds, everyday development and scripting. Best suited to project sizeLarge Swift projects, multi-target CI and memory-intensive workloads.
Available locationsSingapore, Tokyo, Seoul, Hong Kong and the US East Coast. Available locationsSingapore, Tokyo, Seoul, Hong Kong and the US East Coast.
AccessSSH command line and VNC desktop. Get your credentials from the console after signing in. AccessSSH command line and VNC desktop. Get your credentials from the console after signing in.

Choose a location based on your team’s network route and working hours. For interactive development, consider the desktop connection; for automated builds, also consider access to your code and dependency sources. Live availability is shown in the console.

Check before checkout

USD pricing, two payment options

Pay with USDT-TRC20 or Visa, Mastercard or Amex via Stripe. All charges are in USD. Available payment gateways depend on the backend response; renewals use the same payment method.

Pay with USDT-TRC20

Pay using the network, amount and recipient details shown at checkout. Don’t reuse payment details from an older order. To help verify a payment, keep the transaction hash and order number.

Check payment progress in your console order history. If you have questions about an order’s status, sign in and submit a support ticket with the order number and transaction hash.

Pay by card

Visa, Mastercard and Amex payments are processed by Stripe. Check the order currency and total before completing any verification required at checkout. Never send your full card number by email.

Check billing and order status in the console. If a payment fails, note the error message and order number. Before retrying, check the order history to confirm the outcome of the previous attempt.

Review each item in the final order: model, term, location, add-ons and quantities. Displayed prices are for comparison and don’t replace order confirmation. Before renewing, check the current instance and expiry time to make sure you renew the right machine.

Know what to expect from billing

Four questions to consider before checkout

For service start times, changes and expiry handling, refer to your order and instance records. Don’t assume a machine has been delivered based on a payment receipt alone.

When does a daily rental start?

Daily is a billing term, not a fixed settlement time each calendar day. Check your order and instance details in the console for the service start and expiry times. After paying, confirm the allocation status, then connect using the access details provided at delivery.

If the payment status and instance times don’t match, keep your order number and submit a support ticket. The time you opened checkout isn’t the start of your rental, and neither is the time your build began.

What happens if I don’t renew before expiry?

Don’t assume an expired node will remain available or keep your data. When the rental term ends, the machine enters a reclamation and data-erasure process. Check its status in the console. If you still need it, confirm your renewal in advance—don’t wait until a build is running.

Before expiry, export your source changes, build artifacts, signing materials and any logs you need, then remove the runner registration. Don’t rely on a rented node as your only backup or expect to recover its disk contents after reclamation.

Can I upgrade during my rental?

The two plans use different physical configurations; this isn’t a change to a virtual resource quota. To move from Base M4 to Trunk M4 Pro, submit a support ticket in the console to confirm the process, timing and cost. An immediate upgrade on the same machine or a seamless switch isn’t guaranteed.

Back up your project, build configuration and signing materials before migrating. Once the new node is verified, update your CI configuration. Confirm whether you need a new order and how your current term will be handled before making changes, so the two environments don’t drift out of sync.

Can I cancel an add-on separately?

Don’t infer add-on change or cancellation terms from the prices on this page. Check your order items in the console and submit a support ticket to confirm the available timing, effective term and cost before making a change. Refunds aren’t automatically calculated by the unused time remaining.

Move your data before removing an SSD upgrade. Before changing Thunderbolt 5 linking, stop any tasks that depend on the connection. Afterward, check the next term’s order details to make sure the add-on quantity matches your needs.

Start with a real build

Choose your setup,
and let your next merge trigger a build

Test your project to check build time, memory and disk usage. Base M4 from $20.3/day. Confirm your term and add-ons before placing an order.