Setting up an iOS build farm or troubleshooting a host? Email us for setup advice and team plans. For active services, submit a ticket in the console. Send your request to the right place to keep things moving.
Dedicated physical Macs, not virtual machines. Rent by the day from $21.1/day. Check the console for real-time availability.
Email us to discuss your requirements. Use console tickets for issues tied to an account, order, or host. Keep all relevant details in one email or ticket so the full context stays together.
Tell us how many builds you run each day, how many run in parallel, and whether you use simulators. We’ll first assess the resources needed for compiling, signing, and testing, then discuss our three Mac plans.
For connection failures, host issues, or order and billing questions, sign in to the console and open a support ticket. Include the relevant host or order ID so we can match the issue to your service.
Need multiple runners, a phased rollout, or collaboration across regions? Get in touch by email. Start with your usage patterns and number of parallel jobs; you don’t need to choose a configuration for every machine yet.
This tool creates an email draft; it does not submit a form to our website. After you fill it in, your device’s email app will open. Check the recipient and message before sending. All inquiries go to support@armrdp.com.
Start with a defined rental period and toolchain. Get a build working, then decide whether to scale up to a long-running iOS build farm.
Yes. You can rent by the day, starting with the ArmRDP M4 Base at $21.1/day. This is a paid rental, not a free trial. We recommend testing with your own project: clone the repository, install dependencies, archive, sign, and export a build. Compare clean-build times with cache-hit times, then choose a weekly, monthly, or quarterly rental.
Yes. Choose and pin the Xcode versions your projects need, and manage multiple versions if required. Each version must be compatible with the host’s macOS and target SDKs. Share your exact version requirements when you contact us. Set the toolchain path in your pipeline and pin dependency versions to avoid mismatches between the GUI and the runner’s command-line tools.
We accept USDT-TRC20 and Visa, Mastercard, or Amex via Stripe. All payments are charged in US dollars (USD). Available payment gateways are determined by the response from our backend. For order or payment issues, submit a ticket in the console and include your order ID. Never include full payment card details in an email or ticket.
Our regions operate year-round, 365 days a year. Support communications are coordinated using the time zone of the relevant region. Host uptime and staff response times are separate. Include your own time zone when reporting an issue.
For setup advice, team plans, and other inquiries, email support@armrdp.com. The first response confirms your request and any details we still need; it does not mean configuration checks or issue resolution are complete.
If you need to add details about versions, parallel jobs, or rental duration, reply to the original email. Avoid starting new threads so your request stays together.
Email supportFor host, connection, order, and billing issues, submit a ticket in the console. The first response will confirm the scope of the issue. If we need to reproduce or investigate further, continue the discussion in the same ticket.
For connection issues, say whether SSH, VNC, or both are affected. Include the error code and the last time the connection worked. Do not include your host password.
Sign in to view your tickets| Region | Time zone | What to include when reporting an issue |
|---|---|---|
| Singapore | UTC+08:00 | Issue start and end times, with your local time zone |
| Japan (Tokyo) | UTC+09:00 | Issue start and end times, with your local time zone |
| South Korea (Seoul) | UTC+09:00 | Issue start and end times, with your local time zone |
| Hong Kong | UTC+08:00 | Issue start and end times, with your local time zone |
| US West | UTC−08:00 / UTC−07:00 | UTC offset and daylight saving time status in the logs |
Our docs cover setup, connectivity, toolchains, and runners. FAQs explain billing, regions, and usage. Follow the relevant steps first; if you still need help, share the results by email or in a support ticket.