Developer Support

Questions? Get in touch.

Before ordering, email us. For an existing order, sign in to the portal and open a support ticket.

No need to describe your whole project. Tell us what you need to build and where you’re getting stuck.

Planning a build?

Tell us what you need

Ask us about plans, regions or rental periods. The form below prepares an email; it does not send anything to the website.

Three details to include

Tell us which framework you use, how many days you expect to need the Mac, and where you’ll connect from. If you’re unsure which region to choose, select “Help me choose” and tell us where you usually connect from.

Choose a Mac
XcodeHost M4 comes with M4 / 16GB / 256GB SSD; the Pro tier comes with M4 Pro / 64GB / 2TB SSD. Details about your project size, build process and disk space needs are more useful than the framework name alone.
Choose a rental period
Prepay by the day, week, month or quarter. Your estimated number of days helps us advise you; it does not place an order. Confirm the rental period and end date when you order.
Choose a region
Interactive desktop sessions depend more on your connection. For SSH builds, consider both project uploads and downloading build artifacts. Check the portal for current region availability.
Pre-sales email support@xcodehost.com

You can also email us directly. Never include connection passwords, private keys, signing certificates or complete customer source code.

Project type Required
Enter a whole number greater than 0. Include time for setup, building and testing.
Preferred region Required
Include your Xcode version, project size or whether you need command-line builds. Don’t include sensitive credentials.

This opens your email app. Check the recipient and message before sending it from there.

Complete the required fields to prepare your email.

Already ordered?

Get help with an order

Sign in to the portal and open a support ticket. Include your order number, what happened and when.

  1. 01

    Identify the instance

    Include the order number, Mac model and region. If more than one machine is affected, identify each one so a connection issue on one instance isn’t mistaken for a problem with all of them.

  2. 02

    Describe what happened

    Tell us whether VNC failed to connect, SSH login didn’t work or a build command returned an error. Include the time and time zone, client operating system, last successful action and troubleshooting steps you’ve tried.

  3. 03

    Share relevant logs

    Include the relevant output before and after the error, along with the commands and tool versions. Remove tokens, passwords, customer names and sensitive path details first. There’s no need to upload your entire project.

If you can’t sign in, email support@xcodehost.com from your registered email address. Include your order number and the message you see when you try to log in. Don’t send your password or verification code.

Report an affected period

Request a service credit

The availability commitment is 99.9%. Over a 30-day month, that allows for about 43 minutes of downtime.

Include the details

Open a portal ticket with your order number, affected instance, start and recovery times, and time zone. List each interruption separately if there was more than one.

Connection errors or records of interrupted builds can help us check the same period.

How credits are assessed

Downtime beyond the allowance is credited as additional service time based on the affected period. We’ll review the order and cause of the interruption. Service terms cover exceptions such as force majeure and issues caused by user actions.

Submitting a request doesn’t guarantee a credit. We’ll share the result in your ticket.

Check a payment

Payment support

We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All payments are charged in USD.

Crypto payments

Provide your order number, transaction hash, transfer amount and time, and confirm that you used USDT-TRC20. Never share your wallet’s private key, recovery phrase or signing approval.

The transaction hash helps us verify payment. Don’t send a full wallet screenshot that may contain sensitive information.

Card payments

Provide your order number, payment time and amount, plus any message shown on the Stripe page. If you see an error, copy its text or attach a screenshot with sensitive details removed.

Never share your full card number, security code or bank verification code. Available payment options are determined by the backend.

If your payment status doesn’t match your order, add the records to the same portal ticket. Check the existing order before taking further action to avoid paying twice for the same issue.

Keep everything in one thread

Watch for a reply in the same place

Tickets are handled in the order they arrive. We’ll post our findings and any requests for more information in your original ticket; email enquiries get a reply to the original message.

Update the ticket; don’t open another

If you have new logs or the connection is working again, add an update to the existing ticket. If you’ve also emailed us, include the related ticket number so we can link the order, affected period and support history.

We review each issue individually and can’t promise a fixed response time in minutes or hours. Make sure your email address can receive messages, and check your ticket in the portal for updates.

Ready to build?

Choose a Mac and rental period, then confirm the end date before paying.