Send your request to the right queue

Contact the Cloud Mac team without repeating the context

Configuration choices, availability across five nodes, remote access, order and billing questions, security and privacy concerns, and long-term team requirements can all be sent to one support email. For operational issues linked to an order, sign in to the console and submit a ticket so the team can access the order and node details.

CONTACT ROUTING DPLY-CN-05
Public contact channel support@deploymini.com
Order operations Console ticket
Available nodes Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US West
Who we serve iOS / macOS development, CI/CD, AI experimentation, and batch-processing teams
Both channels are monitored Email is best for consultations; tickets are best for delivered devices
Choose a request type

Select the issue category, then provide the details we need

Clicking a category also updates the email assistant below. Each category highlights different information, but the result is always an email addressed to the support team; nothing is submitted to the website backend.

Structured email assistant

Turn the required fields into a ready-to-send email

After you complete the form, your device’s system email app opens with the subject and message prepared. You review and send the email yourself; the page does not store these fields.

SUPPORT REQUEST SHEET Contact details & request context
MAIL-READY
Used to address you or your team in the reply.
Enter an email address that can receive ongoing updates.
Recommended for delivered devices or billing issues.
The system uses this to generate the email subject.
Choose based on your team, repositories, and artifact pipeline.
Choose days, weeks, months, or quarters based on the task duration.
For technical issues, include the time of occurrence, reproduction steps, client environment, error message, and sanitized logs.
Remove sensitive information before sending

Do not include passwords, private keys, or complete payment credentials. Remove access tokens, connection keys, personal data, and reusable authentication details from logs.

When to email us

Best for configuration comparisons, node selection, rental-term planning, payment questions, security and privacy issues, and team needs before an order is created.

First-response target:Confirm the issue category and the information needed for the next step within one business day.

When to submit a ticket

If a delivered device has a connection outage, build-environment issue, network problem, hardware issue, or order and billing dispute, open a ticket from the corresponding order in the console.

First-response target:Urgent issues affecting active operations are prioritized; verification of the order, node, and event records begins within four hours.

Response & routing

The closer an issue is to active operations, the more important it is to link it to an order

The email queue handles request assessment and information gathering; console tickets support investigation using order, device, and node records. A first response means verification has begun and next steps are provided—it does not mean every issue will be resolved within that timeframe.

QUEUE 01

General consultation & configuration selection

Include the project type, expected concurrent tasks, memory usage, data volume, target node, and rental term. Teams can also provide the device count and expected start date.

Email queue · First response within one business day
QUEUE 02

Connectivity or build failure

Submit a ticket from the relevant order and include the node, time of occurrence, client, error message, reproduction steps, and sanitized logs. First state whether the device remains accessible through another connection method.

Ticket queue · Verification of urgent operational issues begins within four hours
QUEUE 03

Security & privacy incident

Describe when it was discovered, the affected scope, containment steps taken, and evidence that can be shared safely. Do not send usable credentials or unprocessed personal data.

Support email or order-linked ticket · Routed by impact
Payment & settlement policy

Only two payment methods are supported

We support USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All charges are settled in USD; actual gateway availability is shown at checkout. For billing questions, provide the order number and transaction status—never send complete payment credentials.

After contacting us, keep moving with the next step

Still comparing configurations? Review the two plans. Ready for your first deployment? Follow the getting-started checklist. Already have a delivered device? Sign in to the console to view the order and submit a ticket.