Plan selection
Tell us about your workflow, preferred region, model, rental term, and target start date so we can check your setup in one go.
- Best for
- First-time rentals and comparing configurations
- Required
- Workload and preferred region
Contact support
Describe the issue first, then include the details we need
For pre-sales questions, send a structured email. For existing orders involving connectivity, builds, inference, or billing, sign in to the console and submit a ticket. Email and console tickets are our only contact channels.
Technical support
For an existing order, include the order ID, node region, OS version, impact, reproduction steps, and redacted logs.
- Priority based on
- Impact and reproducibility
- Credentials
- Never include them in emails or attachments
Bulk requests
Tell us how many nodes you need, concurrent tasks, delivery schedule, storage expansion, and any Thunderbolt 5 daisy-chaining requirements.
2 models · 6 regions
Billing questions
Include the order ID, payment method, payment time, and records to review. Never send full card details or payment keys.
USD charges are reviewed against each order
Request routing
Choose the closest request type
All four request types remain visible. Selecting one takes you to the relevant checklist without hiding other options. If a request involves both configuration and an issue, choose based on whether you already have an order.
Pre-sales inquiry
Turn your workflow, region, and capacity needs into a configuration brief
This form does not submit data to the website. When you finish, the page creates a request summary and an email to support@armmesh.com. Review and send it from your email app.
Support for existing orders
Describe issues with timestamps, impact, and reproduction steps
For existing orders, console tickets automatically include account context and are generally better for ongoing troubleshooting than email. Use the form below to create a redacted summary, then copy it into a console ticket or email.
Six available regions
Choose a region based on access patterns, repository location, and artifact delivery
ArmMesh M4 and ArmMesh M4 Pro are available to order in all six regions. Check the console for real-time availability. When you contact us, include your team’s location, code repository location, and where your artifacts need to go.
Singapore
A good fit for Southeast Asian teams and workflows with repositories, artifact storage, or APIs primarily located in Southeast Asia.
Include: main access cities and upload direction
Japan (Tokyo)
Ideal for users in Japan and Northeast Asia, especially teams that need responsive graphical interactions and continuous code synchronization.
Include: share of interactive work and repository location
South Korea (Seoul)
Suitable for access from South Korea and nearby areas, as well as remote development, build queues, and automation for Northeast Asia.
Include: concurrent task count and access hours
Hong Kong
Useful for collaboration between South China and Southeast Asia. Include details about your local network, repository, and artifact delivery route.
Include: data flow and file sizes
US East
Well suited to CI, artifact processing, and non-interactive MLX API workloads serving eastern North America and Western Europe.
Include: service callers and build queue location
US West
A good fit for teams on the US West Coast, code hosting, and artifact services, with convenient cross-time-zone handoffs for teams in Asia.
Include: handoff hours and main access cities
Region recommendations aren't based on distance alone.
Graphical interactions depend more on round-trip latency; CI/CD depends on repository and artifact routes; and MLX API workloads also depend on request origin and model file synchronization. Read the remote access guide, then share your actual conditions in an email.
Response times
Complete details help us make progress in our first reply
These are typical response targets, not automated acknowledgments. Complex issues may require more logs or verification. The clearer the impact, the easier it is to route your request correctly.
We’ll review your workflow before recommending a model and region
We first check that your workload, concurrency, region, rental term, and add-ons are clear. Our typical target is to provide initial recommendations or follow-up questions within 1 business day.
To get a faster response
Include your start date, node count, and typical task duration
We’ll assess the impact, then investigate using your reproduction steps
Console tickets automatically include order and node context. For requests with a clear impact and reproducible steps, our typical target is initial triage within 4 business hours.
To get a faster response
Include the time, time zone, OS version, and redacted logs
We’ll check each order against its payment status and records
Include the order ID, payment method, payment time, and records you want us to review. Our typical target is to confirm the status or explain what else we need within 1 business day.
To get a faster response
Avoid opening duplicate tickets; continue the discussion in the original one
For urgent issues, clearly explain the impact
Tell us how many nodes and tasks are affected, whether work is fully blocked, whether there is a workaround, and when it last ran successfully. “Urgent” alone doesn't give us the details needed to diagnose the issue.
Data minimization
Run these three privacy checks before sending
Contact information is used only to identify and respond to requests, link orders, troubleshoot issues, and retain necessary handling records. Don’t attach project files or personal data that aren’t relevant just to make your request seem more complete.
01
Include only what’s needed
For pre-sales requests, include your workflow and capacity needs. For technical requests, include the order ID, version, time, impact, and relevant error context.
02
Remove sensitive information
Remove passwords, keys, tokens, signing materials, source code snippets, customer information, and details that identify unrelated people.
03
Review the summary before sending
Check each item in the summary generated on this page. Confirm the recipient is support@armmesh.com, then send it from your email app.
For details about processing purposes, retention, deletion, and your rights, see our Data Privacy Policy. To access, correct, or delete contact information, or restrict its processing, contact us at support@armmesh.com or through a console ticket.
Next steps
Model and region decided? Configure your order
Both models are dedicated physical nodes with Apple Silicon, not virtual machines. When ordering, choose a rental term, one of six regions, and any add-ons you need. Check the console for real-time availability.