Pre-sales
Which configuration?
Describe Xcode builds, GitHub Actions Runner, MLX inference, media processing, or remote collaboration, and include concurrent jobs plus expected memory and disk needs.
Recommended channel: Email
Route by issue, not department
Tell us what you need to solve
Email us about plans, regions, or team purchasing. For existing orders, access issues, or service impact, sign in to the console and submit an order-linked ticket. We review impact and order status first, then respond by priority.
Our only public email: support@vpsgit.com. Never include passwords, keys, tokens, or other access credentials in email or tickets.
REQUEST ROUTING
2 contact channels
Issue routing board
PRE-01
Which plan and region?Workload, location, term, memory, and storage needs
Email
ORD-02
Existing order and billing statusOrder number, payment status, renewal, or configuration changes
Ticket
OPS-03
Connection, build, or node issueStart time, impact, reproduction steps, and checks completed
Ticket
TEAM-04
Team purchasing and phased deliveryQuantity, batches, network limits, access roles, and handoff process
Email
Singapore · Japan (Tokyo) · South Korea (Seoul) · Hong Kong · US East · US West
Check the console for real-time availability
Choose the issue, then the channel
Five issue types, two clear paths
Email works best for pre-order planning. Console tickets are best for order-linked issues, status checks, and ongoing follow-up.
Region
How to choose a region
Share the developer location, code repository location, dependency sources, and main collaboration time zone. We use this to compare six available regions; fixed latency is not guaranteed.
Recommended channel: Email
Order
Existing order issue
Renewals, payment status, region, and model changes require an order link. Submit a ticket in the console to reduce back-and-forth when verifying identity and order details.
Recommended channel: Console ticket
Incident
Technical troubleshooting
Include the issue start time, region, impact, reliable reproduction steps, and completed network, disk, process, and toolchain checks. Do not submit access credentials.
Recommended channel: Console ticket
Team
Team and bulk requirements
Specify the number of cloud Macs, desired delivery batches, network limits, access roles, and cross-time-zone handoff process. We will confirm the available catalog before discussing execution order.
Recommended channel: Email
Pre-sales request email
Describe the workload clearly to move faster than asking only for price
The details below are assembled into an email draft in your browser only; nothing is submitted directly to the site. Starred fields provide the context needed for a useful recommendation.
Existing order support
Link the order first, then describe the reproducible issue
Console tickets are the preferred channel for existing orders, runtime issues, and service impact. Use the checklist below to organize details before copying them into a ticket.
01
Order and region
Prepare the order number, current region, and model in use. Do not submit login passwords or access keys.
02
Start time
State the date, time, and time zone when the issue first appeared, and whether it is continuous or intermittent.
03
Impact
Explain whether one job, one node, all team members, or only a specific network path is affected.
04
Reproduction steps
Start with the last step that worked and record commands, operation order, error text, and expected results.
05
Checks completed
List the results of network, authentication, disk space, process resources, build toolchain, and regional path checks.
Team and bulk requirements
Put quantity, batches, and access boundaries in one email
Team requirements depend on more than machine count. Delivery batches, network limits, access roles, and cross-time-zone handoffs directly affect the preparation sequence.
All orders are settled in USD
Payment supports USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. Actual gateway availability is shown in the console.
- New order and renewal prices follow the fixed term selected at checkout.
- For payment status, renewals, and existing order issues, sign in to the console and submit an order-linked ticket.
- Do not send full card details, wallet keys, or payment credentials by email.
Prioritized by impact and order status
Pre-sales guidance
We aim to send the first reply within 1 business day. When details are complete, we will explain the recommended model, term, and region.
General support
We aim to send the first reply within 1 business day. For order-related issues, the linked information in the console ticket takes priority.
Service event
Valid tickets involving service impact are prioritized. We first confirm the scope, then provide ongoing troubleshooting and recovery updates.
If the order number, region, start time, or reproduction steps are missing, the first reply will usually request more information.
Pre-submission checklist
Submit only the data needed to solve the issue
The form requests contact details, workload, order links, region, timing, impact, and troubleshooting records for recommendations, service delivery, and support tracking. Email drafts are generated locally; after sending, content is retained only as needed for support and order records.
Remove passwords, keys, and tokens
Keep logs to relevant excerpts
Use console tickets first for order issues
Ready to start
Rent a dedicated cloud Mac by the day, week, month, or quarter
Three Apple Silicon physical-node configurations across six available regions. Check the console for real-time availability when ordering.