Contact routing
For pre-sales selection and general questions, email us. For order-linked issues affecting your cloud Mac, sign in to the portal and submit a ticket for faster handling. Prepare the model, node, timestamp, and reproduction details first. Never submit passwords, private keys, or unredacted certificate contents.
Best for pre-sales selection, enterprise requirements, and general questions that do not depend on real-time order status.
support@armmacs.comBest for active-rental incidents, order status, billing records, and issues requiring ongoing progress tracking.
Open the portalPre-sales selection
“I need a Mac” is not enough to identify the right tier. In your email, describe the workload, rental term, resource requirements, target node, and concurrency so our team can recommend a fixed configuration directly.
Tell us whether you need Xcode builds, iOS/macOS CI/CD, a self-hosted Runner, VNC remote desktop, MLX experiments, or GPU Mac rendering. Include your main Xcode version, build frequency, typical job duration, and whether you need a graphical interface.
Specify whether you expect to use the service by the day, week, month, or quarter, and provide minimum memory and storage requirements. Current fixed tiers are Pulse M4 16GB/256GB, Vector M4 24GB/512GB, and Apex M4 Pro 64GB/2TB.
Choose your preferred node from Singapore, Tokyo, Seoul, Hong Kong, or the US West. State the number of builds, tests, or Runners running at the same time; do not substitute team size for actual concurrency.
Pre-sales selection | Xcode CI | 24GB memory | Tokyo | 2 parallel jobs | 1-week rental
Team requirements
Enterprise inquiries should cover who will use the service, how teams will connect, who manages access, and when you plan to purchase. Resources remain subject to fixed configurations, available nodes, and inventory shown in the portal.
Provide the number of developers, CI/CD engineers, and administrators. Distinguish roles that need remote desktop, command-line access, or pipeline-only access.
Tell us whether you use GitHub Actions, GitLab CI, or a custom scheduler. List Runner labels, concurrent jobs, cache directories, and how build artifacts are returned.
Explain who receives credentials, assigns access, cleans up work data, and handles renewals. Also include your expected order date, rental term, and internal approval milestones.
Technical support
Submit active-rental connection, build, Runner, or storage issues through a portal ticket. Once linked to an order, the ticket can track additional details and progress over time.
Copy it from the order details in the portal. Do not provide only the payment time or model name.
For example, Vector M4, Tokyo. Do not replace cloud Mac node details with the name of a local device.
Provide a timestamp with its time zone and state whether the issue is continuous or intermittent.
List the connection method, commands, pipeline stages, and actual results in execution order.
Describe the status, artifact, or exit code you should see under normal conditions.
Keep error codes, timestamps, and relevant context. Remove tokens, private keys, passwords, and certificate contents.
Order number: ID shown in portal order details
Model: Vector M4
Node: Tokyo
Time: 2026-08-08 14:32 UTC+8
Connection: SSH
Issue: Build job exited during dependency resolution
Reproduction: Step 3 after running the pipeline job failed
Expected: Dependency resolution completes and compilation begins
Logs: Tokens, keys, and certificate contents removedBilling questions
Use a portal ticket for billing questions and select the relevant order. This lets us verify the order period, payment status, renewal history, and available payment gateway directly.
All plans, add-ons, and orders are billed in USD. Keep the original order amount and transaction time when contacting us; do not submit a self-converted amount.
Include the order number, transaction time, and a verifiable transaction identifier. Never send wallet private keys, recovery phrases, or complete access credentials by email or ticket.
Card payments are processed by Stripe. Actual gateway availability is determined by the result shown in the portal. For support, provide only the order number, time, and amount—never complete card details.
Order number, payment method, USD amount, transaction time, and current portal status. For duplicate records or an unchanged status, attach a redacted screenshot that preserves the time and status text.
Email composer
The following content is used only to create a draft in your local email app; nothing is uploaded on this page. For active-rental incidents, orders, or billing status, we still recommend signing in to the portal and submitting a linked ticket.
Response queues
The first response confirms whether the information is complete, schedules the next checks, or requests additional materials. Complex issues may require several rounds of reproduction; complete context is usually more effective than resending the same description.
| Issue type | Recommended route | Target first response | What to include |
|---|---|---|---|
| Active-rental incident | Portal ticket | Within 4 hours | Order number, node, timestamp with time zone, reproduction steps, and redacted logs |
| Pre-sales selection | Support email | Within 1 business day | Development task, rental term, memory, storage, node, and concurrency |
| Enterprise requirements | Support email | Within 1 business day | Team roles, CI/CD platform, node preference, access controls, and purchasing timeline |
| Billing question | Portal ticket | Within 1 business day | Order number, USD amount, payment method, transaction time, and current status |
| General inquiry | Support email | Within 2 business days | Clear background, expected decision, and specific conditions to confirm |
Sign in to the portal, select the relevant order, and submit a ticket. Put “cannot connect,” “build failed,” or “order status” in the subject, and include the incident time, node, and most recent successful time in the body.
Final review
Accurate email, node, and timing details determine how quickly an issue can be matched. Sensitive credentials do not help diagnose problems and should be removed before sending.
Confirm the address is spelled correctly and can receive follow-up questions and resolution updates.
Use the full name of Singapore, Tokyo, Seoul, Hong Kong, or US West, and include the model as well.
Record both the incident time and the most recent successful time. Avoid writing only “just now” or “today.”
Remove passwords, private keys, access tokens, recovery phrases, and certificate contents. Keep only error codes and necessary context.
Choose the right route
Send pre-sales and enterprise inquiries to support@armmacs.com. Link tickets to the relevant order and include the node, timestamp, reproduction steps, and redacted logs.