DebugMac delivers dedicated Apple Silicon physical nodes—not virtual machines. Only Debug M4 is currently available: Mac Mini M4, 16GB RAM, and 256GB SSD, orderable by the day, week, month, or quarter in five regions.
$19.5/day starting at; actual availability and amount due are shown in real time by the console.
Confirm isolation and resource ownership first, then decide whether it fits your build, automation, or remote graphics workflow.
No. DebugMac provides Cloud Macs that can be used remotely. Each order corresponds to one dedicated Apple Silicon physical node. CPU, memory, base SSD, and macOS runtime environments are not shared between tenants.
Dedicated means the physical node is assigned to one tenant for the duration of the order. Your build processes, caches, working directories, and remote sessions run on that device rather than on virtual resources shared with other tenants.
Typical uses include Xcode command-line archiving, self-hosted CI runners, React Native or native iOS builds, MLX inference experiments, and remote audio or video processing that requires the macOS GUI. Order by the day for short builds, or by the week, month, or quarter for ongoing pipelines.
There are no hidden entry-level or upgraded plans, nor any models outside the catalog. When ordering, choose the term, region, and add-ons for the same Debug M4.
$19.5/day
The device is a Mac Mini M4. Base SSD and additional storage are billed separately; add-ons do not change the model, memory, or base configuration name.
Choose Debug M4Only Debug M4 is currently available, with fixed specifications: Mac Mini M4, M4 chip, 16GB RAM, and 256GB SSD. Additional SSD capacity is not presented as a different host tier, and models outside the catalog are not offered.
You can add +1TB SSD or +2TB SSD when ordering. Add-ons are billed separately for the selected term and shown with the base configuration, region, and total USD amount before you submit the order.
Thunderbolt 5 daisy chaining is billed per device at $1.7/day, $4.6/week, $8.5/month, or $23.1/quarter. Confirm your workflow, device count, and connection requirements before enabling it.
All catalog prices are in USD. Before payment, reconfirm the model, term, region, and add-ons in the console.
Yes. Debug M4 catalog prices are $19.5/day, $52.8/week, $97.7/month, and $265.7/quarter. Each term has its own catalog price; rates are not calculated by simple multiplication, and no unlisted prices are implied.
Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All orders are settled in USD; the payment gateway available at checkout is returned by the backend in real time.
Verify at least five items: the Debug M4 configuration, term, region, additional storage or Thunderbolt 5 daisy-chaining option, and final USD amount due. After payment, use the delivery receipt to check the host address, username, host fingerprint, and access issuance status.
Debug M4 is available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West. All five catalog options are currently listed as available.
A good choice for Southeast Asia and nearby network paths when regional proximity is a priority for build workloads.
AvailableSuitable for teams that need a Tokyo node for builds, testing, or continuous integration.
AvailableA node option for Northeast Asian workflows, with the same delivery configuration as other regions.
AvailableSuitable for remote development, build artifact transfer, and collaboration between South China and Southeast Asia.
AvailableFor West Coast North American workflows, including CI, archiving, and remote graphics processing.
AvailablePrioritize the networks used by operators, code repositories, artifact storage, and collaborators. Interactive remote work depends more on round-trip latency, while batch builds also depend on dependency downloads and artifact return paths. Test actual network performance with a short term before committing to production work.
It means Debug M4 is currently listed for ordering in all five regions above. At checkout, the console returns real-time availability; the static page is not the final confirmation.
You can submit a migration request, but first export the required data and specify the target region, preferred timing, and acceptable cutover method. The support team will provide steps based on the current order, target node, and data volume; migration does not happen automatically.
After delivery, verify the host fingerprint before starting a command-line or graphical session. Keep traceable records of credential rotation and session recovery.
Suitable for repository pulls, dependency installation, automation scripts, xcodebuild, and runner tasks. Always verify the host fingerprint in the delivery receipt before the first connection.
View first-connection stepsSuitable for debugging, settings, and media tasks that require the macOS GUI. A disconnection does not stop a task; check the original session and background processes before reconnecting.
View connection guideAdministrator access is provided within the limits of the order. Before adding keys, rotating credentials, or changing high-risk system settings, record the purpose and retain a recovery path.
View security boundariesThe host fingerprint confirms that you are connecting to the node named in the delivery receipt. If your local record differs from the receipt, stop and check the host address, DNS, or any confirmed node change—do not simply ignore the warning.
The node provides the management capabilities specified by the order. Before making system-level changes, assess their effect on remote access, the build toolchain, and task availability. For high-risk network, account, or security-policy changes, confirm through a console ticket first.
Check your local network and the node address, then establish a secure connection again and inspect the original graphical session. Put command-line tasks in a resumable session manager or CI runner rather than tying their lifecycle to one VNC connection.
Rotate credentials when a team member leaves the project, a key may have been exposed, access roles change, or a long-running project enters a new phase. Add and verify the new credentials first, then revoke the old ones to avoid locking yourself out.
These terms directly affect resource boundaries, access methods, and pipeline design. Use the same definitions before ordering.
Renewal, migration, export, access revocation, and data erasure form one continuous process. Do not wait until the final moment of the term to begin.
Before the term ends, review the next phase of work. If continuing, verify the renewal period and USD amount in the console; if ending, start the export checklist immediately.
Export unpushed code changes, archives, logs, essential cached content, and team handoff records. Verify locally or in team storage that the files can be read.
To change regions, provide the current order ID, target region, data volume, preferred timing, and acceptable cutover method, then wait for confirmation before proceeding.
After the term ends, revoke SSH, VNC, and related team access credentials. Your team should also delete unused copies of keys and automation variables.
After node reclamation, tenant data and access records are handled through the established process. For information categories, retention decisions, and request procedures, see the Privacy Notice and Terms of Service.
If the original order can be renewed, the next term is generally confirmed around the existing configuration. Still verify Debug M4, the current region, add-ons, and USD amount due before submitting, rather than carrying old project needs into a new phase automatically.
At minimum, include unpushed code changes, build archives, release files, key logs, environment notes, and team handoff documents. Caches can usually be rebuilt, but include any non-reproducible intermediate artifacts.
See the Privacy Notice for information categories, processing purposes, and retention and deletion decisions; see the Terms of Service.
Choose Debug M4, a term, and one of the five regions, then confirm add-ons and the final USD amount. For questions about an existing order, sign in to the console and submit a ticket with the order ID and redacted logs.