Advice for distributed teams

Tell us where your team is based

Start with your team members' locations and working hours, then we can discuss which region best suits your Mac. Haven't ordered yet? Email us with your questions. Already have an instance? Sign in to the console and submit a ticket so the issue stays linked to your order.

Choose a region Prepare an enquiry

We offer two contact channels: email and console tickets. The fields below help you prepare an email on this page; you review and send it yourself.

Before you order

Start your first email with your team's locations

Tell us who will use the Mac, where they will connect from, and what they need to do. This form does not create an order or send anything to our servers. Once your email is generated, review the message and send it from your own email account.

Where does your team work?

Team's primary region Required
List cities, team size, and local working hours. You don't need to include names, personal addresses, or login credentials.

Which configuration do you need, and for how long?

Configuration Required
Expected billing period Required

Not sure which configuration to choose? Pick one as a starting point and describe the size of your workload in the notes. This isn't a confirmation or a reservation.

What will you use this Mac for?

Main tasks Select at least one
Don't include passwords, private keys, full card numbers, or project certificates. Region recommendations are based on team locations and workload; they aren't measured connection results.

Complete the required fields to generate an email. Nothing is sent automatically, and drafts aren't saved.

Write an email

Already ordered

Keep instance issues in one support ticket

For connection failures, unexpected behaviour, renewals, or billing questions, sign in to the console and submit a ticket. Tickets can be linked to your account and order. If you need to add more information, reply to the original ticket so we can review the full history.

  1. 01

    Include the instance and region

    Provide the instance ID and the region shown in the console. If more than one instance is affected, list each one rather than saying only, “I can't connect to my Mac.”

  2. 02

    Include the time and time zone

    Note when the issue started and ended in local time, and include the time zone. If it's still happening, say “ongoing.” For teams in different regions, convert times to a single time zone.

  3. 03

    Describe how to reproduce it

    Tell us what you did, what you expected to happen, what actually happened, and what you've already tried. Redact credentials and unrelated personal information from screenshots. Never send passwords or private keys.

Sign in to submit a ticket

Tickets are handled in the order received. We don't publish guaranteed first-response or resolution times. If anything changes, add the update to your existing ticket rather than submitting another one.

Not sure which region to choose?

Get a region recommendation based on your team and workload

List your team's cities under “Team locations and working hours” above, and ask for a region recommendation in the notes. We'll suggest a region and explain why, based on where your main users are, how often they use graphics-intensive apps, and when team members hand off work. We don't make latency guarantees without measurements.

Frequent graphical interaction

Prioritise the locations of the people who will actively use the desktop. Distance is only a starting point; performance also depends on your local network, routing, and connection stability.

In your email: who uses the desktop, and from where?

Builds and file transfers

Include where your code and files come from, how builds are triggered, and who needs the outputs. Whether tasks can run unattended and how data moves between locations also affect the choice.

In your email: where does the work come from, and where do the results go?

Handoffs between APAC and North America

Tell us whether your teams' working hours overlap. We can consider sharing one instance in shifts or renting separate instances in nearby regions; each option calls for a different data handoff plan.

In your email: share one Mac or use separate instances?

Available regions: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West Coast. Check the console for real-time availability. To change regions, you'll need to create an instance in the new region and migrate your data; an existing instance can't be moved directly between regions.

Add team locations

Payments and billing

Check the transaction before reporting a payment issue

We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), with all charges in USD. Available payment gateways are determined by the response from our backend. Before paying, check the amount and billing period on the order page.

USDT-TRC20 transactions

In your console ticket, include the order reference, amount, transaction hash, and transaction time with its time zone. If the payment page status doesn't match the transaction record, attach screenshots of both.

Never share your wallet recovery phrase, private key, or authorisation keys.

Card transactions

Include the order reference, transaction time, amount in USD, and any error message shown. Redact unrelated personal information from payment records; leave only what we need to identify the transaction.

Never send your full card number, security code, or bank verification code.

Submit a billing ticket

What to expect

Spend less time waiting for follow-up questions

Pre-sales email is for discussing regions, configurations, and workload requirements; it doesn't confirm an order. To buy, go to the order page. For help with an existing service, submit a ticket in the console. We don't offer phone support or publish a guaranteed email response time, so don't rely on an immediate reply for time-critical work.

Keep a record of your email or ticket. Adding when the issue occurred, how the error changed, and what you've already tried is more helpful than sending the same question again. If you can't sign in to the console, email us with the steps where you get stuck—but never include your password or verification code.

Choose a region, then plan your team's handoffs

Know your configuration and region? Go ahead and order. Still comparing locations for your team? Prepare an enquiry first.

Choose a region Prepare an enquiry