Room for larger projects
Consider unified memory and project storage needs—not just the chip name.
- Chip
- M4 Pro
- Unified memory
- 64GB
- Storage
- 2TB SSD
- Access
- VNC · SSH
Choose a term for your build
Two Mac options, four terms—daily, weekly, monthly, or quarterly. Service stops when the term expires.
Develop on Windows or Linux, then use a cloud Mac for macOS builds, signing, and exports. Choose a configuration for your project and a rental term that fits your delivery schedule.
Starting at $19.9/day. Get started and use it the same day. Check the console for real-time availability.
Consider unified memory and project storage needs—not just the chip name.
Compare full-machine pricing
Each price below covers a full billing term, not a prorated daily rate. First, estimate the space your source code, dependencies, build cache, and exported files will need.
M4 / 16GB / 256GB SSD
A good starting point for running Flutter or React Native iOS builds. Consider this option if your workload mainly involves installing dependencies, building a single project, and exporting test builds.
Factor in the initial dependency install and a complete Archive. Include build outputs in your storage estimate; repository size alone is not enough.
M4 Pro / 64GB / 2TB SSD
For projects that need more memory and local workspace, such as large Unity asset bundles, multiple dependency environments, or continuous builds. Whether you need this option depends on your project.
More memory does not guarantee a fixed build speedup. Test dependency installs, asset processing, and exports with your own project before choosing a longer term.
| Compare | XcodeHost M4 | XcodeHost M4 Pro |
|---|---|---|
| Chip | M4 | M4 Pro |
| Unified memory | 16GB | 64GB |
| Built-in storage | 256GB SSD | 2TB SSD |
| Daily | $19.9/day | $59/day |
| Weekly | $53.8/week | $159.4/week |
| Monthly | $99.7/month | $295.1/month |
| Quarterly | $271.2/quarter | $802.7/quarter |
| Hardware allocation | Entire dedicated physical machine | Entire dedicated physical machine |
Match your delivery date
Plan for the initial connection, environment checks, builds, and delivery verification together. Your rental should cover the work—not just the final build.
Plan the first build and follow-up revisions by the week. Check for test feedback before each term ends. Renew if work remains; once delivered, export your files and make a backup.
Plan a month for ongoing debugging, repeated Archives, and signing checks. Ideal for teams producing multiple test builds for a release, without setting up the environment from scratch for every build.
Plan a quarter for a stable build machine. Test your runner, dependencies, and build scripts before extending your use. Your team remains responsible for project secrets and job trigger permissions.
If you only need to test the environment once, start with a daily term. Prices are listed by billing term: don’t treat weekly, monthly, or quarterly prices as daily rates, or rental duration as a promise about build time.
Add only what you need
Add-ons are billed separately and are not included in the full-machine prices above. Check your project’s cache and output sizes before adding storage.
Add space for dependency caches, build directories, and delivery files. A storage upgrade does not change the chip or unified memory of your selected machine.
For projects that need more room for assets or multiple build outputs. Before ordering, distinguish working copies from backups you need to keep long term.
Thunderbolt 5 daisy chaining is priced per machine. Choose it only if your workflow requires it; it’s not necessary for a typical build.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.7 | $7.4 | $13.7 | $37.3 |
| +2TB SSD | $5.4 | $14.8 | $27.4 | $74.6 |
| Thunderbolt 5 daisy chaining (per machine) | $1.3 | $3.6 | $6.7 | $18.2 |
Choose a location for your setup
Available in Singapore, Tokyo, Seoul, Hong Kong, and the US West Coast. Both Mac options are offered at all five locations; see the availability matrix below.
| Model | Singapore | Tokyo | Seoul | Hong Kong | US West Coast |
|---|---|---|---|---|---|
| XcodeHost M4 | Available | Available | Available | Available | Available |
| XcodeHost M4 Pro | Available | Available | Available | Available | Available |
For frequent remote desktop use, consider a location close to the person operating the machine. For SSH builds, also consider the network path for source code, dependencies, and build outputs.
For team workflows, decide who will connect and run builds before choosing a location. Distance is a useful starting point, but your team’s network also affects the experience.
Know what uptime does—and doesn’t—mean
Uptime measures the proportion of time the service is accessible. It does not indicate how fast an Archive completes or how often a build succeeds.
Uptime commitment
Based on a 30-day month, this is about 43 minutes of downtime allowance.All locations operate year-round, 365 days a year. A 30-day month has 43,200 minutes; 0.1% is 43.2 minutes, rounded here to about 43 minutes.
If downtime exceeds the allowance, service time is credited based on the affected duration. Submit a support ticket through the console with your order number, the affected start and end times, and the time zone.
Keep connection errors and relevant task logs to help verify the impact. Don’t include certificate private keys, connection passwords, or complete payment credentials.
Before you pay
Use this six-point checklist to plan your order. It won’t submit a form or save your details. Once you’ve checked everything, continue to configure your order.
Decide whether you need builds, debugging, or CI. For Flutter and React Native, check dependencies and signing; for Unity, consider exported project and asset sizes.
Choose a location close to the person who will connect to the machine. Remote desktop and automated builds have different networking needs, so decide how you’ll mainly work first.
Confirm the selected term and the order’s end date. Allow time for test feedback and rebuilds. Before the term ends, export delivery files, source changes, and any required configuration.
Include dependency folders, build caches, Archives, and exported .ipa files in your storage estimate. Check whether the built-in SSD is enough before adding storage.
Confirm in advance that your developer account, signing certificate, and Provisioning Profile meet your project’s requirements. Check the certificate expiry and app identifier before your final export.
Have USDT-TRC20 or a Visa, Mastercard, or Amex card ready. Before paying, check the machine, term, location, and add-ons, then proceed using the gateway shown at checkout.
Payment and end of use
All orders are billed in USD. Review the machine rental and selected add-ons at checkout. Available payment gateways depend on the response from the backend.
USDT-TRC20 is supported. Pay using the network, recipient details, and amount shown at checkout. Do not use a transfer on a different network to pay for this order.
If we need to verify a payment, include your order number and transaction hash in a support ticket. Never share your wallet’s private key or recovery phrase.
Visa, Mastercard, and Amex are supported through Stripe. We don’t store your card number; follow the payment page prompts to complete verification.
If a payment fails, note the order number and the message shown on the page. Don’t include your full card number, security code, or verification details in a support ticket.
Your machine stops automatically when the rental expires unless you renew. No long-term contract is required for short projects. A stopped machine is not a backup—export any project files, build outputs, and certificates you need before expiry.
Data is deleted after expiry as described in the terms of service. Don’t use an expired rental machine as file storage.
Choose a machine, then check the term, location, and add-ons. Once you’ve confirmed there’s time to export your deliverables before expiry, you’re ready to order.