Skip to content
Sales & support

Get in touch—two ways

Still choosing a Mac mini server? Email us about your needs. For an existing node or order, sign in to the console and submit a ticket. Tell us what you’re trying to do and which node you need help with to avoid repeating details.

Email: support@minissh.com. Email and console tickets are the only ways to contact us.

Before you order

Start with your use case and term

Ask us about choosing a region or billing term, or placing a team order. If you have an account, submit a presales ticket. No account yet? Email us directly—you don’t need to rent a node first.

Email works well for detailed requests

Send your email to support@minissh.com. Use “Presales inquiry” as the subject, and include your team’s main locations, use case, estimated number of nodes, and preferred start date.

For example, tell us whether you need remote development, Xcode builds, or app release builds. Let us know if you need extra build capacity temporarily or a node for ongoing use.

Use a ticket for ongoing conversations

Sign in to the console, open the support section, and create a presales ticket. Keep replying in the same ticket if you need to add team size, term, or region preferences, so the context stays together.

Nodes are available in Singapore, Tokyo, Seoul, and Hong Kong. Tell us where your team will connect from. Cross-region performance also depends on your network, not just geographic distance.

Already have a node

Keep instance issues in one ticket

For connection issues, stuck builds, OS reinstalls, or renewal checks, open a ticket in the console. Link it to the relevant node and order so we can address the right issue.

  1. 01

    Identify the node

    Include the node ID and region. For purchases or renewals, include the order number too. Don’t just say “I can’t connect to my Mac,” and never include a connection password or private key.

  2. 02

    Include when it happened

    Give the time and time zone when the issue first occurred, and say whether it’s ongoing or intermittent. If it worked before, include the time of your last successful connection or build.

  3. 03

    Add steps to reproduce

    Describe what you were doing, what you expected, and the error you saw. Include only relevant log excerpts, with tokens, signing credentials, and sensitive business data removed. Back up any files you need before reinstalling the OS.

Orders & payments

For payment checks, include the right details

We accept USDT-TRC20 and Visa, Mastercard, or Amex via Stripe. All payments are settled in USD. Available payment gateways are shown in the console.

USDT-TRC20: Include the transaction hash

In a ticket about the order, include the order number, transaction hash, transfer amount, and transfer time with its time zone. The hash helps us find the on-chain transaction; a wallet balance screenshot alone isn’t enough.

Before requesting a check, compare the payment with the order’s payment instructions. Never share your wallet recovery phrase, private key, or any verification code in a ticket.

We check: order and transaction records

Card payment via Stripe: Include the order number

Include the order number, payment time, and any error shown on the page. If the payment page and console show different order statuses, tell us what each one says.

Never share your full card number, security code, or bank verification code. If the order status is unclear, check it in the ticket for that order. Don’t make repeated payments just to test.

We check: order status and payment message
Working across APAC and North America

Include your time zone to avoid an extra round of questions

“This afternoon” means different things across time zones. Include your UTC offset in emails and tickets, name one primary contact, and keep updates about the same issue in one thread.

Example

“My time zone is UTC+8, and I’m available to check replies from 09:00 to 12:00 local time. A teammate is in North America. Please keep follow-up questions in this ticket; we’ll add updates as we hand things over.”

Your preferred contact hours help us understand how your team works; they aren’t an appointment or a promise of an immediate response. Also include the time zone for when the issue occurred, so it’s not confused with your availability.

Prepare before you send

Draft an email with your details

Fill in the details below to create an email draft addressed to support@minissh.com. This tool doesn’t upload or send your form contents. Review and send the draft from your email app. To track an existing order, sign in to the console and use a ticket.

Enter the name you’d like us to use in our reply.
Enter the expected number of users and whether they’ll need to share access at different times.
List where your team will connect from. For teams in multiple regions, list each one.
Singapore, Tokyo, Seoul, or Hong Kong. Not sure? Write “Please recommend a region.”
Use a UTC offset and local time. Avoid writing only “morning” or “evening.”
At least 10 characters. Include your use case, estimated number of nodes, rental term, or issue. Don’t enter passwords, private keys, payment security codes, or verification codes.

The draft is created on this page only; it isn’t sent to MiniSSH automatically.

Clarify what you need, then choose how to get started

Still working out your use case? Contact us first. Already chosen a region and term? Place your order. Rentals start by the day and stop at the end of the term unless renewed. Check the console for current availability.