Choosing a configuration or planning capacity for your team? Email us. For an existing order, connection issue, or payment check, open a ticket in the console. Use the right channel from the start.
If you know which configuration you need, you can rent it now without waiting for a reply. Availability is shown in real time in the console.
Email us about your requirements; use a ticket for order-related issues. Please don’t open duplicate requests. Add any follow-up details to your original email or ticket.
Haven’t ordered yet, or need multiple nodes? Tell us what you’ll use them for, how many jobs will run at once, which models you need, how many, and for how long. We’ll confirm the available configurations and delivery plan.
Ask us which to choose: Core or Pro, how to configure extra SSD storage, or how to schedule usage across teams.
support@xcodenode.com
Need help confirming a connection method or toolchain steps? Email us with your client OS, steps to reproduce, and the full error message. Share only relevant logs, with sensitive details removed.
For issues affecting a rented node, open a ticket so we can link it to your order, instance, and support history.
support@xcodenode.com
Sign in to the console and open a ticket. Include the relevant order number or instance ID. Use this channel for unreachable nodes, credential issues, payment checks, and renewals.
Include when the issue started, what’s affected, and what you’ve already checked. Keep follow-up messages in the same ticket.
Track progress in the console
This tool prepares an email draft in your browser; it doesn’t submit a message to our site. Once it’s ready, open your email app or copy the text into your usual email client.
To: support@xcodenode.com
Opening your email app doesn’t send the message. Review it and select Send in your email client. If no email app is set up on your device, copy the body and send it manually.
You can ask about multiple nodes or quarterly billing in one message, but configurations and delivery plans are confirmed for each node. Instead of asking for a “team plan,” start by listing the workloads you actually need to run.
For each node, specify the model, location, rental term, and use case. For example, list build nodes and interactive development nodes separately rather than trying to run every workload on one machine.
Both tiers are dedicated physical machines, not virtual machines. Core comes with M4 / 16GB / 256GB; Pro comes with M4 Pro / 64GB / 2TB. Choose based on the memory your concurrent workloads actually use, not your team size.
Tell us when you’d like to start, which time zone you’re in, and whether delivery can be staggered. We’ll confirm a delivery plan based on each node’s configuration, rather than applying one general timeline to the whole batch.
For extra storage, specify +1TB SSD or +2TB SSD. For Thunderbolt 5 daisy-chaining, include the number of nodes and intended use. Bulk requests don’t change the configurations in the public catalog. The console shows the final amount and available payment options at checkout.
A clear description helps us start troubleshooting right away. Sensitive information won’t speed things up; it only adds risk.
For presales, include the model, location, quantity, and rental term. Existing customers should include an order number or instance ID. For payment questions, name the payment method and transaction reference—never include full card details. We accept USDT-TRC20 and Visa / Mastercard / Amex via Stripe. All charges are in USD.
Explain what you expected to happen and what actually happened. Include the time and time zone, the exact error, and the steps you’ve tried. For connection issues, say whether SSH, the graphical desktop, or both are affected instead of simply saying “the machine doesn’t work.”
Never send passwords, private keys, certificate passphrases, access tokens, or complete project files. Redact secrets, personal data, and internal addresses in logs and screenshots. Don’t put machine credentials in an email subject line.
General inquiries are handled around APAC business hours. Include your time zone in your message. Nodes run 365 days a year; machine uptime and staff reply hours are separate things.
Configuration recommendations, bulk orders, and long-term plans depend on your requirements. We don’t publish a fixed email response time. If you need a reply by a specific date, include your project deadline and time zone so our support team can confirm.
If you haven’t heard back, check your spam folder, then reply to your original email with any updates. Please don’t start a new thread about the same request; it can split the conversation.
If you can’t connect to an instance or your work is blocked, open a ticket linked to your order. Include when the issue started, which nodes are affected, and the results of your connection tests. Unreachable-node issues are prioritized for troubleshooting—not by the number of duplicate tickets.
Opening a ticket doesn’t mean the issue is fixed. Check console replies for confirmation, requests for more information, and progress updates. Keep the original ticket open and add the time you confirmed service was restored.
For connection steps, start with the connection guide. For an existing instance, sign in to the console. Email is for confirming requirements, not placing an order.