Every instance is a dedicated physical Mac mini, not a virtual machine. Use it for Xcode cloud builds, automated app packaging, fastlane pipelines, and self-hosted Mac Runners.
xcodebuild archive
destination: arm64
72% · 04:18
M4 PRO
64GB · 2TB
12 / 14 completed
2 jobs active
No vague compute units. Before ordering, verify the chip, memory, storage, region, and fixed rental term; after delivery, view device status and connection details in the console.
Each rental instance is a dedicated Mac mini with an isolated macOS environment. Both the macOS graphical interface and command line are available.
Run Xcode, xcodebuild, fastlane, and CI/CD Runners. Build commands, archive results, and failure logs can all feed into your existing pipeline.
Choose a region based on your development team, code repository, and pipeline entry point to reduce unnecessary cross-region transfer paths.
Review inputs, execution location, and outputs step by step to assess whether your current development tasks fit a cloud Mac.
Ideal for continuous archiving, signing, export, and release delivery. Teams inject repository access and signing materials using least-privilege permissions.
Register the dedicated node with your existing pipeline, assign jobs by repository and task labels, and clean up leftovers when each job ends.
Ideal for local inference, model validation, and developer-tool testing that require larger unified memory. Save results together with runtime parameters.
MiniRents M4 is for lightweight builds and single-project signing; MiniRents M4 Pro is for high-concurrency builds and memory-intensive workloads. All prices are in USD.
Ideal for lightweight iOS builds, single-project signing, dependency checks, and low-concurrency Runners.
Rent MiniRents M4 nowIdeal for high-concurrency builds, large dependency caches, model inference, and workloads requiring 64GB of memory.
Rent MiniRents M4 Pro nowRegion affects code pulls, dependency downloads, remote desktop traffic, and artifact uploads. Prioritize regions near your operators or repository, then validate performance with real builds.
All nodes operate year-round, 365 days a year. Moving between regions is a configuration change; submit the device ID, target region, and desired time range through a console support ticket first.
View regions and configurationsSGIdeal for Southeast Asian teams and regional repositories.
AvailableJPIdeal for development collaboration in Japan and East Asia.
AvailableKRIdeal for local builds and connectivity in South Korea.
AvailableHKIdeal for teams in South China and cross-border development.
AvailableUS-EIdeal for collaboration across the US East Coast and the Atlantic.
AvailableThis comparison covers delivery models and resource boundaries without presenting one option as the universal answer for every team.
| Comparison point | Dedicated physical rental | Purchased hardware | Shared virtual machine |
|---|---|---|---|
| Cost structure | Pay by day, week, month, or quarter based on the selected configuration | Cover procurement, rack space, networking, power, and ownership costs | Typically pay according to shared specifications and usage period |
| Delivery process | Choose the model, term, and region, then order and receive connection details | Handle procurement, shipping, rack installation, networking, and environment setup | Create a virtual instance and configure its software environment |
| Resource exclusivity | Dedicated physical Mac mini, not a virtual machine | The team owns and exclusively uses the device | Underlying physical resources may be shared with other instances |
| Upgrade flexibility | Choose again between the two available configurations for the next term | Re-purchase, replace, or add hardware | Adjust virtual resources, subject to the shared architecture |
| Operations responsibility | The team manages code, credentials, dependencies, and the build environment | The team also manages hardware, networking, and the environment | The team manages the instance environment and task data |
| Best suited for | Time-bound projects, remote teams, build farms, and elastic concurrency | Long-term fixed workloads with local operations capability | General workloads without a need for physical exclusivity |
Every step has defined inputs, an execution location, and outputs. When a job fails, locate logs by job ID and time range instead of searching the entire device blindly.
A repository event triggers the pipeline with the commit ID, branch, and job parameters.
The Runner connects to the designated cloud Mac by label and prepares an isolated working directory.
Install locked dependencies, call xcodebuild, and continuously write build logs.
Inject signing materials with least-privilege access, then archive, validate, and export.
Upload artifacts and redacted logs, then remove temporary credentials and job caches.
Record single-build duration, daily build volume, and peak concurrency first. Start lightweight jobs on MiniRents M4; use MiniRents M4 Pro for high-concurrency or memory-intensive workloads.
Keep the commit ID, job ID, start and end times, exit code, and key error sections. Hide tokens, private keys, and signing materials before submitting a support request.
After artifact upload completes, remove temporary environment variables, download credentials, and unnecessary caches, then verify working-directory permissions and device status.
We support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), with all charges settled in USD. The payment gateway available at checkout is determined by the backend response at that time.
Billing is organized around the rental term, model, region, and selected add-ons. When asking about a bill, provide the order ID, term, region, and add-ons—never submit passwords or private keys.
This example shows billing fields only and does not generate prices outside the directory. The actual total depends on the selected term, model, and add-ons.
The answers below distinguish service facts, configuration guidance, and usage limitations to support a technical evaluation before ordering.
No. Cloud Macs are dedicated physical Mac minis; each rental instance corresponds to one dedicated device with an isolated system environment.
Start with the base tier (M4, 16GB, 256GB). Choose the Pro tier (M4 Pro, 64GB, 2TB) for high-concurrency builds, large-model inference, or workloads requiring more memory.
Yes. A cloud Mac can be registered as a self-hosted Runner. Restrict permissions by repository, use clear job labels, and remove sensitive variables and temporary files after every run.
SSH command-line access is supported. Use VNC remote desktop when you need the macOS graphical interface. Verify the host fingerprint on first connection and safeguard your credentials.
Choose based on your team, repository, and artifact-upload locations, then validate with real repository pulls, dependency installs, and builds. The directory includes Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States.
Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All charges are settled in USD; the available gateway is determined by the backend response at checkout.
Compare the two configurations, four rental terms, and five regions first. Existing customers can sign in to the console to view device status, connection details, billing, and support tickets.