Presales, technical support, billing, and team purchasing each require different context. For questions before ordering, send an email. For issues linked to an order, node, or billing record, sign in to the console and submit a ticket.
Sending duplicate emails and tickets will not speed up handling and may fragment the context. Choose one entry point and keep adding information in the same email thread or ticket.
Suitable for configuration advice, node selection, payment policy questions, and team purchasing evaluation. We usually confirm receipt within one business day; complex configurations are reviewed further after requirements are confirmed.
Suitable for connection failures, build issues, node status, renewals, and billing records. The ticket retains the order context, returns an acknowledgment after submission, and provides diagnostic updates based on the issue scope.
Saying only “I need a Mac” is not enough to assess memory, storage, or node requirements. Complete the information below to generate an email to support; the form contents are not submitted to the website server.
For existing orders, submit a console ticket first so the node and billing records can be linked. The form below can generate an email draft for organizing essential details when you cannot access the console.
Team purchasing is not just about node count. Runner tags, concurrent builds, cache directories, storage growth, and deployment regions all affect configuration and management.
VMArm offers five nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West. Both available configurations cover all five regions.
Suitable for Southeast Asian teams, or workloads whose repositories and collaborators are primarily located in the region.
Preselect Singapore nodeSuitable for teams in Japan and East Asia; consider actual connectivity from your local networks to the node.
Preselect Japan nodeSuitable for teams in South Korea and Northeast Asia; verify connection quality from your usual office networks first.
Preselect South Korea nodeSuitable for collaboration across South China and Southeast Asia, helping accommodate developers in multiple locations.
Preselect Hong Kong nodeSuitable for teams on the North American West Coast and projects whose repositories, build services, and primary collaborators are in North America.
Preselect US West nodePrioritize the node closest to your main operators and code repositories. If your team spans multiple regions, include the primary access locations, repository location, and peak build hours in your email.
All charges are settled in USD. We support USDT-TRC20 and Visa, Mastercard, and Amex processed through Stripe. Actual gateway availability is shown in the console in real time.
When asking about a transaction status, provide the related order and a redacted transaction identifier. Do not send wallet keys or other sensitive credentials.
Card payments are processed through Stripe. For billing issues, submit a ticket linked to the order in the console so the payment status can be checked.
Before sending an email or ticket, remove keys, signing private keys, access tokens, complete connection credentials, and other sensitive data. Crop unrelated account information from screenshots, and retain the surrounding error context in logs while replacing sensitive values.
Connection, configuration, billing, ordering, and order management each have a clear entry point. Completing the basic checks first helps your email or ticket move directly to the next step.
First check the node address, client fields, network, resolution, keyboard mapping, and reconnect path.
Read the remote connection guideReview the two available models, four billing terms, additional storage, Thunderbolt 5 linking, and node coverage.
View common questionsSelect the model, term, node, and add-ons in the configuration flow. Actual availability is returned by the console in real time.
Start the ordering processFor an existing order, sign in to the console to view order, billing, and node information, and continue adding diagnostic materials to the original ticket.
Sign in to the consoleBefore ordering, review the plans first. For existing orders, submit a console ticket and preserve the complete handling context.