Haven’t ordered yet? Ask us about models, locations, or team rentals. If you’re already set up, use a console ticket so we can look up your instance and billing details. Keeping these requests separate helps us find the right records faster.
Support hours are weekdays, 09:00–18:00 (UTC+8). These are targets for the first human response, not resolution times; complex issues may require further investigation.
For questions about choosing a model, multi-machine deployments, billing cycles, or purchasing requirements. Include the estimated number of machines, use case, preferred location, and desired start date. If anything is undecided, just say so.
First-response target1 business day during support hours
For connection issues, build failures, renewals, payment checks, and billing exports. Sign in to the console, open Tickets, select the relevant instance or order, and include the exact error, when it occurred, and steps you’ve already tried.
First-response target8 hours during support hours; location-level incidents are prioritized
You don’t need to create a ticket for presales questions. For existing customers, tickets let our team check the relevant instance and order directly, with fewer follow-up questions.
Fill in the details below to create a draft in your email app, addressed to support@zshmac.com. Nothing is sent to our servers through this page. Review the draft in your email app and send it yourself.
For bulk rentals, the key isn’t just the total machine count—it’s knowing what each machine will do. Include a simple list of intended uses in your email, and we can review models, locations, and billing cycles one by one.
If your build and test machines need access to the same internal resources, ask about deploying them in the same location. Let us know if you need fixed instance roles, CI labels, or a particular way for team members to connect.
Ideal for parallel builds, automated testing, and clearly divided pipeline tasks.
In your inquiry, list the estimated number of machines, the model for each, and the billing cycle. Include the billing name required for purchasing. To view or export bills for existing orders, sign in to the console.
Ideal when your team needs to review costs for multiple instances together.
If your workflow requires high-speed connections between machines, ask about adding a Thunderbolt 5 interconnect. It’s billed per machine at $5.3/month; tell us first what kind and volume of data the machines need to exchange.
For multi-machine workflows with a clear interconnect requirement—not a default for every deployment.
All charges are in US dollars (USD). We accept USDT-TRC20 and Visa / Mastercard / Amex via Stripe. The gateways available at checkout are shown in the console. For USDT transfers, verify the TRC20 network and the payment details shown for your order.
Paid, but your order status hasn’t updated? Need to change the invoice name or export a bill? Sign in to the console, find the relevant order, and submit a ticket with the order number and payment date. Never send your full card number or payment credentials by email.
For teams in Southeast Asia, start by comparing Singapore. For East Asia, compare Tokyo, Seoul, and Hong Kong. For teams in eastern North America or western Europe, compare US East. If your team is distributed, test the actual routes between your main developers and CI dependencies first.
The homepage latency table shows the median of 100 consecutive ICMP pings and is intended as a starting point. Actual connections also depend on your local provider, network routing, and time of day. In your presales email, tell us where your team is based so we can discuss your workload.
Know which machine you need? Compare the three models and four billing cycles, then configure your order. Still have deployment questions? Add them to the email draft above.