Dedicated physical Mac mini, not a virtual machine. Cloud Mac rental starts at $21.1/day. Choose a configuration based on a real build, then decide how long to keep the machine.
Switch the headline price shown on the plan cards
Daily prices are shown; full pricing for all 4 billing options is always available.
All prices are in USD. Models, locations and current availability are confirmed in the console.
All 3 models provide a dedicated physical environment. They differ in unified memory and SSD capacity. Build count alone does not determine the right configuration: check resource use for a single archive first, then account for overlapping jobs.
$21.1/day
A good fit for getting an iOS build pipeline running or moving one project’s archive job off your local machine. Start with sequential jobs to establish build-time and disk-usage baselines.
Include DerivedData, archives and dependency caches in your 256GB storage budget.
Rent M4 Base$41.4/day
A good fit for teams that need more room for dependency caches, multiple schemes or simulator runtimes. 24GB of unified memory and a 512GB SSD provide more headroom for everyday builds.
Check the workload on one runner before adding concurrent jobs to the same machine.
Rent M4 Plus$59.5/day
A good fit for large projects, multiple toolchains and workloads that include local model inference testing alongside builds. 64GB of unified memory and a 2TB SSD accommodate larger jobs and caches.
Before running multiple jobs on one machine, track peak memory use and disk writes for each.
Rent M4 ProSwitching the displayed price does not place an order. Selecting a model preselects its configuration; confirm the billing option and add-ons at checkout.
These configurations are listed for straightforward procurement checks. All 3 are Apple Silicon physical nodes with full macOS GUI and command-line access; Xcode, simulators and Metal run natively.
| Item | ArmRDP M4 Base | ArmRDP M4 Plus | ArmRDP M4 Pro |
|---|---|---|---|
| Chip | M4 | M4 | M4 Pro |
| Unified memory | 16GB | 24GB | 64GB |
| Built-in SSD | 256GB | 512GB | 2TB |
| Resource allocation | Entire dedicated physical machine | Entire dedicated physical machine | Entire dedicated physical machine |
| Daily | $21.1 | $41.4 | $59.5 |
| Weekly | $57.1 | $111.9 | $160.7 |
| Monthly | $105.7 | $207.2 | $297.6 |
| Quarterly | $287.5 | $563.6 | $809.5 |
If your project depends on specific CPU/GPU core counts, network settings or an OS version, send your requirements to support@armrdp.comand confirm them before choosing a rental term.
The base SSD is included in the model rental price. The following add-ons are priced separately across all 4 billing options. For a complete quote, list the base model, each add-on and its billing option rather than comparing machine prices alone.
Add space for dependency caches, DerivedData or archives. Before migrating, confirm the mount location and use an explicit path in your build scripts.
Storage upgrades do not increase unified memory.
For workloads that need to retain multiple archives, project caches or larger test datasets. Set cache cleanup and artifact retention rules before expanding storage.
Extra storage is not a backup; store important artifacts separately.
Priced per participating machine. For a multi-machine setup, specify the number of machines, data flow and target jobs. Confirm the connection design before adding it to your quote.
An interconnect does not combine multiple machines into one pool of unified memory.
To add an upgrade mid-term, check the relevant order, add-on term and amount due in the console before confirming. Don’t use full-term list prices to estimate the cost for the remaining rental period.
Choose Singapore, Tokyo, Seoul, Hong Kong or the US West Coast. Start with the location nearest your team or dependency services, then test download, archive and upload times using a real repository.
| Model | Singapore | Japan (Tokyo) | South Korea (Seoul) | Hong Kong | US West Coast |
|---|---|---|---|---|---|
| ArmRDP M4 Base | Available | Available | Available | Available | Available |
| ArmRDP M4 Plus | Available | Available | Available | Available | Available |
| ArmRDP M4 Pro | Available | Available | Available | Available | Available |
Evaluate interactive use and builds separately.VNC responsiveness depends more on round-trip latency. Automated builds also depend on your repository, dependency sources and artifact destination. Location can help narrow your options, but it can’t replace testing your project.
Keep your setup reproducible before migrating.Record runner labels, toolchain versions, environment variables and cache settings. When switching locations, validate the new environment before changing job routing in your pipeline.
For example, an ArmRDP M4 Plus in Tokyo with an additional +1TB SSD. Both items are billed weekly, for a sample total of $119.9 USD. This shows how the total is made up; it is not a payment request.
The base model and storage upgrade use the same billing option.
$111.9 + $8 = $119.9
This example excludes any unselected add-ons. For an actual order, check the model, location, billing option, add-ons and total individually.
Choose a billing option based on how long you need to keep the machine, not how fast it builds. The examples below use list prices; refer to your order for the actual rental period.
Run a clean build, a cached build and a signed export. Record build time, peak memory and SSD usage before deciding whether to keep the same environment.
Example: M4 Base
$21.1/dayFor a short test, define the task scope first. A single successful run doesn’t measure concurrent capacity.
When a release cycle involves repeated fixes, regression tests and rebuilds, keeping the toolchain and caches in place can make issues easier to reproduce than reconfiguring each time.
Example: M4 Plus
$111.9/weekTwo consecutive weekly payments cost more than a monthly plan at $207.2. Check your full release schedule before renting.
A good fit for everyday CI and a stable long-term release environment. Validate the configuration with real jobs before extending the rental term; a longer term won’t fix an unsuitable resource choice.
Example: M4 Pro
$297.6/month · $809.5/quarterAt list prices, the difference between quarterly billing and three monthly payments is $297.6 × 3 − $809.5 = $83.3.
If individual jobs slow down after you add concurrency, check memory pressure, disk contention and cache conflicts first. To isolate release jobs, assign multiple runners to separate physical nodes instead of only increasing concurrency on one machine.
All orders are billed in USD. We accept USDT-TRC20 and Visa, Mastercard or Amex via Stripe. Available payment gateways are confirmed by the backend at checkout.
When you reach the payment step, follow the network, address and amount shown for your current order. Confirm you’re using TRC20 before sending, and save the transaction ID to help verify the payment.
Check the order receipt in the console for payment status; initiating a transfer does not confirm payment.
Card payments are processed by Stripe. Check the order total and currency, complete verification, then return to the console to check the payment status. If it hasn’t updated, check the original order record first.
Don’t create another order while a payment is still being verified.
Check the expiry time, outstanding invoices and renewal options in the console. Whether auto-renewal is enabled, and the available reminder channels and times, depend on what’s shown for your order and account. A reminder does not mean renewal is complete.
Before expiry, export your code, certificate backups and build artifacts, and confirm the service end date after renewal.
To check a payment or invoice, sign in to the console and submit a support ticket with your order number, amount and transaction ID. Never send full card details, private keys or machine passwords in a ticket or email.
Start by choosing a model, location and billing option. Track build times and resource use on a real project, then decide how long to keep it and whether to add more nodes.