Get clear answers on the device, pricing, and workflow before you rent.
We currently offer one configuration: the dedicated physical Mac Mini M4. Find practical answers below about the device, billing, locations, builds, remote access, and data responsibilities.
Jump by question type
If you already have an order, jump straight to the relevant section for connection or build issues. For host-specific status, sign in to the console for real-time information.
What device does each order include?
Confirm the device type and fixed specifications first, then decide whether the memory, storage, and chip fit your build workload.
Is the Cloud Mac a virtual machine?
No. Each order includes one dedicated physical machine, with its Mac hardware resources reserved for that order. Network egress and upstream links are infrastructure resources, so device dedication does not mean the entire network path is exclusive.
Which Mac configurations are available?
We currently offer only MiniDebug M4: Mac Mini M4, 16GB RAM, and 256GB SSD. No other chip, memory tier, or base storage configuration is available. For more storage, select the +1TB SSD or +2TB SSD add-on when ordering.
What is 16GB RAM / 256GB SSD suitable for?
It suits standard iOS automation builds, Xcode projects, GitHub Actions self-hosted Runners, fastlane release workflows, and Apple Silicon inference validation with controlled memory needs. Large dependency caches, multiple working copies, video assets, and model files consume disk space quickly, so estimate the combined usage of source code, DerivedData, archives, and caches in advance.
How are the four rental terms priced?
The base configuration is billed for the selected term, and all pages and orders use US dollars (USD).
What is the base rental price for MiniDebug M4?
These prices include Mac Mini M4, 16GB RAM, and 256GB SSD. Storage upgrades and Thunderbolt 5 interconnects are not included.
Should I choose a day, week, month, or quarter?
Start with daily billing for short-term troubleshooting, temporary archiving, or a single release. Choose weekly billing for continuous iteration, Runner validation, or a sprint. Monthly or quarterly billing suits a stable CI or long-term development environment. Also consider setup time, dependency-cache reuse, artifact migration, and backup arrangements before the term ends.
Do I need to reconfigure the build environment when renewing?
When the host remains managed by the current order, renewal extends the usage period; it should not be treated as a new environment. The console’s real-time status determines the available actions and final bill. Before submitting, verify the term, add-on quantities, and total in USD.
How do storage upgrades and interconnects work?
Add-ons are charged for the selected rental term and are not separate host tiers. The base device remains MiniDebug M4.
What is +1TB SSD useful for, and how much does it cost?
It is suitable for keeping multiple Xcode versions, large dependency caches, multiple repository working copies, archives, or medium-sized model files. Pricing is $2.7/day, $7.4/week, $13.7/month, $37.3/quarter, and must be selected when ordering.
What is +2TB SSD useful for, and how much does it cost?
It suits large audio/video projects, numerous build artifacts, multiple model versions, or workflows designed to reduce frequent cache cleanup. Pricing is $5.4/day, $14.8/week, $27.4/month, $74.6/quarter, and must be selected when ordering.
What is Thunderbolt 5 interconnect, and how is it billed?
It is for workflows that coordinate multiple devices and require a planned high-speed interconnect. Billing is per device. Pricing is $1.2/day, $3.3/week, $6.1/month, $16.6/quarter. If you need interconnects, choose the quantity during checkout and verify the connection plan and billing details before submitting the order.
Which payment methods are supported?
Orders are settled in USD. The payment gateways actually available are determined by the backend response at checkout.
Which payment channels can I use?
Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All orders are settled in US dollars (USD).
Where can I start a purchase, renew, or view billing?
For a new order, select the model, term, location, and add-ons from the configuration portal. Renewals, billing, and management of existing hosts are handled in the console. The contact page is for inquiries and issue routing; it does not replace order submission or payment.
How should I choose among the five locations?
The current catalog includes Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East, for a total of 5 locations.
Where can I order MiniDebug M4?
The MiniDebug M4 catalog covers Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East. Consider your team’s location, code repository, dependency sources, and final delivery target when choosing a location.
Do I only need to choose the location closest to the developer?
Not necessarily. For frequent graphical remote access, local network quality to the location matters more. For primarily automated builds, also consider the path from the location to your code repository, dependency sources, and artifact destination. Test the connection from the team’s usual network first, then use fetch times in build logs to guide the decision.
How do I confirm location availability when ordering?
Open the configuration portal, select MiniDebug M4, and confirm the available locations from the console’s real-time response. The location catalog and availability at checkout are separate concepts; the console’s real-time response is authoritative.
Are the locations available year-round?
All locations operate normally 365 days a year. For a specific task, check the location status, host online status, remote connection status, and build task status separately rather than relying on a single indicator.
How do I integrate it into an existing iOS build workflow?
The Cloud Mac provides a full macOS graphical interface and command-line environment. Your team remains responsible for project versions, dependencies, signing materials, and task orchestration.
Can I use Xcode and xcodebuild?
Yes. Use Xcode for graphical tasks and xcodebuild for automation. Pin the Xcode version, Scheme, Configuration, SDK, and export parameters, and define them in scripts or CI configuration to prevent differences between local settings and remote jobs.
Which steps is fastlane suitable for?
It can coordinate dependency checks, archiving, export, signing-configuration retrieval, artifact uploads, and result notifications. Split different release targets into separate lanes and define failure exit codes, log directories, and artifact directories. Adjust example commands for the project’s Bundle Identifier, Scheme, paths, and credential-injection method.
Can it serve as a GitHub Actions self-hosted Runner?
Yes. Before registration, plan the Runner labels, repository or organization scope, working directory, and concurrency policy. Clean up temporary files after each job and retain only reusable, non-sensitive cache content. On failure, return the exit code, key logs, and artifact path—not the complete unsanitized environment.
How should signing materials be added to the build workflow?
Apply least-privilege access to signing certificates, provisioning profiles, repository tokens, and upload keys, and never commit passwords directly to the repository. Inject them through controlled variables or temporary files, restrict who can read them, and remove temporary materials when the job ends. Before submitting support logs, remove certificate contents, tokens, private keys, and complete environment variables.
How do I retrieve build artifacts locally or pass them to the next step?
Write archives, export packages, symbol files, and key logs to a fixed directory, then retrieve them through the CI artifact workflow or controlled file transfer. For each job, record the commit identifier, build number, Xcode version, artifact checksum, and output path. Clean up old files only after confirming the download is complete.
How do SSH, VNC, and Screen Sharing differ?
Choose the connection method based on whether the task needs a graphical interface, file transfer, or a long-lived session.
Which tasks should use SSH first?
Prefer SSH for pulling code, running xcodebuild, running fastlane, viewing logs, managing a Runner, and transferring files. It requires less bandwidth and is better suited to scripting. Verify the host fingerprint on first connection, use keys for routine access, and use resumable session management for long-running tasks.
What is the difference between VNC and macOS Screen Sharing?
Both support graphical tasks such as viewing Xcode, adjusting project settings, or checking export results. VNC works well with general-purpose clients or browser-based connection portals; macOS Screen Sharing is suited to native connections initiated from Finder. The best choice depends on your local system, client capabilities, and network restrictions.
What should I change first if the screen stutters on a weak connection?
First lower the image quality and resolution, disable unnecessary animations and live previews, and keep the window size fixed. Switch to SSH for command execution, log viewing, and large file transfers whenever possible. If instability continues, check host status, destination address, port, local network restrictions, client version, and concurrent sessions in that order.
How do I protect credentials during remote access?
Update the host credentials after the first login, prefer SSH keys, do not save passwords on shared devices, and avoid having multiple people share one account long-term. Lock or end the session when leaving, and regularly review authorized members, connection records, and active remote sessions.
What should I handle before the rental term ends?
The user manages source code, certificates, assets, models, caches, and build artifacts during the rental term and should verify them before releasing the host.
What needs to be backed up before the rental term ends?
At minimum, check unpushed source code, archives, symbol files, build logs, assets, model results, CI configuration, and project settings that must be retained. Dependency caches and DerivedData can usually be rebuilt, but if your team relies on specific caches to speed recovery, decide explicitly whether they need to be migrated.
What checks should I perform before releasing the host?
Confirm that artifacts have been retrieved, source code is synchronized, the Runner has been removed or disabled, repository tokens and upload keys have been rotated or revoked, and unnecessary temporary signing materials have been deleted. After release, the host should not be treated as a backup location, so complete the migration beforehand.
Which information must be removed from troubleshooting logs?
Remove login passwords, private keys, complete payment credentials, signing-certificate passwords, repository tokens, upload keys, unsanitized project source code, and complete environment variables. Retain the order identifier, location, time of occurrence, reproduction steps, exit code, relevant log excerpts, expected result, and actual result needed for troubleshooting.
What are MiniDebug’s and the user’s respective responsibilities?
MiniDebug is responsible for infrastructure within the scope of physical nodes, the management portal, and order delivery. The user is responsible for account access, project code, build configuration, credential permissions, data compliance, backups, and migration. When an issue occurs, first distinguish between location status, host connectivity, macOS usage, project code, and external dependencies, then submit the relevant materials.
How do I contact support if the issue remains unresolved?
For existing-order issues, sign in to the console and submit a ticket first so it can be linked to the order and host information. For general inquiries, email support@minidebug.com. Include the location, order identifier, time of occurrence, reproduction steps, and sanitized logs to avoid repeated follow-up.
Once the configuration is confirmed, choose your rental term and location.
MiniDebug M4 is fixed at Mac Mini M4, 16GB RAM, and 256GB SSD. Before ordering, verify the term, location, storage add-ons, and total in USD.