Contact

Tell us what you need in a clear, concise summary

Still choosing a configuration? Email us first. If you already have an order, submit technical issues through the portal. Tell us what you’re trying to do, where you need your machine, and what’s getting in the way. That lets us start with the specific issue instead of asking you to explain the background first.

Not sure what to write? Use the summary builder below. Your details are put together on this page; sending the email is still handled by your email client.

Choose a channel

Ask about a configuration by email; include your order for support

Our only contact channels are the support email and portal tickets. You can submit either at any time. Receipt time does not determine when a support agent will reply, and we do not promise a fixed response time.

Before renting

Pre-sales questions

Ask about configurations, storage upgrades, team quantities, or your expected rental term. Tell us which tools you plan to run, how many tasks will run in parallel, and roughly how much disk space your project currently uses.

When to contact us
Email us any time.
What to expect
We’ll review your requirements and reply to your email. If we need more information about your workload, we’ll ask in the same thread.
Email us about a configuration
Existing orders

Technical support

For connection issues, build environment problems, or help using an instance, sign in to the portal and open a ticket. Include your order number and the relevant instance so we can check the details of your setup.

When to contact us
Submit a ticket through the portal any time.
What to expect
We’ll post updates in the original ticket. Reply to that ticket with any logs or details so the issue stays in one place.
Submit a ticket in the portal
Payments & invoices

Billing questions

For payment checks, billing, or invoices, include your order number, payment method, amount, and payment date. If you have an account, please link the order in a portal ticket.

When to contact us
Email us or submit a ticket any time.
What to expect
We’ll check the order and payment records before replying. Keep your original payment receipt and don’t pay again while waiting for a response.
Email us about billing

Support email: support@gnumac.com. Never include your password, private keys, verification codes, or full payment card details in an email or ticket.

Summarise your request

Prepare your summary, then open your email

This is not an online submission form. Once your draft is ready, review it and select “Open email app.” You can then confirm the recipient and message before sending. For technical issues with an existing order, use the summary as the body of your support ticket.

Tell us which tools and tasks you’ll run. You don’t need to choose a configuration yet. If you’ve already chosen one, include its full name in your message.
Preferred location Required
Choose based on where most users are and the network conditions they’ll have. If you’re not sure yet, tell us where your team is based. You can select a location when you place your order.
Planned rental term Required
This records your plans only; it won’t create a subscription or trigger a charge. Include your expected start date and project deadline in your message if relevant.
Enter a whole number from 1 to 999. If you need machines in multiple locations, list the quantity for each one in your message.

This step just captures your requirements

It doesn’t reserve a configuration, confirm a delivery time, or replace placing an order. Check the portal for current availability and payment options.

20–2,000 characters. You can paste a short error message after removing sensitive details. Don’t include keys, access tokens, or full logs containing customer data.
Have an order? Submit a ticket

Your draft will appear here once it’s ready. No email has been sent yet.

Before you send

Include these four details to avoid follow-up questions

You don’t need an order number for pre-sales questions. For support, include enough information to identify the specific instance. A single, complete message is easier to follow up on than several short emails.

  • Name the configuration

    For example, GNU Core M4 (M4 · 16GB RAM · 256GB SSD) or GNU Studio M4 (M4 · 24GB RAM · 512GB SSD). If you haven’t chosen one yet, just tell us which tools you’ll use, how many tasks will run in parallel, and how much disk space you need.

  • Specify the location

    Choose Singapore, Tokyo, Japan, Seoul, South Korea, or Hong Kong. If you need machines in more than one location, give the quantity for each instead of saying “Asia-Pacific.”

  • Include your order number for support

    Copy the relevant order number from the portal and include the instance name. For payment questions, add the billing reference. You don’t need to share your account password to verify that the order is yours.

  • Describe the steps and timing

    Explain what you did, what you expected, and what happened instead. Include the time and time zone. For connection issues, also tell us which client operating system and connection method you’re using.

Multiple machines & long-term use

Send your machine list and project schedule together

Team requirements involve more than just the number of machines. Tell us what each one will be used for, what data it will store, and when you expect to finish. That helps us determine whether one configuration will work for everyone or different workloads need different options.

Considering quarterly billing? Start with your workloads

We offer four billing periods: daily, weekly, monthly, and quarterly. For a long-term project, review the quarterly options first. Before choosing a longer rental term, make sure you’ve considered your tool versions, storage needs, and the team’s actual usage patterns.

In your email, list the number of machines for each configuration, preferred location, planned start date, expected rental term, and whether you need an additional +1TB SSD or +2TB SSD. Your order details will confirm the final configuration and price. An enquiry does not commit you to a payment.

Compare configurations and prices

Planning a Thunderbolt 5 connection? Tell us why

Thunderbolt 5 connections between multiple machines are billed per machine. Tell us how many machines are involved, which tools you want to run, and whether the goal is data transfer, collaboration, or an app’s own multi-machine computing features.

A physical connection won’t automatically distribute tasks or combine memory across machines. First check whether your software supports the multi-machine workflow you have in mind, then discuss the connection setup and any additional items you may need.

Email us about connecting machines
Payment checks

Two payment methods, billed in USD

We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. All payments are settled in US dollars (USD). Check the portal for currently available payment options.

USDT-TRC20

Follow the network, payment details, and amount shown on the order payment page. If you’re checking on a payment, include your order number, transaction hash, transfer amount, and date so we can match it to the on-chain record.

Don’t rely on a wallet screenshot alone to confirm that an order is complete. Check the payment status in the portal first. If you’re unsure, keep the original transaction record and follow up in the same ticket.

Visa / Mastercard / Amex

Card payments are processed by Stripe. For payment or invoice questions, include your order number, billing reference, payment amount, and date, and explain what you’d like us to check.

Never send your full card number or security code by email. Check the payment status and available billing information in the portal first, then add any further details to the original ticket.

Know what you need? Start with one machine.

Choose from two dedicated physical Mac mini configurations across four Asia-Pacific locations. Match the configuration to your workload, or send us the summary above if you’d like help deciding.