Requests are handled in the order received on business days. Please allow 1–2 business days; updates will come by email or ticket. This is not a real-time, round-the-clock service.
Not sure which setup you need? Email us first. For existing orders, use a ticket to keep the issue and node details together.
Our only public contact email is support@armshell.com. For questions about orders, nodes, or payment records, please submit a ticket through the console after signing in.
For teams without an existing order: get advice on Xcode builds, always-on CI, automated testing, MLX experiments, and choosing a node, memory, and storage.
Tell us what you’ll run, how large your team is, and how long you expect to use it. We’ll assess the bottlenecks before discussing a machine—not just go by the project name.
Response time: Please allow 1–2 business days. Complex multi-node requests may need more information.
Prepare a sizing emailFor connection issues, build errors, remote desktop problems, or a disconnected runner on an active node. Keep adding troubleshooting updates to the same ticket.
Sign in to the console and open a ticket. Include your order number and node. If you can’t sign in, email us from your account address and explain the login issue.
Response time: Requests are handled on business days. Please allow 1–2 business days; an initial reply does not mean the issue is resolved.
Sign in to submit a technical ticketFor payments not linked to an order, billing-term checks, renewal records, or invoice questions. Use a console ticket and include the relevant bill so we can look into it—don’t send a screenshot without an order number.
For card payments, include the bill number. For USDT-TRC20 payments, include the transaction hash. We’ll confirm what information is needed and how invoice requests are handled in our reply.
Response time: Please allow 1–2 business days. Payment checks and invoice requests may require additional confirmation.
Sign in to check a billUse the fields on the right to draft an email subject and message in this browser. The button will try to open your email app; it won’t submit a ticket or send an email from this page.
Review the message in your email app, attach any files, then send it to support@armshell.com. If your device has no email app set up, copy the draft below and paste it into the email service you normally use.
Instead of just saying “I need a fast Mac,” tell us whether you build occasionally or continuously, how many jobs run at once, whether you have large caches, and which Xcode versions your project requires. No measurements yet? Just describe your workflow.
Tell us where the main users, code repository, and build artifact destination are located. Node choice isn’t just about proximity: interactive latency and large file transfers may call for different considerations. Availability is shown in real time in the console.
You don’t need to find the root cause first. Just give support enough information to identify the affected system, reproduce the issue, and understand what you’d like to happen next.
For existing orders, include the order number and node. For connection issues, add the time and time zone. For presales questions, tell us your main use case, when you expect to start, and where the users are located. Never send login credentials.
Attach redacted screenshots, commands you ran, and relevant terminal output to your email or ticket. Describe what you expected, what happened, whether it happens every time, and what you’ve tried. “Can’t connect” alone makes it hard to tell whether the issue is with the network, credentials, or your local setup.
For sizing, tell us whether you need the node by the day, week, month, or quarter, and whether you need to keep the work environment available between sessions. For billing questions, include the relevant term. For upgrades or add-ons, share your current and target setups; the console and our reply will confirm the effective time and price.
ArmShell provides dedicated Apple Silicon physical nodes, not virtual machines. Adding nodes and upgrading a node solve different problems. First, let’s understand how your workload is split so you don’t overprovision and still end up waiting in a queue.
Tell us whether you want “each node to run a separate job” or need “Thunderbolt 5 linking.” CI queues typically distribute jobs across multiple nodes. Linking requires details about node count, data flow, software support, and storage needs.
Linking nodes doesn’t automatically combine all memory or compute resources. Share your actual workload first so we can confirm the connection setup and any add-ons. Don’t estimate performance based on the number of devices alone.
Tell us how many people will use the node, their time zones, and whether they’ll be working on it at the same time. Taking turns on one machine has different memory, process isolation, and build scheduling requirements from running builds simultaneously.
Keep personal working directories separate from shared caches, and end unrelated sessions before handing off the node. Don’t share passwords by email. Discuss accounts, permissions, and session schedules in a ticket.
Tell us how long you expect to use the node continuously, your Xcode version, dependency cache size, and backup strategy. A persistent runner needs a stable toolchain and clear renewal plans—not just a fast single build.
The three configurations are M4 / 16GB / 256GB, M4 / 24GB / 512GB, and M4 Pro / 64GB / 2TB, corresponding to Shell M4, Shell M4 Plus, and Shell M4 Pro. Describe your workload before choosing a tier; memory capacity alone does not guarantee performance.
We accept USDT-TRC20 and Visa / Mastercard / Amex through Stripe. No other payment methods are accepted. Available payment gateways are confirmed by the backend.
Start the payment process from the console and check the currency, term, and bill number. Email discussions are not payment instructions. Never send full card details to support.
If the bill status doesn’t match your payment record, add the details to the same ticket rather than sending multiple emails.
Check payment in the consoleOrder → Ticket → Follow up
Sign in to the console, open a ticket, and include the order number, node, and redacted logs. Keep replies and additional information in the same ticket so the troubleshooting history stays complete.