Contact Engineering Support

Clarify the issue first, then use the right support channel.

Whether you are evaluating three Cloud Mac plans, planning bulk CI, migrating a remote development environment, preparing an AI experiment, or troubleshooting an existing physical node, we handle requests based on configuration, region, term, and reproducibility details.

Email support Log in to the console to submit a ticket
Issue routing

Choose an inquiry type and see what information to prepare.

Your selection only changes the preparation checklist on this page. The final contact channel is still support email or a ticket submitted after logging in to the console.

Recommended channel Support email

Tell us your target workflow, concurrent tasks, preferred model, node, and rental term, and we will reply with catalog-based configuration guidance.

Project requirements checklist

Define your workflow and resource requirements clearly.

Email inquiry

Pre-sales reviews do not require extensive background. We mainly check task type, concurrency, peak memory, storage growth, rental term, and connection region. Complete the fields below to generate an email draft addressed to support.

Choose the primary task; add other tasks in the notes.
Enter the number of builds, sessions, or experiments running at the same time.
Base storage is 256GB, 512GB, or 2TB, depending on the selected model.
Used to assess cross-border connection paths, not to expand the nodes available for sale.
View the three plans first

The email subject will include the inquiry type. Add a greeting, your contact time zone, and any necessary background before sending.

Channel guidelines

Which questions should go by email, and which should be submitted as tickets?

Routing requests by whether they are linked to an order reduces back-and-forth and preserves complete context for technical issues.

Support email

You have not ordered yet, or you need a solution reviewed manually.

Good questions to email

  • How to match the three models to build, remote development, or AI workloads
  • How to choose among the five nodes based on team location and working hours
  • Data migration, toolchain reproduction, and term planning
  • USD billing fields, periods, or add-on checks
  • Confirming the scope of bulk CI and project partnerships

Your email should include at least

Target workload, concurrency, model preference, node, term, expected start date, and the questions you want us to answer clearly. Billing inquiries must also include the order ID and payment method.

Email support@hireamac.com
Console ticket

You have an existing order and the issue is linked to a specific physical node.

Good questions for a ticket

  • Graphical desktop or terminal connection issues
  • Node status, session, or system environment issues
  • Failed build jobs with redacted logs available
  • Storage read/write, migration, or data export issues
  • Issues requiring joint review of the order instance and billing records

Your ticket should include at least

Order ID, model, node, time and time zone, impact area, reproduction steps, expected result, actual result, and redacted logs. Do not submit valid access credentials.

Log in to the console to submit a ticket
Self-service resources

Complete verifiable checks before submitting an issue.

You can first check common connection, toolchain, and billing fields using the guides. If the issue persists, include the results in your email or ticket.

Help Center

Find steps for first-time use, connection diagnostics, Xcode and command-line tools, storage operations, and billing fields.

Open the troubleshooting index

Remote access guide

Check node details, access credentials, local network, graphical desktop, terminal sessions, and automated access steps.

Check the connection path

Console tickets

Log in, link the order, submit the issue, and view the status of instances, subscriptions, billing, and existing tickets.

Open the console
How do I add information after the initial response?

Reply in the original email thread or ticket to keep the order ID, node, and issue context connected. For new logs, include the collection time and time zone, and state whether the issue can still be reproduced.

What connection information is needed for node selection?

Provide your team's main work locations, usual time zones, approximate shares of interactive remote desktop and automated tasks, and the region where project data needs to reside. Recommendations are limited to the five nodes available for sale: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US East.

What should be removed from technical logs?

Remove access keys, passwords, session tokens, private repository URLs, signing materials, business data, and information that could identify individuals. Keep error codes, commands, tool versions, exit status, timestamps, and necessary call context.

Get started

If your configuration is clear, proceed directly to checkout.

All three Apple Silicon physical machines are non-virtualized and available for daily, weekly, monthly, or quarterly rental. When ordering, choose a model, one of the five nodes, a term, and any add-ons. Actual availability is shown in real time in the console.

Payment is limited to USDT-TRC20 and Visa / Mastercard / Amex via Stripe. All orders are billed in USD.

Rent a Cloud Mac now Compare the three rental plans