Choose the right channel and save a round trip
Still deciding which Mac to rent? Email us about your build workload. Already have an instance? Sign in to the console and submit a ticket. Need several machines? Include concurrency, rental term, and delivery schedule.
Support email: support@osxhost.com. Email us about plans or purchasing; keep order-related details in the same ticket whenever possible.
Start with your request
No need to send the same request twice. Use the same support email for plan advice and purchasing, and a signed-in ticket for instance issues.
Tell us your project type, workload per build, concurrent simulators, and cache usage. We’ll help you choose from three Mac tiers based on workload—not just repository size.
For connection, build, or disk issues, find the relevant order in the console and submit a ticket. Link the instance and time period so we can assess the impact.
Start with a reproducible build task. List concurrent jobs, the number of machines needed, and delivery batches. Then discuss machine allocation, data sync, and billing requirements.
Include the details we need
This form does not submit messages to our servers. Review the draft, then send it from your email app to support@osxhost.com. For technical issues with an existing order, please use a ticket.
If no email app is configured, copy the content into your usual email app. Check the recipient and attach any redacted files yourself.
Submitting and getting a reply are different
Tickets and emails can be submitted at any time. Nodes run 365 days a year; machine uptime does not mean an immediate human response.
Sign in to the console, open a ticket, and include the relevant order number. Add logs and new reproduction results to the same ticket so the full history stays together. Once the instance is back up, share the recovery time so we can confirm the impact window.
Email support@osxhost.com with your request. When you receive a reply, continue the same thread with the number of machines, rental term, and build requirements—no need to start a new subject.
Check the console or your support email for current staffed hours and estimated first response times. Include the time window when you’d like a reply so we can coordinate across time zones.
Use UTC+8 as a reference—for example, “Please reply between 09:00 and 18:00 (UTC+8).” This is when you’re available, not a commitment to staffed support hours.
Specify UTC−8 or daylight saving time, UTC−7. For issues spanning midnight, give the full date and start and end times instead of relative terms like “last night” or “this morning.”
Start with a working setup, then scale
Every machine is a dedicated physical host, not a virtual machine. Before scaling out, confirm workload isolation and cache strategy, then decide how many machines you need.
Separate queued jobs from those that must run simultaneously. Note whether archive builds, simulator tests, Unity exports, or MLX inference share a machine, and estimate how long each job takes.
Host M4 Lite: M4 / 16GB / 256GB; Host M4 Plus: M4 / 24GB / 512GB; Host M4 Pro: M4 Pro / 64GB / 2TB. Start by checking memory and cache use, then validate concurrency with your own project.
Choose from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West. Tell us where your code repositories and build artifacts are accessed. For Thunderbolt 5 daisy-chaining, include the number of machines, topology, and data exchange goals so we can confirm compatibility before you order.
List the machines needed for the initial test and each later expansion batch. All charges are in USD. For consolidated billing, send the billing entity, related orders, and billing cycle requirements; support will confirm how they can be grouped.
Check only what you need
We accept USDT-TRC20 and Visa / Mastercard / Amex via Stripe. All charges are in USD. Available payment gateways are determined by the response from the backend.
First confirm the network, amount, and recipient details shown on the order page, then check whether the transaction has been confirmed. To help us verify the order, provide its number, transaction hash, USD amount, and payment time.
Don’t pay again to refresh the order status. If payment details don’t match, share the transaction information in the same ticket. Never send wallet keys.
Sign in to check your paymentAfter paying with Visa / Mastercard / Amex via Stripe, check the billing status in the console. If your bank shows a charge but the order hasn’t updated, attach the order number, amount, payment time, and a redacted screenshot.
We verify payment status against gateway and order records; a screenshot alone isn’t enough. Never send your full card number, security code, or verification details by email or ticket.
Sign in to check billingSubmit a ticket in the console with the order in question, the reason for the refund, and relevant payment records. Support will check the order status and applicable terms, then explain the available options.
Processing time, refund route, and eligible amount depend on the order and gateway verification. Until confirmed, don’t send a different payment address or ask to redirect the refund.
Sign in to ask about a refundTake a minute to check before contacting us
Connection, signing, disk, and toolchain issues each need a different approach. Record the current state before reinstalling anything or clearing caches.
Check the instance details, connection method, and local network. For build issues, include your Xcode version, the failed step, and the exact error text. For disk issues, record storage usage before deciding what to remove.
Check the current rental term, add-ons, and order expiry first. When asking about upgrades, renewals, or data handling, include your order details so general guidance isn’t mistaken for a decision on your order.
Order now to choose a model, rental term, and region. Need to confirm the setup or purchasing arrangements first? Draft an email.