Two full-system options, rented by the day.From $19.2/day.
Run your Xcode build machine in a data center without managing power, networking or cooling yourself. Each rental includes a dedicated physical Mac mini, not a virtual machine. Both configurations are available in all 5 locations. Choose the memory and rental term that fit your workload.
Online 365 days a year. Availability is shown in real time in the console.
For everyday builds of a single app, start with 16GB. Choose 24GB for multiple targets or a mixed tech stack. Changing the term below only updates the displayed prices; it won’t place an order. Confirm your configuration and total when you order.
Prices shown are daily rates in USD.
Keep code checkout, dependency installation and everyday archiving on one dedicated machine. A good starting point for migrating one pipeline and validating your toolchain and cache directories before scaling up.
$19.2/day
Dedicated Mac · SSH / VNC · 5 locations
Rent Push M4 SExtra memory and local storage for parallel archives, Flutter and React Native iOS builds. A good fit for projects with many dependencies or multiple build directories to keep.
$39.7/day
Dedicated Mac · SSH / VNC · 5 locations
Rent Push M4 LPrices below cover the complete machine for each term and exclude optional add-ons. Rent by the day for short-term work, or compare weekly, monthly and quarterly rates to budget for a continuous pipeline—no need to estimate longer terms from the daily price.
| Model and configuration | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| Push M4 SM4 / 16GB / 256GB SSD | $19.2 | $51.8 | $95.9 | $260.8 |
| Push M4 LM4 / 24GB / 512GB SSD | $39.7 | $107.2 | $198.5 | $539.9 |
You rent a physical Mac mini, not a virtual machine on a shared host. Your chosen model includes its chip, unified memory and local storage. The data center handles power, networking and cooling; your team manages project environments, build scripts and access permissions within macOS.
A dedicated machine lets you keep DerivedData, dependency caches and toolchains between builds. You don’t have to clear your entire working directory after every build. Set cache keys by branch or project to reduce repeat downloads and make issues easier to reproduce in the same environment.
Use SSH for scripts and CI, and VNC when you need a graphical desktop to inspect the environment. Both connect to the same machine—they’re not separate products. Find your login details in the console after payment is confirmed and the machine is assigned.
The specs don’t guarantee a particular network bandwidth or build speed. Archive time depends on codebase size, compiler settings, dependency downloads and concurrent workloads. To evaluate performance, time a clean build and a cached build using your own repository.
Both configurations are available in Singapore, Tokyo, Seoul, Hong Kong and the eastern United States. Start with the location of your primary users, then consider where your repositories and build artifacts are stored. Remote desktop responsiveness and pipeline data transfer can depend on different factors.
| Model | Singapore | Tokyo | Seoul | Hong Kong | Eastern United States |
|---|---|---|---|---|---|
| Push M4 S | Available | Available | Available | Available | Available |
| Push M4 L | Available | Available | Available | Available | Available |
Both configurations are available in the same locations, so you don’t need to upgrade just to choose a particular location. Check real-time availability in the console.
If your team uses VNC to troubleshoot UI issues, consider a location near the people doing the work, then test it on your office network. A compatible work timezone can make handoffs easier, but it doesn’t mean the network routes are the same.
Unattended macOS CI runners also depend on repository, dependency source and artifact transfer locations. Distributed teams can use dedicated machines in different locations and assign location labels to runners, so jobs land in the right environment instead of competing for one queue.
Check whether the base SSD can hold your toolchain, projects, dependencies and build artifacts before adding storage. Add-ons are priced separately for each term. For Thunderbolt 5 linking, also check the connection and software requirements for your multi-machine workload.
For workloads nearing the base storage limit that still need room for frequently used dependencies and recent archives. This storage add-on does not change the selected model’s unified memory.
For multiple repositories, several Xcode environments or a large volume of build artifacts. Set a retention policy before adding capacity so old caches don’t fill the extra space indefinitely.
Priced per machine for multi-machine setups that need a linked connection. Connecting multiple machines doesn’t automatically combine their memory or speed up compilation; your tools and scripts still need to distribute the work.
All prices are in USD. Confirm the final combination of machine and add-ons, eligibility and total at checkout.
Both configurations use M4; they differ in unified memory and base SSD capacity. Don’t choose based on lines of code alone. Track peak memory use, disk space, concurrent jobs and the results of a complete archive.
For CI that builds a single app and runs jobs in sequence, start with Push M4 S. Install dependencies, configure signing and run your first archive, then check performance with a warm cache. Include concurrent tests, builds and interactive work in your resource budget—don’t judge by memory use at idle.
If you’re short on disk space but have memory to spare, consider an SSD add-on. More storage does not mean more memory and won’t solve memory pressure.
For parallel archives across multiple targets or mixed Flutter and React Native builds, consider Push M4 L. Its 24GB of unified memory and 512GB base SSD give multi-process workloads and multiple working directories more room, but test concurrency with your actual project.
Pin your toolchain versions and build settings before comparing job times. If dependencies and cache state change between runs, it’s hard to tell whether the difference comes from the configuration or the environment.
Note their main work timezone, whether they use SSH or VNC, and where repositories and artifacts need to move before choosing a location.
Estimate storage for your toolchain, dependencies, DerivedData and archives, and note which jobs need to run concurrently.
Plan temporary evaluation and ongoing CI separately. Back up files you’ll need before migrating; changing models or locations does not automatically migrate your data.
Confirm the model, term, location and add-ons before paying. Once payment is confirmed, the system assigns your machine and shows connection details in the console. Submitting payment doesn’t mean credentials are ready; check your order status for delivery progress.
Pay with USDT-TRC20 or Visa, Mastercard or Amex, processed by Stripe. All payments are in USD. Available payment gateways are confirmed by the backend at checkout.
For USDT-TRC20, follow the network, recipient details and amount shown in your order, and keep your transaction hash. Card details are handled by the payment provider; this site does not store card numbers.
Renew or change your term in the console. Follow the effective date and amount shown on the page. Before changing locations or machines, list the files and environment details you need, then confirm the migration steps.
For payment or delivery issues with an existing order, submit a support ticket in the console with your order number, selected location and current status. Don’t include full card details or your machine password in a ticket.
Two M4 configurations, 5 locations, from $19.2/day. Choose your setup and term, and let the data center host your Xcode build machine.