Tell us about your project size, build frequency, and team time zone. Email us with pre-sales questions; for an existing machine, submit a ticket through the portal so your request and its history stay in the right place.
Average first-response time: we don’t yet have a figure to share. Email replies stay in the original thread; track ticket progress in the portal. When you submit a request, include your deadline and time zone.
Not sure which setup you need? Use the email builder below to put together a message that’s ready to discuss.
There are two ways to get in touch: support email and portal tickets. We handle three types of requests separately, so there’s no need to send the same information twice.
Not sure whether Base M4 or Trunk M4 Pro is right for you? Tell us your Xcode version, project size, simulator usage, and how often you build—both per build and per day.
Include your team’s time zone and rental period. We can help you compare CPU, unified memory, storage, and remote access options instead of guessing from a project name.
Email us about your setupPlanning to deploy 5 or more machines or set up a Mac cluster? Start with the number of machines, model mix, CI job queue, and target start date.
Let us know whether each machine will run tasks independently or if you need to test across multiple machines. Note any Thunderbolt 5 daisy-chaining requirements separately so they aren’t confused with network communication between nodes.
Discuss your team setupSign in to the portal, open the ticket area, and submit a new request with the machine ID, region, time of the issue, and error output. For an existing ticket, add details there to keep the troubleshooting history together.
If you can’t sign in, email support with details of the login issue and the related order number. Never send passwords, private keys, verification codes, or complete signing credentials.
Sign in to troubleshootFill this in to open your email app, where you can review and send the message. This form does not submit anything to the site or create a ticket. If you’re reporting an issue with a machine you’re signed in to, use the portal instead.
We organize communication around two time zones: Asia-Pacific and US Eastern. These are suggested collaboration hours, not a live availability indicator. Nodes run 365 days a year, and these contact hours do not affect your machine’s availability.
09:00–18:00 UTC+8
A useful window for Asia-Pacific teams to discuss setups and reproduce issues. Give a specific time, such as “14:30 UTC+8,” and tell us which email address to reply to.
09:00–18:00 US Eastern local time
Eastern Standard Time is UTC−5; Eastern Daylight Time is UTC−4. For release deadlines, include the UTC offset rather than just saying EST or “before close of business.”
For email enquiries, check the original thread; for tickets, check the corresponding record in the portal. We don’t currently have an average first-response time to share, and we don’t promise an unconfirmed resolution time. Sending the same request again won’t add troubleshooting details. Add new logs, changes in impact, or deadline updates to the original thread or ticket.
We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All payments are settled in US dollars (USD). Available payment gateways are confirmed by the backend.
Open a portal ticket with your order number, payment time, and payment method. For USDT-TRC20, include the transaction hash. For card payments, include the relevant billing reference and a redacted error message—never send your full card number or security code.
Sign in to the portal, find the relevant order in your billing history, and download the record. If something needs checking, include the billing reference, related order, and specific discrepancy. There’s no need to resend the original payment receipt by email.
First, check the instance expiry date and current billing period. For questions about renewals, additional storage, or Thunderbolt 5 daisy-chaining, include the instance ID. The portal shows the current configuration and payment status.
Keep the machine ID, error excerpt, and reproduction steps together in one record. Haven’t connected yet? Start with our support guide to check SSH, VNC, and your build environment.