Support email
Best for presales selection, bulk requirements, payment details, and regional partnerships. The form only creates an email draft on your device; it does not submit data to the website.
Route first, resolve next
Buy a Cloud Mac or troubleshoot an active node
Ask by email about model, region, and term selection. For connection, build, network, or billing issues on an existing order, submit a console ticket with the node ID.
- Before purchase
- Send your configuration, region, term, and team size
- While in use
- Provide the node ID, time range, and reproduction steps
CONTACT ROUTING
Two channels
Console tickets
Best for connection, build, hardware, network, and order issues on an activated node. Tickets can be linked directly to the service record.
Single public email
support@orbvps.com
Contact options
Choose a channel by issue stage
There is no need to send the same issue twice. Use support email before purchase; for issues linked to an order or node, use a console ticket to preserve context and handling history.
Before purchase & partnerships
Send a structured email
For model selection, team-size planning, region selection across four nodes, rental terms, payment record inquiries, and regional partnerships. Include your target workload, concurrent task volume, and preferred start date in one message.
- The recipient is always support@orbvps.com
- Initial triage is usually completed within one business day on business days
- For complex selection requests, we will continue verifying requirements by email
Existing order
Submit a console ticket
For SSH, graphical desktop, Xcode builds, self-hosted runner, disk, network, restart, and billing issues. Select the relevant service and include the node ID in your ticket.
- Node issues can be linked to the relevant service record
- Progress and additional information stay in the same ticket
- For urgent incidents, provide an accurate time range and command output
Email generator
Prepare all the information support needs
The following information is used only to create a draft addressed to support@orbvps.com on your current device. The website does not receive or store form contents, and you can still edit the draft in your system email app before sending.
Payment inquiries
Payment methods and required details
All orders are settled in USD. Available gateways are determined by the console and support only the following two methods.
USDT-TRC20
For payment-status inquiries, provide the order number, transfer time, amount, and transaction ID. Never send wallet access credentials or recovery information by email.
Visa / Mastercard / Amex
Card payments are processed by Stripe. To verify a payment, provide the order number, payment time, and last four digits of the card. Do not send the full card number or security code.
Use a console ticket for billing issues.
Tickets can be linked to order records. Email is best for confirming payment details before purchase or explaining that you cannot access the console.
Privacy & confirmation
Submit only what is needed to resolve the issue
Contact information is used to identify requests, respond to questions, verify orders or service context, and prevent duplicate handling. Email and ticket records are retained only for the periods needed for fulfillment, security audits, and necessary dispute handling, then deleted or de-identified according to applicable procedures.
Redact technical materials before sending. Remove access credentials, private keys, tokens, personal user data, unpublished source code, and build artifacts unrelated to the issue. If more information is needed, reply to the original email or ticket instead of creating parallel records.
View the data privacy policy-
01
Confirm the channel
Use support email before purchase; prioritize console tickets for existing-node issues.
-
02
Confirm the context
State the order or node, time of occurrence, reproduction steps, expected result, and actual result.
-
03
Confirm redaction
Check the message, screenshots, and logs. Do not send access credentials or unrelated business data.
Existing order
Link the node and submit a console ticket
Select the relevant service and attach the node ID, issue time, command output, and redacted screenshots. To purchase a new node, proceed directly to configuration.