01
Haven’t ordered yet or can’t log in
Send a structured email for configuration selection, technical feasibility, billing clarification, or partnership requests.
support@vmorbit.com
Contact & routing
Route your question and required details to the right workflow
Ready to rent a cloud Mac? Use the template below to organize your team, workload, region, and term requirements. For existing orders, instances, or billing questions, log in to the console and submit a linked ticket so our team can access the relevant records.
The only public contact channels are support email and console tickets. Do not include passwords, private keys, recovery codes, or complete payment credentials in your email.
Request routing workflow
ROUTE / 02
02
Existing order or instance
Select the relevant order in the console before submitting a ticket to keep the region, billing, and handling records linked.
Open the console
Email generator
Choose an issue type, then provide the required details
This form does not submit data to the website backend. When complete, it opens your device’s mail app and creates a draft with the recipient, subject, and message body.
Inquiry details
Different questions require different minimum details
The closer the information is to your actual runtime environment, the fewer follow-up questions are needed. The fields below support routing and reproduction; do not send sensitive credentials.
Pre-sales inquiry
Used to determine whether the two models, six regions, and four billing terms fit your development or experimental workload.
- Team size and concurrent usage
- Xcode builds, CI/CD, or AI experiment workloads
- Target region and actual office network location
- Expected daily, weekly, monthly, or quarterly term
- VMOrbit M4 or VMOrbit M4 Pro
Technical inquiry
For compatibility checks before ordering. For issues with an existing instance, use a console ticket so the node record stays linked.
- SSH, VNC, or not connected yet
- Xcode, Command Line Tools, and SDK versions
- fastlane, dependency management, and build commands
- Self-hosted runner platform and repository scope
- Redacted log summary and target completion date
Billing inquiry
All orders are billed in US dollars (USD). For verification, include the order ID, billing term, and specific question.
- Order ID shown in the console
- Related model and add-ons
- Daily, weekly, monthly, or quarterly billing term
- Completed payment or renewal action
- Expected outcome and current displayed status
Partnership inquiry
For defined team purchasing, sustained build capacity, or cross-region collaboration needs. No separate email address is required.
- Planned node count and regions
- Initial launch date and expected rental term
- Build concurrency, queue, or experimental resource requirements
- Team permissions and handoff process
- Verifiable acceptance criteria and deliverables
Payments & billing
Confirm the payment route before submitting a billing question
VMOrbit supports only the two payment methods below. Actual gateway availability is determined by the console response, and all orders are billed in US dollars (USD).
USDT-TRC20
For billing verification, you may provide the order ID, transaction ID, and payment time range. Do not send wallet recovery codes, private keys, or complete account credentials.
Visa / Mastercard / Amex
Card payments are processed by Stripe. Describe only the order status, payment time, and publicly shareable transaction result; do not submit the full card number or security code.
Unified USD billing
The USD amount confirmed in the order controls the model, term, and add-ons. If the displayed amount differs, submit a billing ticket for the relevant order in the console.
Region check
Choose from the six available regions
Select preferred regions based on developer location, repository routes, dependency sources, and remote desktop experience. Actual availability is shown in real time by the console.
Region selection list
6 REGIONS
Singapore
Ideal for connection testing from networks in Southeast Asia.
Japan (Tokyo)
Ideal for teams in Japan and nearby locations evaluating real network routes.
South Korea (Seoul)
Ideal for Korean teams and build workflows targeting local networks.
Hong Kong
Ideal for cross-region Asian teams validating network performance.
US East
Ideal for teams whose members or dependent services are located in the eastern United States.
US West
Ideal for developers in the western United States and related code and dependency routes.
Both VMOrbit M4 and VMOrbit M4 Pro are available in all six regions above. Do not enter cities outside this list; fulfillment details are determined by the order confirmation.
See how to choose a region
Safe submission
Redact logs; keep credentials out of email messages
For troubleshooting, we usually need only the region, time of occurrence, reproduction steps, error type, and a minimal log excerpt. Do not send anything that could directly log in, sign, recover an account, or complete a payment.
Minimum necessary information
Keep the error context, but remove token values, host credentials, signing material, and complete fields that could identify a payment instrument.
Passwords and recovery codes
Do not send login passwords, one-time recovery codes, or any string that could be used to take over an account.
Private keys and complete tokens
Remove SSH private keys, CI tokens, repository tokens, and signing materials from logs and screenshots.
Complete payment credentials
Provide only the order ID and publicly shareable transaction result; do not send full card numbers, security codes, or wallet private keys.
Minimal reproducible record
The region, time, steps taken, error summary, and impact scope are usually enough to begin triage.
Response expectations
How each entry point records, responds, and continues the conversation
Email is best for pre-order questions and help when you cannot log in. Console tickets are best for anything tied to existing orders, instances, or billing records.
Email thread
After sending an email, reply to the same thread and add materials there instead of creating multiple threads for one issue. The first business response target is 1 business day.
Console ticket
A request record is created after successful submission. Progress, categorization, and additional materials are updated continuously in the corresponding thread.
Connection interruption triage
Choose the technical or node issue category and include the region, time of occurrence, and minimal logs. The initial triage target is 4 hours.
Billing and partnership requests
The first business response target for billing questions is 1 business day. For partnership requests with complete details, the target is 2 business days.
Next steps
Link a ticket for existing orders; generate an email if you have not ordered
Choose the entry point that matches your current status and include the minimum necessary details so your request is actionable from the first response.