Configuration & Node Support

Explain the task. Get the next step.

DebugMac handles contact requests only through its support email and console tickets. For pre-sales, include your workflow, region, rental term, and storage needs. For active nodes, submit a console ticket with the order ID, incident time, and sanitized logs.

Rent a Cloud Mac Choose a request type
Support email Pre-sales, enterprise collaboration, and general security matters usually receive a first reply within 1 business day
Console ticket Active nodes, billing, and access issues enter the queue with the order context
REQUEST REVIEW DESK Two contact channels
INTAKE / 01 Request triage checklist
PRE
Pre-sales configuration Workflow, region, rental term, concurrency, and storage
Email
RUN
Active node Order ID, incident time, impact, and logs
Ticket
BIZ
Enterprise collaboration Delivery batches, access roles, audit, and capacity planning
Email
Response scope Available configurations · Node selection · Troubleshooting steps · Next actions
Choose a request type first

Five request types, each with different required details

This page does not submit content to a custom backend. The form organizes an email subject and body in your browser only. Active-node and billing issues go through console tickets so they can be linked to order records.

Pre-sales

Confirm your workflow and configuration requirements

For visitors who have not ordered yet and need to verify whether Xcode builds, self-hosted runners, MLX inference, or audio/video processing are compatible with Debug M4.

Submit pre-sales request →
Active node

Submit troubleshooting details with order context

For connection issues, build failures, storage detection, node sessions, or access credentials. Start with basic network and host fingerprint checks.

Prepare node issue →
Billing & payment

Verify the USD amount and payment status

For order amounts, payment status, renewal records, or gateway responses. Link the relevant order through a console ticket; never send complete payment credentials by email.

Sign in and submit a ticket →
Enterprise collaboration

Describe delivery batches, roles, and capacity plans

For CI teams, multi-node collaboration, and phased delivery assessments. The current catalog offers Debug M4 only and does not promise configurations outside the catalog.

Submit enterprise requirements →
Security

Provide impact and sanitized evidence

Include affected nodes, discovery time, reproduction conditions, and controls already taken. Do not send valid keys, complete credentials, or unsanitized personal information.

Send security email →
Pre-sales request form

Turn your goals into a configuration checklist

The only configuration currently available is Debug M4: Mac Mini M4, 16GB RAM, and 256GB SSD. Nodes are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the western United States. Check the console for real-time availability.

Be specific aboutRepository size, toolchain versions, task duration, and artifact types
ConfirmRental term, region, concurrent tasks, additional storage, and Thunderbolt 5 expansion
First replyUsually confirms available configurations and next steps within 1 business day
PRE-SALES / DEBUG M4

Pre-sales configuration consultation

Email composer
Preferred node region
Expected rental term
Storage and expansion needs

Clicking this button creates a draft in your computer’s default email app; this page does not upload the content. Before sending, check again for keys, passwords, or unsanitized logs.

View plan pricing first

Active node form

Make your ticket ready for troubleshooting

Submit node issues through the console first so the ticket can link the order, region, and current service status. Use the form below to organize a troubleshooting summary; after generating the email, you can also copy it into a console ticket.

RequiredOrder ID, node region, incident time, and impact
RecommendedReproduction steps, command output, host fingerprint verification, and sanitized logs
Do not includeValid private keys, complete passwords, payment credentials, or another person’s personal information
Sign in and submit a ticket
ACTIVE NODE / TRIAGE

Node issue summary

Send to ticket
Node region
Add attachments from your computer after opening the email draft. Before sending, remove keys, passwords, complete addresses, and unrelated personal information.
Open console ticket

Enterprise collaboration

Plan multi-node collaboration by delivery batch

Enterprise consultations confirm how Debug M4 can be delivered for CI, release, and remote collaboration workflows. The current catalog contains only Mac Mini M4, 16GB RAM, and 256GB SSD. Consultations do not promise models, regions, or payment methods outside the catalog.

Delivery batchesState the number of nodes, activation order, and expected duration for each batch
Access rolesSeparate administrators, release engineers, build tasks, and read-only reviewers
Audit requirementsList the operation records, handover records, and internal approval points to retain
Capacity planningProvide daily task volume, peak concurrency, cache size, and artifact retention period
TEAM DELIVERY / REVIEW

Enterprise collaboration review

Email composer

Replies will focus on the existing Debug M4, five node locations, available add-ons, and delivery steps. Catalog-external configurations will not be confirmed by email.

View workflow examples

Payment guidance

Check the order record first, then submit a billing ticket

All orders are settled in USD. The available gateway is determined by the console. Only the following two payment methods are officially supported.

CRYPTO SETTLEMENT

USDT-TRC20

For payment issues, provide the order ID, amount shown in the console, transaction status, and a sanitized transaction ID. Do not send private keys, seed phrases, or complete wallet access credentials.

Settlement currency USD
CARD VIA STRIPE

Visa / Mastercard / Amex

For payment errors, record the order ID, time, on-page error summary, and whether you retried. Do not email the full card number or security code.

Support channel Console ticket
What to include in a billing issue

Order ID, selected rental term and region, USD amount due, payment method, incident time, and status shown in the console. For active orders, submitting a console ticket reduces the time needed to verify order ownership.

Sign in and submit a billing ticket
Before submitting

Include everything once so the reply can go straight to configuration or troubleshooting

Replies cover the currently available Debug M4, catalog availability, node selection, rental term, and next steps. Check real-time availability in the console; orders, renewals, billing, and active-node records are managed there.

  1. 01 Confirm the request type Choose one primary issue: pre-sales, node, billing, enterprise collaboration, or security.
  2. 02 Complete identifying details For pre-sales, include the workflow and region; for active issues, include the order ID, time, and impact.
  3. 03 Remove sensitive content Sanitize logs, screenshots, and command output. Do not send keys, passwords, or complete payment credentials.
  4. 04 Choose the right channel Send pre-sales and enterprise collaboration requests by email; submit active-node and billing issues through a console ticket first.

Configuration confirmed? Go straight to ordering

Debug M4 includes Mac Mini M4, 16GB RAM, and 256GB SSD. Choose nodes in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or the western United States, with daily, weekly, monthly, or quarterly billing.

Rent Debug M4 now Sign in and submit a ticket