01
Pre-Sales Consultation
Use this for comparing three models, five regions, four rental terms, and published add-ons. Include your workload, concurrency, and expected rental period.
Contact Support
Clear context gets every support conversation moving
Whether you need to confirm a configuration, troubleshoot a connected host, or review rental and billing details, you can contact ArmCLI. Select a topic and include the model, region, time, and steps already tried.
Our only external contact channels are support email and console tickets. Never send unredacted passwords, private keys, tokens, or complete connection credentials by email or ticket.
Route Request
ARMCLI / SUPPORT
02
Issue with an Active Host
For connection drops, credential status, disk space, or build failures, sign in to the console and open a ticket from the relevant order.
03
Rental & Billing Questions
Include the order ID, current expiry time, preferred rental term, and payment method. Do not send complete payment credentials or sensitive screenshots.
Support Email
support@armcli.com
Email Builder
Submit enough information to diagnose the issue
This form does not send data to the website server. When finished, it creates a draft addressed to support and hands it to your system mail app.
Technical Details
Provide six pieces of context in troubleshooting order
Do not write only “cannot connect” or “build failed.” The details below help Support determine whether the issue is local networking, the remote session, system resources, or the build toolchain.
01
Time of Incident
State the time zone and approximate duration, such as “UTC+8, 14:20–14:35.” Avoid native date controls or vague terms like “just now.”
02
Node Details
Provide the region, model, and a redacted order ID. Include only the host address fragments needed for troubleshooting; do not submit complete connection credentials.
03
Connection Method
Specify whether you use SSH or VNC, and whether the issue occurs during connection setup, authentication, session persistence, or reconnection.
04
Commands and Versions
Include reproducible commands, the Xcode or Fastlane version, runner labels, and the working directory. Do not paste complete environment variables containing tokens.
05
Error Summary
Keep the first useful error, exit code, and key stack trace. Remove certificate contents, private keys, access tokens, email addresses, and business data.
06
Steps Already Tried
List connections retried, caches cleared, disk space checked, and permissions reviewed so Support does not repeat the same steps.
Pre-Sales Guidance
Recommendations are based on the current catalog
Support will explain differences based on workload and budget, but cannot add models, regions, or payment methods outside the catalog. Actual availability is determined by the console in real time.
Three Models
Start with memory, storage, and concurrent workloads
ArmCLI M4 S includes M4, 16GB, and 256GB; ArmCLI M4 L includes M4, 24GB, and 512GB; ArmCLI M4 Pro X includes M4 Pro, 64GB, and 2TB.
Single-project development, parallel builds, multiple runners, and AI experiments require different resource headroom.
Five Regions
Choose a node based on team networks and workload location
The current catalog covers Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East. Remote performance depends on the user's local network, routing, and connection method.
Include your primary city and connection method so we can identify which region to test first.
Four Rental Terms
Choose daily, weekly, monthly, or quarterly based on certainty
Start short-term validation with a daily or weekly rental; compare monthly or quarterly terms for stable pipelines. Also provide your delivery date, peak concurrency, and any extra storage needs.
Pricing and configuration are defined on the rental plan and order confirmation pages; temporary quotes are not issued by email.
Response & Billing Facts
Confirm the context first, then get a clear path forward
General questions are handled in the order received; instant replies are not guaranteed. Complex networking, remote sessions, or build issues may require redacted logs or step-by-step validation after the first reply.
Support email is best for pre-sales questions
Emails enter the queue in the order received. Include the issue type in the subject and the model, region, rental term, and workload in the body. If key context is missing, Support will request it before advising or troubleshooting.
Email SupportConsole tickets are best for existing orders
Tickets can link the host, rental term, and service records. Continue adding information to the same ticket rather than creating multiple requests for the same issue. Resolution time depends on reproducibility and the logs required.
Sign In to Open a TicketBilling channels stay fixed
We support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), with all charges settled in USD. Available gateways are confirmed during checkout.
For billing questions, provide a redacted order ID and payment status. Do not send complete card details, wallet keys, or usable payment credentials.
Have an order? Start a ticket from its record
The console keeps host, rental, and service records together for ongoing technical and billing support. If you have not ordered yet, start the configuration flow to choose a model, region, and rental term.