Compare specs first. Plan your build queue next.

Three Mac tiers.
Pricing that fits your build pace.

Every plan includes a dedicated physical Mac mini, not a virtual machine. All 6 locations are available across daily, weekly, monthly, and quarterly billing. Check live availability in the console.

Rent a Cloud Mac View All Prices

Start at $21.7/day to test your project. Each physical machine is dedicated to one tenant, with full access to the macOS desktop and command line.

Three specs. Four billing periods.

Choose a billing period, then compare specs

Switching periods updates the displayed prices on the three cards; chip, memory, and SSD specs stay the same. The table below always shows all four prices for easy budget comparisons.

Showing daily prices. All prices are in USD.

For a single-app build

XR Build 16

M4 16GB memory 256GB SSD

$21.7/day

Move a single app's Archive and release scripts to a dedicated machine. Run a clean build, then check incremental builds and code signing to confirm your project reliably produces its artifacts.

  • A good starting point for one app with a few builds each day.
  • The 256GB SSD holds source code, dependencies, and build output; remember to clear old archives.
  • Dedicated physical Mac with macOS and Xcode preinstalled; connection credentials are provided.
Rent XR Build 16
Multiple targets & testing

XR Build 24

M4 24GB memory 512GB SSD

$40.8/day

Give your main app, widgets, and extensions more room for memory and caches. Add UI tests to your pipeline, then use your own workload to find the right job order.

  • For projects with multiple targets, many dependencies, or UI tests.
  • The 512GB SSD leaves more room for dependency caches, simulators, and build artifacts.
  • Set concurrency based on peak memory use; avoid launching unlimited jobs.
Rent XR Build 24
Parallel jobs & large caches

XR Build Pro 64

M4 Pro 64GB memory 2TB SSD

$59.5/day

Built for parallel simulator matrices, MLX experiments, and large caches. If builds and experiments share a machine, schedule jobs by priority rather than running everything at full tilt.

  • For memory-intensive workloads and projects that need to retain larger artifacts.
  • 64GB unified memory and a 2TB SSD, with clear specs and no virtual quotas.
  • Set concurrency based on real project benchmarks; memory capacity alone doesn't determine how many jobs to run.
Rent XR Build Pro 64

Full pricing and specs

These are the listed prices for each billing period, not daily equivalents. Before choosing a longer term, make sure your dependencies, signing setup, and build scripts work on the machine.

3 Mac tiers · USD · day / week / month / quarter
Plan Chip / memory / SSD Day Week Month Quarter
XR Build 16 M4 / 16GB / 256GB $21.7 $58.5 $108.3 $294.6
XR Build 24 M4 / 24GB / 512GB $40.8 $110.2 $204.1 $555.2
XR Build Pro 64 M4 Pro / 64GB / 2TB $59.5 $160.5 $297.3 $808.7
Choose by bottleneck, not project name

Use a full build as your baseline

For a single app built a few times daily, start by testing XR Build 16. For multiple targets, widgets, extensions, and UI tests, consider XR Build 24. For parallel simulator matrices, MLX experiments, or large caches, evaluate XR Build Pro 64. These are starting points; your project data should guide the final choice.

  1. 01

    Measure peak memory first

    Run dependency installation, compilation, Archive, and tests separately. Check for sustained memory pressure before deciding whether to add memory or reduce concurrent jobs. Don't judge by idle usage alone.

  2. 02

    Then track disk usage

    Measure source code, dependency caches, DerivedData, simulators, and archives separately. Decide how many artifacts to retain, leave room for temporary build output, then determine whether you need more SSD storage.

  3. 03

    Finally, check for job conflicts

    Start with serial jobs and add concurrency gradually, comparing individual job times with overall throughput. If two jobs write to the same output directory or share a mutable cache, separate the directories and scripts before adding hardware.

A dedicated machine means you don't share physical resources with other tenants. Jobs you start on the same machine still share its chip, memory, and storage.

Check capacity first, then connectivity

Budget separately for caches and retained artifacts

SSD expansion is an add-on and doesn't replace the three base configurations. Thunderbolt 5 linking is priced per machine; it doesn't automatically combine memory or distribute build jobs. Check the order page for the actual configuration and available options.

Add-on list prices · billed in USD · check separately from your base plan
Add-on Day Week Month Quarter
+1TB SSD $2.8 $7.7 $14.2 $38.6
+2TB SSD $5.6 $15.4 $28.4 $77.2
Thunderbolt 5 link (per machine) $1.8 $5 $9.2 $25

