Contact our support team

Get help from the team that can investigate.

Planning to rent a cloud Mac, or need help with an existing order? Email us with plan questions. For connection, billing, or instance issues, sign in to the console and open a ticket so we can check the right service records.

Tell us which model you’re considering, your preferred region, or what’s going wrong. We’ll review the details needed to respond. Resolution time depends on the issue and the scope of our checks; example workflows are not response-time guarantees.

Support guide Choose a channel, then share the details

These are recommendations, not order statuses or response-time estimates.

01
Choosing a planTell us about your project, model, and preferred region
Email
02
Connection issueInclude your order ID and redacted error details
Ticket
03
Billing questionSpecify the order and charge you want us to review
Ticket
04
Data requestDescribe the scope; include your order ID if applicable
Email or ticket
Support email:support@udpmac.com
New inquiry · Email

Prepare an email you can send

The fields below create an email draft on your device only. This page does not receive or store your form entries. You can review and edit the draft in your email app before sending.

Your inquiry

Start here for plan advice or general data requests. For issues or billing questions about an existing order, use a console ticket.

We’ll include this as the reply-to address in your email.
Describe your workflow, what you need us to check, or the error you’re seeing. Don’t include passwords, private keys, or signing certificates.

Existing orders · Console tickets

For help with a specific order, keep the conversation linked to it.

For connection failures, instance access issues, billing checks, or data requests related to an existing service, sign in to the console and open a ticket. Your order details, service management, and ticket updates are all in one account, helping us identify the right instance instead of relying on an email description alone.

After submitting, check ticket status and replies in the console. Investigation and response times depend on the details provided and the scope of our checks. If an issue persists, add updates to the same ticket.

Have these four details ready

  1. 01Order IDCopy the order ID shown in the console and identify the affected instance.
  2. 02When it happenedInclude the time and time zone, and say whether the issue is ongoing or intermittent.
  3. 03Steps and resultsNote how you connected, the steps to reproduce the issue, the expected result, and what actually happened.
  4. 04Redacted logsInclude the relevant error lines after removing tokens, sensitive parts of addresses, and project secrets.
Choosing a plan

Check the catalog first, then discuss your project requirements

The current catalog offers three models across five regions. Confirm current ordering options in the console. Project suitability depends on your dependencies, build workloads, and resource usage.

01 / Models

Start with your workload

UDPMac M4 Start comes with M4 / 16GB / 256GB; UDPMac M4 Build with M4 / 24GB / 512GB; and UDPMac M4 Pro with M4 Pro / 64GB / 2TB. Share your project size, concurrent build count, and artifact storage needs so our team can help you compare options.

View specs and rental terms
02 / Regions

Start with where your team works

Choose from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West. Tell us your team’s time zones, current CI workflow, and preferred deployment region. Don’t assume build performance based on unmeasured latency.

View available regions
03 / Details to check

Compatibility needs verification

For questions about disk capacity, a specific Xcode version, dependency architecture, or CI runner integration, include version numbers, storage requirements, and reproduction steps. Our team will check and get back to you. Availability doesn’t mean your project will build without changes; that needs to be verified.

Read the preparation guide
Before you send

Redact screenshots and logs, but include enough detail to investigate.

Keep error codes, command names, timestamps, and relevant context. Hide access credentials, personal information, signing materials, and project secrets. You can replace usernames and project names in paths, but retain enough directory structure to help locate the issue.

Useful troubleshooting details

  • Connection method, client and OS versions, and redacted error messages.
  • Xcode and dependency tool versions used for the build, plus the steps that failed.
  • Order ID, timestamp, and time zone. Never send account passwords or private keys.
Read our privacy policy
Ready for the next step?

Choose a cloud Mac or tell us what you need help with.

Check the configuration and region before ordering. For an existing order, open a console ticket and include its order ID.