An entire Mac mini, dedicated to one customer. Apple Silicon M4 and M4 Pro, not virtual machines—Xcode and simulators run directly on the physical machine.
For everything from everyday single-app CI to multi-target archiving, choose a model based on memory and working set, then pick a term that fits your workload. Starting at $20.1/day, with no hardware purchase required.
Dedicated machine · 4 locations · Availability confirmed in real time by the console
Change the displayed pricing unit. Confirm the billing term and full configuration when placing your order.
Everyday single-app CI, scripts and standard archiving
$20.1/day
A good way to validate project compatibility before choosing a longer rental term.
Run builds, tests and caches on a node dedicated to your team—no competing with other customers for the same machine. Build times still depend on project size, dependencies and parallelization.
Multiple targets, Unity exports and larger build working sets
$61.5/day
A good way to validate project compatibility before choosing a longer rental term.
Room for multiple simulators, asset imports and archive caches. 64 GB of memory is not a promise of a specific number of concurrent jobs. Check capacity against your own peak build usage and disk footprint.
Prices currently shown per day in US dollars (USD).
The prices below are listed for each billing term. They are not daily rates added up or monthly prices converted into promotional rates.
| Model | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| Glide M4 | $20.1 | $54.4 | $100.7 | $273.9 |
| Cruise M4 Pro | $61.5 | $166 | $307.4 | $836.1 |
The difference between the models is hardware capacity, not exclusivity. Each physical Mac is dedicated to one customer, with full access to the macOS desktop and command line.
When choosing a model, budget for source code, dependencies, DerivedData, simulator runtimes and artifacts you need to keep. If builds frequently trigger memory swapping, consider the 64 GB model first; more SSD storage is no substitute for a memory upgrade.
Add storage or connectivity to your base rental as needed. Add-ons are priced for your selected term, so their cost is not bundled into the model price.
Ideal for DerivedData caches and dependency folders. Check disk usage after a full build before adding space. Keep rebuildable caches separate from your only copy of important files.
Ideal for simulator libraries, Unity export folders and larger build histories. Set retention rules for logs and older artifacts; extra capacity is not a long-term backup service.
Priced per machine for connecting multiple machines in parallel builds. Your team configures task distribution, cache sync and runner scheduling; two machines do not automatically become one.
The configurator shows add-ons available for the selected model and your final price. For multiple nodes, plan your topology and project split first, then configure the connectivity each machine needs.
Example: Glide M4 in Singapore with a +1 TB SSD upgrade. This breakdown shows how the price is composed; it does not mean an order has been placed or paid.
Total$115.0 USD
Base node $100.7 + storage upgrade $14.3
In this example, both the node and SSD are billed monthly. For another term, use the listed price for that term for each item; don’t add a daily add-on rate to a monthly bill.
Once your node is provisioned, check its expiry date and renewal bill in the console. You’ll receive a reminder before expiry, but your team should still assign someone to check the order status. Don’t rely on email reminders as your only renewal plan.
If you don’t renew, the node stops running at expiry and its entire disk is erased. Move source code, certificates, keys and irreplaceable artifacts before then. Caches can be rebuilt; don’t rely on the node to retain your only copy of important data.
Consider budget, provisioning and operational responsibilities together. Dedicated hardware removes resource contention between customers, but it won’t fix slow dependency downloads, serial tests or project configuration issues.
| What to consider | VMFly dedicated Mac rental | Own hardware | Shared virtual machine |
|---|---|---|---|
| Cost | Pay by the day, or choose a week, month or quarter; add-ons priced separately | Upfront hardware purchase, plus power, networking and maintenance costs | Often billed by the minute; jobs may wait in a shared queue |
| Provisioning | Assigned and initialized after payment confirmation; typically ready in about 4 minutes | Requires purchasing, setup, network connection and environment configuration | Jobs can usually be submitted quickly; scheduling determines when they run |
| Exclusivity | Whole machine dedicated to one customer; not a virtual machine | Dedicated hardware; your team manages the system and on-site issues | Host resources shared with other customers |
| Scaling up | Add a higher-spec node, then migrate your project and runner | Buy another machine or rethink your hardware setup | Limited to the platform’s available specs and execution rules |
For a release-week capacity boost, try your workflow by the day first. For regular builds, compare weekly, monthly and quarterly prices. Before migrating, record your Xcode version, dependency lockfiles and runner labels, then benchmark with the same commit for a reproducible comparison.
Singapore, Tokyo, Seoul and Hong Kong—four locations. The table shows which models are listed for sale at each location; check the console for real-time availability.
| Model | Singapore | Japan (Tokyo) | South Korea (Seoul) | Hong Kong |
|---|---|---|---|---|
| Glide M4 | Available | Available | Available | Available |
| Cruise M4 Pro | Available | Available | Available | Available |
If you regularly use remote desktop to debug simulators, choose a location near your team and test the experience on your actual network. Distance is a useful starting point, but it can’t replace a real connection test.
For CI-only workloads, consider the locations of your source repository, dependency sources and artifact destination. Moving between locations requires a new node and a data transfer; the original machine won’t move seamlessly.
We accept USDT-TRC20 and Visa, Mastercard or Amex via Stripe. Available payment gateways are confirmed by the backend; your final total is shown at checkout.
At checkout, verify the network, recipient details and amount due before transferring. Don’t send assets over a different network to the displayed payment address. Use the payment details returned for your order.
If you need to check payment status, keep your order number and transaction hash, then open a support ticket in the signed-in console. Never share your wallet’s private key or recovery phrase.
Card payments are processed by Stripe and charged in US dollars (USD). Complete any verification requested on the payment page, then check the order status. A bank debit notification alone doesn’t confirm that your node has been provisioned.
Physical machine assignment and system setup begin after payment is confirmed. Around 4 minutes to availability is a typical provisioning estimate, not a guaranteed countdown for every network or payment.
Before placing your order, double-check the model, term, location and add-ons. Clicking Pay again won’t speed up confirmation. If the status is unclear, check your existing order first to avoid creating a duplicate.
Plan for your data before changing capacity. For order-specific timing and costs, check the console and confirm through a support ticket.
You can choose Cruise M4 Pro to meet new workload requirements, but it’s a different physical machine—not an online memory upgrade for your current one. Check the new node’s configuration in the console, then migrate your dependencies, keys, caches and runner.
Before switching, stop the existing runner from accepting new jobs and wait for running builds to finish. Once the new node is validated, update your scheduling labels. Contact support through a ticket to confirm how the remaining term and charges on your original order will be handled; don’t assume they’ll be credited automatically.
If you don’t renew, the node stops running at expiry and its entire disk is erased. Daily rentals also require you to save source code, certificates, keys and build artifacts elsewhere before expiry. Don’t use the node’s disk as your only storage location.
Configure your pipeline to upload artifacts to storage your team controls, and test a restore before the rental ends. To keep using the node, check its renewal bill and expiry date in the console ahead of time.
SSD upgrades are priced separately and billed for the term you choose. If you no longer need one, move any data off the extra storage first, then open a console support ticket to confirm when it can be changed and how the bill will be handled. Don’t assume you’ll be refunded for the unused days in your current term.
If the change affects project paths, cache folders or runner working directories, update your configuration and run a build to verify it before removing the upgrade. This helps prevent jobs from writing to the old paths.
If you’re not sure how long you’ll need the node, start with a daily rental. Glide M4 is $20.1/day and Cruise M4 Pro is $61.5/day. Use the same commit to verify compilation, tests, archiving and artifact uploads across a repeatable end-to-end workflow.
For longer-term use, compare the full price list and choose a week, month or quarter. Changing the displayed pricing unit only changes how prices appear on this page; confirm the final term in the order configurator.
From $20.1/day, get a dedicated physical Mac for your pipeline. Review the model, location and add-ons before paying.