Do you archive one app a day, or run multiple release pipelines at once? Share your build volume, test concurrency and team time zones so we can recommend dedicated cloud Mac configurations and rental terms. For existing orders, submit a console ticket.
Two ways to get in touch: email support@osxbuild.com or submit a ticket in the console after signing in.
This form creates an email draft only; it won’t send anything from this page. Review the details, then send it from your preferred email app.
To: support@osxbuild.com
In your email app, check the recipient, sender and message before sending. If no email app is set up on your device, copy the preview and email it to the address above.
There are three types of request, but only two ways to contact us: email and support tickets. For existing orders, continue in the same ticket to keep the context together.
Haven’t ordered yet? Start with an email. Include your daily build volume, archive time and peak concurrency so we can discuss M4 or M4 Pro, cache storage and billing terms. Team size alone isn’t enough to size your machines.
For first-time rentals, location selection or moving builds from local machines.
Sign in to the console and submit a ticket with your order number, location, the time the issue occurred and steps to reproduce it. Use the same channel for connection failures, build issues, billing and renewals.
Helpful details: the last 50 lines of a redacted log and steps you’ve already tried.
Email the same address: support@osxbuild.com. Include the number of machines, rollout schedule, expected rental term and which tasks need to run concurrently. For multiple locations, describe each team separately.
Use “Team bulk rental” as the email subject to get straight to configuration planning.
Our support team coordinates across APAC and US West time zones. Response times depend on the current queue and issue complexity. Providing the full context helps avoid follow-up questions.
If your team works in APAC time zones, include your time zone and available contact hours. Note when the issue first occurred to help us interpret logs across time zones.
If build volume differs between regular workdays and release days, share both the average and peak. For planning, it matters more when jobs run concurrently than the daily total alone.
US West teams can share local working hours and their next release date. For async support, include the failed step, actions already tried and current status so the next person can pick up where you left off.
If you get new logs or resolve the issue while waiting, reply to the original email or update the existing ticket. Don’t open a duplicate ticket; it can split the troubleshooting history.
For ongoing troubleshooting, keep the original email subject or ticket number. Email send time doesn’t indicate when a machine will be delivered; check order progress in the console.
Bulk rentals are about distributing workloads, not installing every tool on every machine. Map dependencies across archiving, testing and exports before deciding what to run in parallel.
M4 Pro configurations come with 64 GB of memory and a 2 TB SSD. In a multi-machine build farm, assign dedicated runners by app, release branch or task type to avoid simultaneous changes to the same working directory.
Describe concurrency needs for archives and UI tests separately. Plan keychains, cache directories and build artifact paths by task, too. Multiple machines won’t automatically split a single archive run.
DerivedData, dependency caches and simulator resources all use disk space. Add a 1 TB or 2 TB SSD. When you contact us, tell us which past artifacts you need to keep and whether caches can be regenerated.
Thunderbolt 5 daisy-chaining is billed per machine: $1.8/day, $4.8/week, $8.8/month or $23.9/quarter. It’s a physical connection option, not a cross-region network connection. Tell us how you plan to use it when discussing multiple machines so we can confirm the setup.
See the plan page for pricing on two machine configurations, four rental terms and add-ons. Ready to go? Order now. Need help mapping your workloads? Email us first.
Use email to describe your requirements and tickets to follow up on orders. Neither channel requires your complete signing assets or account password.
Do not include certificate private keys, account passwords, complete .p12 files or API keys. Redact keys, public-facing credentials and sensitive paths from screenshots. Just tell us which signing method you use.
For technical tickets, include the location, order number, time of occurrence and time zone. The last 50 lines of a log are usually easier to work with than the full build output. Include context around the first specific error, too.
For pre-sales, say “I’d like to confirm the configuration and rental term.” For troubleshooting, say “I need help restoring the connection” or “I need help diagnosing an archive failure.” If you’ve resolved it yourself, update the existing thread so no one acts on outdated information.
Know what you need? Rent now. Still deciding? Email us your workload and concurrency details. For existing orders, continue in your console ticket.