Haven’t ordered yet? Email us to discuss your use case. Already have an order? Sign in to the console and submit a ticket. Whether you’re choosing a region, connecting to a machine, or checking a bill, start with one of these two options.
First response time: We don’t publish a verifiable average or guarantee a response within a set number of minutes. Support staff handle both emails and tickets. Check the relevant conversation for updates.
All three topics use the same support email. Include the category in your subject line. For actions or questions about an existing order, use a console ticket so we can refer to the order history.
Not sure which region to choose or how long to rent? Tell us what you’ll be doing. A one-off build, iterative development, and always-on CI have different usage patterns, so you don’t need to add every extra up front.
Helpful details: your team’s time zone, expected rental period, project toolchain, and approximate project and build-cache storage needs.
support@macminivps.comCan’t connect over SSH, seeing remote display issues, or getting a failed build command? First, tell us whether it’s a connection issue or a project issue. Include the original error message—it’s more useful than simply saying “it doesn’t work.”
Helpful details: order number, region, steps that caused the issue, commands, and relevant logs. For an existing order, add details to its ticket in the console.
support@macminivps.comIf your USDT-TRC20 transfer has gone through but the order status hasn’t updated, or you need us to check a Stripe card payment, include the order and transaction details in the same conversation.
Helpful details: order number, payment method, amount, and transaction hash or payment reference. Never send your full card number, security code, or wallet keys.
support@macminivps.comThis tool creates an email draft; it doesn’t send your information to us. Review it, then click the button to open your email app. We’ll receive it only after you send it from your email app.
Multiple Desk M4 workstations can handle development, builds, and testing separately. Tell us what each machine will do, whether they’ll run at the same time, how much project and cache storage you need, and whether you need Thunderbolt 5 interconnects. Our team will review the setup based on those requirements—we won’t present multiple machines as one machine with more unified memory.
The only available configuration is Desk M4: M4, 16GB memory, and 256GB SSD. Team orders follow published catalog pricing; volume discounts aren’t assumed. Extra storage expands disk capacity, not unified memory. Confirm interconnect use and delivery requirements before ordering.
Specify the rental period and extras for each machine so we don’t apply one workstation’s add-ons to the whole team. The console will show the final configuration, available gateways, and amount due.
Add follow-up details to the existing conversation. Multiple tickets can split up logs, action history, and payment information; keeping everything in one thread makes it easier to track.
Copy the relevant number from your order details. For multiple workstations, specify which machine. For billing questions, include the relevant invoice reference. There’s no need to send screenshots of every order.
Include the region and the destination IP where the issue occurred. For connection failures, specify whether you’re using SSH or a graphical desktop, and whether the connection timed out, was refused, or failed authentication.
Include the actual command, the first relevant error, and surrounding context. For build failures, specify your Xcode version and target, and whether the issue is reproducible. Remove tokens and sensitive paths first.
Specify your local network type, whether you’re using a proxy, when the issue occurred and the time zone, and whether the result changes on another network. Don’t send personal information that isn’t relevant to troubleshooting.
Sign in and open the relevant order or instance details. Follow the options shown there to renew, reinstall, or restart. Confirm the region and machine before taking action. Reinstalling affects the existing environment and data, so back up first and follow the on-page confirmation prompts.
If an option is unavailable, an action fails, or you’re unsure what it will affect, submit a ticket with the order number and on-page message. Don’t retry the same action repeatedly or send your password or verification code to support.
Support schedules are coordinated across APAC and US West time zones, but we don’t publish fixed shift hours or verifiable average first-response times. The table below helps you share availability; it doesn’t mean live support is available around the clock.
| Schedule reference | What to include when you contact us | Replies and follow-up |
|---|---|---|
| APAC time zones | Include your local time and UTC offset, and tell us when you’re available to troubleshoot. | We’ll reply by email or in your console ticket. Check the conversation for updates on when it’s being handled. |
| US West time zone | Include the local date, time, and time zone. When daylight saving time applies, provide the UTC time if possible. | For issues that span multiple days, add details to the existing conversation—no need to submit a new ticket because of the time difference. |
| Order-related issues | Include the order number, impact, error message, and last known time it worked. Specify whether the issue concerns connectivity, builds, or payment. | Sign in to the console and submit a ticket. First response and final resolution are separate steps; we don’t guarantee a resolution timeframe. |
Regions operate year-round, 365 days a year; this doesn’t mean live support will respond immediately. USDT-TRC20 transfer confirmations and card payment processing also aren’t live support responses. Check the order status and the outcome in your support conversation. Payments are accepted only via USDT-TRC20 and Visa, Mastercard, or Amex (through Stripe), and are charged in USD.
For an existing order, keep all details in its ticket. If you’ve settled on a configuration, start with a dedicated physical Mac workstation for a day. Check the console for real-time availability.