Still choosing? Email us to discuss your options. Already have an active machine? Sign in to the console and submit a ticket. We’ll confirm your workload, machine count, and machine IDs, then help arrange your dedicated Mac mini server.
Contact is available by email or console ticket only. The tools below help prepare an email; they do not submit your inquiry to this website.
Tell us whether you need a single-project build, multi-simulator testing, or an MLX experiment. Include your estimated machine count, region, and rental term so we can discuss the right setup for your memory, storage, and workflow needs.
Report connection failures, build errors, renewals, or order questions through a console ticket. Submit it from the relevant account and include the region and machine ID so we can locate the right system.
For multiple runners, deployments across regions, or quarterly rentals, outline each task group and its owner. Specify the number of machines separately from the number of concurrent tasks—team headcount alone doesn’t determine machine count.
Tell us your workload, machine count, preferred region, and rental term. After generating the email, review its contents, then send it from your own email account to support@vpshold.com. You don’t need to include payment details or connection credentials here.
To: support@vpshold.com
Review the message and click Send in your email app. If your device isn’t set up with an email app, copy the text above into your preferred email service.
Sign in to the console, open the tickets area, and create a ticket linked to your order or machine. Don’t just say “it won’t connect.” Tell us whether you’re using remote desktop or SSH, where the failure occurs, and when it started.
Include the region, machine ID, and relevant order ID. Use the order ID for order and renewal questions, and the machine ID for connection and system issues. If multiple machines are affected, list each one separately.
Include your local operating system, connection method, exact error message, and steps to reproduce the issue. For build problems, add the Xcode version, failed stage, and relevant logs. Don’t upload the entire project instead of the key error details.
Say whether work is fully blocked, whether there’s a workaround, and when the machine last connected successfully. Include the UTC offset to avoid time zone confusion.
Don’t paste passwords, SSH private keys, complete signing certificates, payment card details, or repository URLs containing access tokens. Redact sensitive information from screenshots; error codes, timestamps, and machine IDs are enough.
If you can’t sign in to the console, email support@vpshold.comwith your account email address and details of the login issue. Keep follow-ups about the same issue in one email thread or ticket instead of creating duplicates.
A team sharing development machines across shifts has different capacity needs from multiple pipelines building at the same time. List concurrent tasks first, then discuss machine count. For cross-region deployments, specify each region’s purpose, owner, and expected rental term separately.
Distinguish between running tasks in parallel on separate machines and a Thunderbolt 5 setup. Describe each task’s memory needs, how data moves between tasks, whether a graphical interface is required, and which tasks must run at the same time.
A parallel setup does not automatically pool memory, allocate compute, or provide a ready-made distributed software environment. Discuss and confirm specific connectivity and workflow requirements first.
List the machine count and owner for each location. The five regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US East. Consider where your users, code repositories, and data sources are located when choosing regions.
Explain whether code, caches, and assets need to be synced; disks aren’t shared by default across regions. For team access, also agree on system accounts, runner permissions, and screen usage.
Choose a daily, weekly, monthly, or quarterly term. For long-running workloads, include each machine’s expected start date, renewal owner, cost center, and data export plan when the rental ends.
Bulk inquiries don’t include additional unpublished discounts. Machine and add-on prices are listed in the plans catalog. Payment is accepted in USD via USDT-TRC20 or Visa, Mastercard, and Amex through Stripe.
You can submit emails and console tickets at any time. Regions operate year-round, 365 days a year, but that doesn’t mean every inquiry receives an immediate reply. First responses and progress updates are sent by email or ticket. For release-critical issues, include your deadline and the impact.
| Region | Local time zone reference | Submission availability | Suggested format |
|---|---|---|---|
| Singapore & Hong Kong | UTC+08:00 | Anytime by email or console ticket | Add UTC+08:00 after the time of the event, and say whether it affects a current build. |
| Japan (Tokyo) & South Korea (Seoul) | UTC+09:00 | Anytime by email or console ticket | Add UTC+09:00 after the time of the event; avoid vague terms like “tonight” or “tomorrow morning.” |
| US East | UTC−05:00 / UTC−04:00 | Anytime by email or console ticket | Include the actual UTC offset for standard or daylight time, rather than using an abbreviation alone. |
For example: “The error occurred at 17:00 (UTC+08:00), or 09:00 UTC.” The same moment is 18:00 in UTC+09:00, 04:00 US Eastern Standard Time, and 05:00 US Eastern Daylight Time. These are time conversion examples, not fixed support hours.
If the issue is resolved, add the resolution time and steps taken to the original ticket. This helps distinguish an ongoing issue from a temporary one and avoids repeated questions in follow-ups.
These are examples of clear communication, not customer testimonials or response-time guarantees. Use the same format for your own email or ticket.
“I included the machine ID, region, and exact SSH error in one ticket, along with the time of my last successful connection. That way, we’re discussing my machine, not just a general connection issue.”
“I started by listing two parallel build groups, then specified the owner, resource size, and quarterly rental term for each. The email explains how we plan to work, not just how many machines we want to buy.”
Find self-service guides for connections, Xcode, certificates, CI setup, and renewals. For an active machine, include its ID in a console ticket. Still choosing? Describe your workload in an inquiry email.