Keep the error context
Keep commands, tool versions, timestamps, exit statuses, relevant lines before and after the error, and reproduction steps.
Route first, then add the details
Send your request to the right queue and reduce back-and-forth
Send pre-sales and enterprise requests to support@deploymac.com; for existing orders, device issues, and connection problems, sign in to the console and file a ticket first. This form does not upload data; it only prepares the email subject and body locally.
- Public email
- support@deploymac.com
- Order issues
- Console ticket
- How requests are handled
- Impact and completeness of information
Request handoff board
ROUTE / 04
A1
Pre-sales guidance
Use case, region, term, concurrency, memory, and storage
Email
B2
Existing order
Order ID, device configuration, term, and current status
Ticket
C3
Connection issue
Region, time, reproduction steps, and redacted logs
Ticket
D4
Enterprise deployment
Device count, CI queues, permissions, and delivery schedule
Email
Next step
Choose a type first, then submit reproducible details
Four request paths
Choose an issue type first; only fill in the relevant fields
You do not need to email and file a ticket for the same issue. Use the console first for existing orders; use a structured email for pre-sales or enterprise deployment requests.
A1
Pre-sales guidance
You have not ordered yet and need help choosing a configuration, region, term, or SSD upgrade.
Generate consultation email B2 Existing orderYou need to verify the device, term, order status, or confirmed delivery details.
Sign in to the console and file a ticket C3 Connection issueYou can reproduce an issue in the command line, graphical session, network, disk, or build workflow.
Prepare troubleshooting details D4 Enterprise deploymentYour request involves multiple Cloud Macs, a standardized toolchain, CI queues, and role-based access.
Generate requirements emailPre-sales consultation form
Describe the workload, then compare the two configurations
The base tier includes M4, 16GB RAM, and 256GB SSD; the higher tier includes M4 Pro, 64GB RAM, and 2TB SSD. This form prepares information in your browser only and does not upload it.
Technical support materials
Use one reproducible record instead of multiple rounds of questions
For connection, performance, or build issues on an existing order, sign in to the console and file a ticket first so it can be linked to the order and device. Use the form below to prepare the details, then copy them into a ticket or send them by email.
Enterprise planning
Describe queues and permissions before discussing device count
For multiple Cloud Macs, the key considerations are more than quantity: toolchain versions, CI task allocation, access roles, cache boundaries, and delivery batches. Submitting this form generates an editable requirements email.
Pre-submission privacy check
Logs can be complete; credentials must be removed
Support troubleshooting usually needs error context, but never needs secrets that could directly sign in, sign, or restore access.
Replace secret fields
Replace tokens, keys, passphrases, and internal identifiers with clear redacted placeholders.
Limit the data scope
Submit only the smallest log excerpt that demonstrates the issue; do not attach unrelated repository content or user data.
Review attachments
If you copied logs locally, search again for common token, key, and password fields before sending.
Response expectations
Assess impact first, then check whether the evidence is sufficient
Handling priority depends on impact, order association, completeness of reproduction materials, and whether access security is involved. No fixed completion time is promised before review.
Access security or credential risk
Describe the affected device, when it was discovered, isolation steps taken, and whether it is still accessible. Do not submit any actual credentials.
Blocking issues during the current term
This includes connection failures, persistent build failures, disk issues, or unavailable critical tools. Provide the order ID and shortest reproduction steps together.
Performance variation and environment differences
We need to compare the time, region, local network, resource usage, tool versions, and actual task results. A single screenshot is usually not enough.
Pre-sales and enterprise deployment
We’ll first confirm the use case, concurrency, memory, storage, region, and delivery schedule, then recommend a configuration or request missing details.
Order management
Existing customers can continue in the console
Device details, term, order status, and ticket history should be reviewed in the context of the same order. For issues with a current device, open a ticket from the corresponding order to avoid missing the region or configuration.
Billing guidance
Keep payment methods and currency consistent
All orders are billed in USD. Available payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex via Stripe; the console determines the payment gateways currently available.
USDT-TRC20
For billing questions, provide the order ID and payment status shown in the console. Do not send wallet private keys or recovery codes.
Visa / Mastercard / Amex
Card payments are processed by Stripe. Support email does not require your full card number, security code, or other payment credentials.
USD
Plan prices, add-ons, and order confirmations use USD amounts consistently; no currency conversion is performed on the page.
Ready to get started
Place your order when the requirements are clear; send a structured email if you still need help choosing
The two configurations are available across 5 regions: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US East. Actual availability at checkout is returned in real time by the console.