Choose a contact route

Put your issue in the right hands

For pre-sales planning, describe your workload by email. For orders, billing, or issues with a running node, log in to the console and submit a linked ticket for faster verification. Partnership inquiries also go to the shared support address.

Email support Log in to submit a ticket

Use the same subject for both channels and keep adding information there so the support team has a complete record.

CONTACT ROUTE

Choose an entry point by issue type

Two channels
A

Pre-sales configuration advice

By email, describe your project type, concurrent tasks, storage needs, duration, and preferred node.

Email
B

Orders and billing

For existing orders, submit a linked ticket first and include the order number and relevant billing period.

Console
C

Connection and build issues

Include the node, time of occurrence, symptoms, and any necessary redacted logs.

Console
D

Partnership inquiries

Describe the partnership scope, expected use, and the points you need to confirm.

Email
Structured email

Organize the details before opening your email client

This tool does not submit anything to the website backend. After you complete it, it creates an email addressed to support in your system email client. You can still review, edit, and add necessary redacted attachments before sending.

REQUEST SHEET

Contact and issue details

Email draft

Describe your goal, current symptoms, checks already completed, and the specific points you want the support team to confirm.

Required fields include your name, contact email, issue type, and issue description.

Good reasons to email us

Configuration assessments, rental-period planning, preferred-node selection, and partnership-scope confirmation before placing an order. We recommend discussing one clear topic per subject.

Initial confirmation
Within 1 business day
Email us directly

Good reasons to submit a console ticket

Order status, billing records, connection details, or issues with a running node. Linking the order helps the support team spend less time verifying basic information.

Prepare
Order number, node, and time of occurrence
Processing order
Routed by impact and information completeness
Log in and submit a linked ticket
Security check before submitting

Redact logs, never send credentials

The support team typically needs reproduction conditions, error context, and a time range. Removing sensitive fields unrelated to troubleshooting does not reduce a ticket’s value; it reduces follow-up cleanup.

01

Narrow the log scope

Capture the necessary lines before and after the error, keeping the timestamp, command stage, exit status, and relevant module names.

02

Replace sensitive values

Replace usernames, private portions of repository addresses, tokens, and internal paths with clear redaction markers.

03

Preserve the issue context

State whether the failure occurred during graphical connection, command-line use, dependency installation, compilation, archiving, or artifact export.

04

Send only necessary attachments

Attach only the redacted logs or screenshots needed for troubleshooting from your system email client. Do not send the full project directory or unrelated data.

Pre-sales information checklist

Five groups of details are enough for the first recommendation

Not sure whether to choose ArmVMS M4 or ArmVMS Pro (M4 Pro)? You do not need to guess the configuration first. Describe your actual workload using the fields below, and the support team can recommend one of the two available configurations.

01

Project type

Tell us whether it involves iOS, macOS, visionOS, CI/CD jobs, remote development, or AI experiments, and list the main toolchain.

02

Concurrent tasks

Provide the number of builds, tests, or inference tasks running at the same time, and whether they need to run continuously for extended periods.

03

Storage needs

Estimate the size of your code, dependency caches, build artifacts, and model files, and indicate whether you need +1TB SSD or +2TB SSD.

04

Rental period

Tell us whether the work will run for days, weeks, or months so you can choose from daily, weekly, monthly, or quarterly terms.

05

Preferred node

Choose among Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US East, and share the approximate locations of your team and code sources.

Two available configurations

If you are unsure, describe the workload first—no need to choose a model yet

ArmVMS M4 includes M4, 16GB memory, and a 256GB SSD for lightweight builds and everyday development. ArmVMS Pro (M4 Pro) includes M4 Pro, 64GB memory, and a 2TB SSD for larger projects and large-model inference.

View complete rental plans
Response and additional materials

Keep the confirmation details and continue in the same thread

Creating multiple requests with the same content splits the incident timeline. After receiving confirmation, reply to the original email or add materials to the original ticket, keeping the subject, order number, and node fields.

Support email Within 1 business day

Initial confirmation

The support team first confirms the issue category and whether the information is complete. If more details are needed, the missing fields will be listed in the same email thread.

Console ticket Routed by impact

Enters the processing queue after the order is linked

Issues such as connection interruptions, order status, or billing records are routed based on their impact and the information submitted.

Additional materials Continue in the original thread

Do not create the same request again

When adding logs, screenshots, or reproduction results, reply to the original email or update the original ticket to keep the record continuous.

If the issue affects a running task, begin the subject with “Running node” and provide the order number, node, time of occurrence, impact, and redacted error details.

Ready to get started

No order yet? Email us. Existing order? Submit a linked ticket.

Choose the route that matches your current stage and submit all required details at once. The support team will continue handling the request in the same thread.

Configure a rental order Log in to submit a ticket