Contact VMOwn

Clear questions get straight to the right team

Contact our support team by email for pre-sales selection, remote access, CI/CD integration, billing checks, and team purchasing. For issues involving an existing order, device, or access credentials, sign in to the console and submit a ticket so the team can verify the order context.

Rent a cloud Mac now Sign in to the console to submit a ticket

For general inquiries, email support@vmown.com. Include your target task, configuration, node, and preferred rental term to reduce follow-up questions.

Support request handoff board CONTACT / HANDOFF

Submit for

Pre-sales configuration Task, concurrency, rental term, node

Existing order Order ID, device, time of occurrence

Connection issue OS version, network location, error details

Automated build Runner, working directory, failed step

Billing & purchasing Rental term, configuration count, billing method

Public support email support@vmown.com

Existing order issues Console ticket

Initial response Usually within 1 business day

Choose the right channel first

Six issue types, each with different information to prepare

Selection, purchasing, and partnership questions without an order are best sent by email. For existing orders, device status, renewals, or access credentials, submit a ticket through the console first.

Configuration advice

Describe your main task, number of concurrent projects, peak memory use, storage needs, and expected rental term. Our support team will help you choose among the three available configurations without inventing additional options.

Organize your configuration needs

Ticket

Existing order

Orders, renewals, billing-cycle changes, device details, and access-credential management are tied to your account context. Sign in to the console, submit a ticket, and include your order ID.

Open the console

Ticket preferred

Connection issue

Provide the time of occurrence, target node, client network location, OS version, complete error text, and reproduction steps. For an existing order, submit the ticket through the console so we can identify the relevant device.

Submit a connection ticket

Email or ticket

Development environment

Include your Xcode version, build command, Runner type, dependency-management method, and failed stage. Ask about general integration issues by email; submit a ticket for issues on an ordered device.

Describe your development environment

Invoices & billing

Include your order ID, rental term, configuration count, and the charges to review. Do not send complete payment-card details or account passwords by email.

Describe your billing issue

Team purchasing

Include your team size, number of devices needed, planned nodes, rental term, and purchasing timeframe. Send partnership and security-material requests to the sole support email address as well.

Organize your purchasing needs

Structured email

Generate a support email with the essential context

This form organizes the email subject and body in your browser only; it does not submit the content to the website server. After you click the button, your device’s email app will open a draft.

Basic request information

Fields marked with an asterisk are required to generate the email. Enter an order ID only for an existing order. Do not enter account passwords, private keys, or remote-control verification codes.

Name or preferred form of address *

Work email *

Issue type *

Order ID Leave blank if you have no order; for existing-order issues, we recommend submitting a console ticket as well.

Target node

Preferred rental term

Issue description * Include the target task, time of occurrence, environment versions, error text, steps already tried, and expected result. Minimum 20 characters.

Send a blank email directly

Minimum information for technical issues

Six pieces of context are enough to start troubleshooting

Do not send only a screenshot or say “cannot connect.” Copyable error text, the exact time, and reproduction steps make it easier to match the issue with node records and build logs.

Time of occurrence

State the local date, exact time, and time zone. If the issue recurs, also describe its frequency and duration.

System and tool versions

Provide the version numbers for macOS, Xcode, Runner, fastlane, or relevant dependencies; do not just write “latest.”

Network location

State the country or region where the connection originates, the network type, and the target node to help assess interaction latency and route differences.

Complete error details

Prefer copyable error text, the exit code, and the failed step. Before sending logs, redact tokens and sensitive paths.

Reproduction steps

Starting from a known-good state, list the actions, commands, input conditions, and expected results in order, and note whether the issue reproduces every time.

Order ID

Include the order ID when a device is involved, but never send complete passwords, private keys, or remote-control verification codes.

Order management

Manage orders, renewals, devices, and access credentials in the console

For a new order, choose one of the three available configurations, a rental term, a node, and any add-ons. Renewals, billing-cycle changes, device details, and access-credential management for existing orders are also handled in the console. Availability is determined by the console in real time.

Rent a cloud Mac now Manage existing orders

Available configurations: VMOwn M4 Core, VMOwn M4 Plus, VMOwn M4 Pro Max
Available nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US West
Rental periods: Daily, weekly, monthly, quarterly

Payment guidance

Two payment methods, all billed in USD

VMOwn supports only the payment methods below. The payment gateway available to you is determined by the console, and all order totals are settled in US dollars (USD).

USDT-TRC20 Complete the transfer using the information shown for the order and keep the transaction record associated with it.
Visa / Mastercard / Amex Card payments are processed by Stripe. VMOwn will never ask you to send complete card details by email.

Security boundaries

Support will never request sensitive credentials

When troubleshooting connection, build, or billing issues, provide only the minimum information needed to investigate. The support team will never ask you to send any of the following:

Private keys or private-key file contents
Complete account or device passwords
Remote-control verification codes
Complete payment-card details
Unredacted tokens, cookies, or signature material

Response boundaries

Choose the right channel for complete context

Email is best for general inquiries; console tickets are best for existing orders and device issues. Both channels are handled by the support team, but they carry different context.

VMOwn contact channels: use cases and response guidance
Channel	Best for	Recommended information	Initial response guidance
Support email	Pre-sales selection, general technical questions, billing checks, team purchasing, and partnerships	Task type, configuration scale, target node, rental term, and a clear question	Usually within 1 business day
Console ticket	Existing orders, device connections, access credentials, renewals, and order charges	Order ID, time of occurrence, system version, error text, and reproduction steps	Queued according to issue impact and context

Next steps

Once your task details are ready, start the conversation

Send general inquiries to support@vmown.com. For existing orders or device issues, sign in to the console and submit a ticket. Once your configuration is confirmed, proceed directly to checkout.

Rent a cloud Mac now Submit a console ticket