Haven’t ordered yet? Tell us about your model size, concurrency needs, or build tasks, and we’ll help you choose the right dedicated physical Mac mini. Already have an order? Sign in to the console and submit a ticket for technical issues or payment checks so we can link it to your node and order.
For pre-sales email, just describe your task. For existing orders, include the order number if possible. Never send passwords or keys by email.
First, where are you in the process?
You don’t need an order number for pre-sales questions. For an active machine, submit a ticket through the console so our team can check the instance and billing records.
Include the model’s quantization, expected concurrent requests, or the number of Xcode build and CI jobs you run in parallel. We can then help you compare XOps 16, XOps 24, and XOps Pro 64. Whether a model can stay loaded depends on its actual weights and context length.
If SSH won’t connect, the VNC display is abnormal, an MLX endpoint isn’t responding, or a runner build fails, sign in to the console and submit a ticket for the relevant order. Include when it happened, which node was affected, steps to reproduce, and sanitized error details. Avoid reporting only “can’t connect.”
If you need us to check a USDT-TRC20 transfer or a Visa / Mastercard / Amex payment (via Stripe), submit a ticket through the console with your order number, amount, and payment reference. Never share your full card number, verification code, or wallet private key. All orders are billed in USD.
Fill in the fields below to create an email in your default mail app addressed to support@xcodeops.com. This page doesn’t upload or store your entries. Review the recipient and message in your mail app before deciding whether to send it.
Our support team handles inquiries during Asia-Pacific business hours. For existing orders, submit a console ticket so we can link your issue directly to the order and node—usually faster than confirming your details by email. These are targets for the first reply, not a guarantee that the issue will be resolved by then. Troubleshooting time for complex issues depends on the logs and reproduction steps available.
During Asia-Pacific business hours, we aim to reply within 4 hours for the first response
We aim to reply within 1 business day for the first response
Keep the original error message, then describe what you’ve tried
“I asked about my model size by email and got a tier recommendation in ten minutes.”
— AI startup engineer
“I submitted a billing ticket with my order number, and it was sorted out the same day.”
— CI platform maintainer
These quotes are illustrative. Actual first response times depend on the queue and the details of your issue.
Not sure which machine to choose? Start with an email. For an existing order, open it in the console and submit a ticket.
Include your use case, model or build workload, preferred node, and expected rental period. If the email address is difficult to enter, copy it into your mail app.
Draft a pre-sales emailSign in, select the relevant order, and submit a technical or billing ticket. Include the node, time of issue, and order number. Don’t send account credentials by email.
Sign in to submit a ticketWant to troubleshoot it yourself first? Read the Connection and deployment guide, FAQs, or check Plans and pricing for specifications and billing periods.
Choose from three dedicated physical Mac mini tiers to match your workload and rental period. Check real-time node availability in the console when you place your order.