More storage isn't a backup

Extra capacity gives you room for more caches and artifacts, but it isn't a substitute for a separate backup. Keep your source code in version control, back up release artifacts and essential signing materials somewhere you control, and test that you can restore them.

Clean up before expanding

Dependency caches can be rebuilt, while release artifacts need a retention policy. Remove unused archives and simulators, then check available disk space after a build. Add capacity only for data you actually need to keep.

All 6 locations, all 3 tiers

Choose a location for your team and a Mac for your workload

All three Mac tiers are available in Singapore, Tokyo, Seoul, Hong Kong, the US East Coast, and the US West Coast. The table shows the current catalog, with all listed combinations available. Check live availability in the console.

3 Mac tiers × 6 locations · all listed combinations available
Plan Singapore Tokyo, Japan Seoul, South Korea Hong Kong US East Coast US West Coast
XR Build 16 Available Available Available Available Available Available
XR Build 24 Available Available Available Available Available Available
XR Build Pro 64 Available Available Available Available Available Available

Lots of interactive work: Start with a location close to your team's network. Test remote desktop responsiveness, source sync, and artifact downloads. Distance is only a starting point; your local network and routing also affect the experience.

Lots of automated builds: Consider the locations of your code repository, dependency mirrors, and artifact destination. Headless jobs don't need constant desktop access, but download retries, connection stability, and log delivery still matter.

Working across time zones: Agree on build triggers and log time zones before choosing a location. Nodes run year-round, so your team's working hours don't determine when they can run.

Review your order before checkout

USD pricing. Pay and renew in the console.

Choose a plan, billing period, location, and add-ons, then check the order total before paying. The billing-period switcher previews prices; your order page shows the final configuration.

Card payments

Visa / Mastercard / Amex are supported and processed by Stripe in USD. Available payment gateways depend on the response from the backend. Before paying, check the order details and amount shown on the payment page.

Don't include payment verification details in support tickets or email attachments.

USDT-TRC20

USDT-TRC20 is supported. Check the network, payment details, and amount shown on the payment page before sending funds. Don't reuse payment details from an earlier order; follow the instructions for the current order.

For payment issues, provide your order number and transaction hash—never your private key.

Renewals and upgrades

Sign in to the console to check your current rental term and arrange a renewal or request an upgrade before it expires. Before changing plans, back up your project and essential files, then follow the steps shown in the console.

Upgrades don't guarantee a seamless migration. Confirm how your data will be handled first.

Keep payment questions separate from build issues

For payment checks, have your order number, billing period, and payment method ready. For build troubleshooting, include the location, Mac plan, Xcode version, and error logs. Current customers can sign in to the console to submit a support ticket. For presales or other questions, email support@xcoderent.com. Never send full connection passwords, private keys, or unredacted signing certificates.

Open Console
From order to your first artifact

Start with a minimal pipeline after delivery

Ordering, assigning a location, and receiving connection credentials are three separate steps. We don't promise a fixed delivery time; check the order and instance status in the console. Example build times aren't delivery estimates.

  1. 01

    Place your order and pay

    Choose a Mac, billing period, and location, then add any extras you need. Check the configuration and total before paying. Keep your order number to check its status in the console.

  2. 02

    Get your machine ready

    Once your order enters the delivery process, a dedicated physical machine is assigned with macOS and Xcode preinstalled. Confirm the toolchain version you need; prepare your project dependencies, build scripts, and project settings for your workload.

  3. 03

    Get your SSH and VNC credentials

    Sign in to the console to view connection details and verify the instance and selected location. Run automated jobs over SSH, use the macOS desktop to check signing and your toolchain, then run a full Archive to verify the resulting artifact.

Keep a record of these four items

Note your Xcode version, dependency lockfile, build command, and output path. Run clean and incremental builds with the same source and signing setup, and save the complete logs. Once you've confirmed the artifacts work, register a self-hosted runner, enable scheduled jobs, or add concurrency.

A dedicated machine won't fix dependency conflicts in your project. If the first build fails, identify whether the issue is network downloads, toolchain versions, signing, or compilation before repeatedly clearing all your caches.

Specs are clear. Now test your project.

Choose a plan and start your Mac

Rent for a day, then run a full build, tests, and an archive. Once you've confirmed you have enough headroom, choose a billing period for your regular build queue.

Rent an iOS Build Mac Already have an account? Open the console