Our engineers handle both email enquiries and support tickets. Still choosing a model? Email us. Need help troubleshooting an existing order? Sign in to the console and submit a ticket.
Start with your goal, then include relevant setup details and logs. Never send passwords, private keys, or full payment card details.
Tell us about your workload, expected rental period, and number of concurrent tasks. Our engineers can recommend a model, storage expansion, and location based on your actual needs—not just a project name.
If you can't connect to a location, a build fails, or your remote desktop is acting up, submit a ticket through the console. Include your order and the issue in the same ticket so we can investigate from start to finish.
For questions about a payment, order total, or invoice details, email us. If you have an existing order, you can also use a console support ticket so we can link your payment record.
For all enquiries, email support@armvnc.com. Use this address for business enquiries, security reports, and compliance documentation requests, too.
Fill in the form to create an email, then send it from your own email app. The draft is prepared in your email app; it does not automatically create a support ticket. For technical issues with an existing order, use the console instead.
Fields marked “Required” must be completed. You can leave the location and model as “Not decided”—you don't need to choose before getting in touch.
The email will be addressed to support@armvnc.com. Opening your email app only prepares a draft; you'll still need to confirm and send it there. If you don't have an email app configured, copy the text and paste it into an email yourself.
Planning a multi-host setup takes more than a machine count. Share task requirements, resource usage, and data flows. For parallel workloads, tell us which tasks can be scheduled independently and which need to communicate across machines.
Tell us how many runners will operate at once, how long each archive takes, your peak build hours and time zone, and your expected rental period. Let us know whether each host will run one task or several builds in parallel. Include current cache and artifact usage so we can discuss memory and disk headroom.
Specify the number of hosts, target model, connection purpose, and expected data transfer volume. Thunderbolt 5 linking is an add-on charged per host; it does not automatically combine memory or GPU resources. Task distribution and software compatibility also need to be confirmed.
Tell us where your team is based, where your code repository is hosted, how builds are triggered, and where artifacts need to go. Available locations are Singapore, Tokyo, Seoul, Hong Kong, and US East. For runners in different locations, define task labels, cache policies, and how artifacts will be handed off.
Both models are available in all 5 locations. Check the console for current availability. You don't need to share repository access for an initial quote; a redacted workflow description and resource usage details are enough to get started.
We prioritize issues where a location is unreachable. Model selection, configuration questions, and billing enquiries are handled in queue. The contact method itself doesn't determine priority; the impact and the details needed to reproduce the issue matter more.
Ticket updates are added to the original ticket, and email enquiries receive email replies. If we need more information, reply in the same thread and include any confirmed setup details and steps to avoid repeating yourself.
Include the time zone when reporting an issue. For example, “Started at 14:10 local time, lasted about 15 minutes, UTC+8” is more useful than “couldn't connect this afternoon.”
Sign in to check ticket statusCopy these fields into your ticket. Redact command output and screenshots before attaching them.
Order number:
Location code / instance ID:
Issue start and end time:
Time zone:
Impact:
Connection method / build command:
Expected result:
Actual error:
Steps already tried:If you can't sign in to the console, email support with a description of the login issue and your account email address. Never send your account password or verification code.
Make sure you select the TRC20 network. To help us verify a payment, provide the order number, transaction hash, amount, and transfer time. Check the console for payment receipt and confirmation status.
Our engineers can investigate using the transaction record; we never need your wallet private key or recovery phrase.
Card payments are processed by Stripe. For billing questions, provide the order number and a redacted receipt. If the amounts don't match, include both the order total and the amount shown on your receipt.
Never send your full card number, security code, or card verification code by email or support ticket.
Both payment methods are settled in US dollars (USD). Available payment options depend on the response from the payment service. Contact us by email or through a console support ticket to verify invoice details.
Rent an exclusive Apple Silicon physical host, not a virtual machine. Rentals start at one day, from $21.2/day. Choose your rental period, location, and add-ons when you place your order.
We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. All charges are in USD.