Start with your workload

Let’s talk about your build queue

Email us about plan selection or multiple machines. For issues with an existing node, sign in to the portal and open a ticket with the plan, node and relevant error details.

Email us at support@xcoderent.com. Not sure which specs you need? Use the checklist below to put your requirements in an email.

Start with the right channel

Email works best for discussing requirements; support tickets keep orders, nodes and troubleshooting history together. Keep each issue in one email thread or ticket so the context stays in one place.

Before you order

Still deciding which plan to rent? Tell us what you build, how many Xcode targets you have, what you test and how much disk space you use. Instead of just saying “we need more speed,” share your current clean-build, incremental-build and Archive times.

You can also ask about node locations, extra storage and billing cycles. All three plans include an exclusive physical Mac mini, not a virtual machine. Availability is confirmed in real time by the portal.

Technical support

For SSH, remote desktop, Xcode, code signing or billing issues with a rented node, sign in to the portal and open a ticket linked to the relevant order or instance.

Include when things last worked, the steps that failed and a concise summary of the full error. Never include passwords, private keys, certificate passphrases or access tokens in an email or ticket. Redact sensitive information from logs first.

Multiple machines for your team

For parallel builds across multiple machines, tell us how many nodes you need, what each one will run and how long you expect to use them. Note which tasks involve compiling, simulator testing and artifact uploads so we can help determine whether to split the queue or increase the specs of each machine.

Also let us know whether you share caches, need isolated code-signing environments and have preferred cutover times. All multi-machine enquiries go through the same support email—there’s no need to contact a separate sales team.

When should I expect a reply?

We don’t promise a fixed response time. Email replies stay in the original thread, and you can check the progress of a ticket in the portal. If a build is blocked, tell us what’s affected, whether another node is available and when you can help troubleshoot. Sending a duplicate ticket won’t fill in missing details; add any logs to the original ticket.

Put your build requirements in an email

This creates an email draft; it does not submit an online form. After generating the draft, review its contents and open your email app to send it. The information you enter here is not uploaded to our servers.

Workload and preferences

Enter the number of people who develop or build, for example, 5.

Enter your estimate. If you haven’t tracked it yet, enter 0 and add a note below.

Choose based on your team’s working hours and actual connection experience. Node location doesn’t guarantee latency.

This is just a preference for your enquiry. It won’t reserve a node or create an order.

A short-term trial and an always-on build queue may suit different cycles. Confirm the final setup when you place your order.

Each physical node is assigned to one tenant. Node count is not the same as the number of concurrent tasks on a machine.

Include project size, Xcode version, target count, cache usage and times you could help with a migration. Don’t include access credentials or other secrets.

Review the draft after it’s generated, then decide whether to send it.

Payment and billing

We accept USDT-TRC20 and Visa / Mastercard / Amex via Stripe. All charges are in USD. Available payment gateways are confirmed by the backend. Enquiries by email are not charged and don’t place an order. Confirm your plan, billing cycle, add-ons and final price during checkout.

Plan a cutover using local time

Agree on a time to pause new jobs, sync data and validate the new node. The times below are local times, not support staff schedules. US locations use representative time zones; daylight saving time is handled automatically by your browser.

Singapore

Asia/Singapore · UTC+8

Coordinate source syncs and artifact checks with your Southeast Asian team’s working hours.

Tokyo, Japan

Asia/Tokyo · UTC+9

When coordinating with a team in Japan, include both the local time and time zone to avoid confusion across dates.

Seoul, South Korea

Asia/Seoul · UTC+9

When working with a team in South Korea, agree on the order for switching the signing environment and runner queue first.

Hong Kong

Asia/Hong_Kong · UTC+8

A convenient option for teams in southern China and Southeast Asia. Test the connection before moving large caches.

US East

America/New_York · Changes with daylight saving time

Find overlapping hours for teams in eastern North America and Western Europe. Always specify the time zone when scheduling.

US West

America/Los_Angeles · Changes with daylight saving time

Fits the working hours of teams on North America’s west coast. When coordinating with teams in Asia, double-check the date in both locations.

Local time is based on your device’s clock, not node monitoring data. Nodes run year-round, 365 days a year. Use these times to plan your own data migration and build cutover.

Or start with one machine

Try a day to validate source checkouts, the Xcode toolchain and your Archive workflow. Get one real pipeline running first, then decide whether to expand to a multi-machine build farm.

Daily rentals start at $21.7/day. Choose your plan, billing cycle and node when you order; availability is confirmed in real time by the portal.