Advice and support for independent developers

Not sure whether to buy or rent?
Let's talk it through

Your main computer, project scope and how long you need a Mac matter more than choosing the most expensive option. Email us with pre-sales questions. For an active machine or billing issue, sign in to the console and submit a support ticket.

You don't need to place an order before asking a question. We'll also let you know when renting isn't the right fit.

Before you order

Work out how long you'll need it

If you need a Mac for a single release sprint, renting may make sense. If you develop full-time every day from the same location, buying one could be more cost-effective. You don't need to choose a model before emailing us; start by telling us what you need to get done.

Choosing a Mac: start with your workload

If you're mainly maintaining one app and need to build and create an Archive, start by considering the Omni M4 Desk with Apple Silicon M4, 16GB unified memory and a 256GB SSD.

If you need to run several simulators, work across multiple repositories or use resource-intensive tools, tell us what you'll be running at the same time. A slow build alone doesn't mean you need the highest tier.

Include in your email: project type, tools you'll run at once and current disk usage.

Location: desktop use and build times differ

If you spend a lot of time editing and debugging in a graphical interface, network quality and distance to the node have a bigger impact on responsiveness. If you mainly submit builds and download artefacts, file transfer routes matter too.

Typical node latency is only a guide; it can't predict how the connection will feel on your network. Tell us your region, connection type and how often you'll use the remote desktop.

Include in your email: region, connection type and whether you'll mainly use the desktop or run automated builds.

Usage period: occasional or ongoing

If you want to test your project first, renting by the day works well for a small trial. A full release sprint may be better suited to a weekly plan that covers fixes and resubmissions.

If you've decided to keep developing over time, compare the monthly and quarterly options. The per-unit cost is higher for daily rentals, so breaking a clear long-term need into short rentals may not be the best fit.

Include in your email: expected start date, how long you'll need the Mac and whether you expect to keep developing.

When renting may not be the right fit: You only want to look at macOS for a few minutes, need to connect a local iPhone to the machine over USB for debugging, or rely heavily on physical peripherals at your desk. A remote, dedicated physical Mac can't replace those local connections.

Existing orders

Keep issue reports with your order

If you can't connect to your Mac, a build is failing or you need help checking a payment, submit a support ticket through the console. The order details make it easier to investigate than an email without an order number, and you can keep any follow-up in the same thread.

  1. 01

    Sign in and open a support ticket

    Sign in to the console with the account you used to order, open the support section and describe the issue. Include the relevant order number. If you can't sign in, email support and tell us what message you see when you try.

  2. 02

    Describe what happened clearly

    Include the Mac model, node, time and time zone of the issue, browser or remote desktop client, and the last action that worked. Distinguish between “can't connect”, “the screen freezes after connecting” and “Xcode reports an error” rather than just saying “it doesn't work”.

  3. 03

    Follow up on the same ticket

    List the steps you've already tried and what happened, and include any relevant error text. If things change, reply to the existing ticket. Never send passwords, verification codes, certificate private keys, recovery codes or full payment card details.

Email checklist

Turn your development plan into an email

This isn't an online submission form. Fill it in to create an email draft, then open it in your device's email app. We'll receive it only after you review and send it. The recipient is support@vpsomni.com.

Use an address where you can receive replies, and check which account your email app will send from.
Your main computer
What do you need to do?
It helps to include your expected usage period, tools you'll run at once and region. For existing orders, include the order number. Don't paste sensitive credentials.

This page only helps you prepare an email; it doesn't send anything to our support team.

Replies and next steps

We prioritise by impact and keep updates in the same thread

We don't promise a fixed response time in minutes or hours on this page. We prioritise issues based on their impact on the service, whether they can be reproduced and whether we have the details needed to investigate. We'll send updates in the original email or support ticket.

An active service is affected

For connection drops or an unusable instance, explain what's affected and when it started. Our technical team will need the Mac model, node and order details. Avoid repeatedly taking actions that could change the state of the system while trying to recover it.

Use a console support ticket and add updates to the same thread.

A payment or order needs checking

Include the order number, payment method, payment time and time zone, and the status shown on the page. Payment verification and technical troubleshooting need different details, so be specific—for example, “payment completed but status hasn't updated” or a particular billing question.

Don't make another payment to test, and never send your full card number.

You're planning or comparing options

Email us with questions about choosing a Mac, usage periods or how to use the service. If you have a release deadline, mention it in your first email. While you're waiting for advice, don't schedule an unconfirmed start date into a critical release step.

Reply to the original email with any extra details so we have the project context.

Payment checks

USD billing, two payment options

We accept USDT-TRC20 and Visa / Mastercard / Amex processed through Stripe. All orders are billed in US dollars (USD). The payment options available at checkout depend on the gateways returned by the backend at that time.

Checking a USDT-TRC20 payment

Before paying, check the network, amount and recipient details shown at checkout. If you need help verifying a payment, provide the order number and transaction hash. Never share your wallet private key or recovery phrase.

Transfers on other networks aren't supported payment options on this page.

Visa / Mastercard / Amex card payments

Payments are processed by Stripe. If the page shows an error, keep the message and note when it happened, then submit a support ticket in the console so we can check the order. Don't include your full card number or security code in an email.

If you're unsure whether a payment went through, check the order status before taking another step.

You can also ask about renewals and expiry in a support ticket. Service stops at expiry if you don't renew. Before the expiry date, confirm whether you'll continue and export any projects or files you need to keep.

Choose a Mac once you know how long you need it

Ready to go? Place your order. Still deciding? Tell us about your project. A one-off release and long-term development don't have to call for the same choice.