Sort Out Your Rental Before You Start

Tell Us About Your Project Timeline

How many machines do you need, for how long, and where are your clients? Start with these details, then decide whether to try one machine by the day or arrange separate machines for multiple clients.

Ideal for last-minute builds, extra capacity during delivery week, and concurrent client projects. Already renting? For connection, build, or payment issues, sign in to the console and submit a ticket so we can link it to the right machine and order.

Rent by the Day Email Us About Scheduling

Rent by the day and get started the same day. Your rental stops at the end of the term unless you renew. No long-term contract.

Put Your Requirements on One Schedule

Include These Four Details

There’s no need to prepare a procurement document. Share what you’ve decided and ask about anything still unclear. Don’t attach client source code or full certificates to your enquiry.

Project duration

Include your expected start and delivery dates, and whether you’ll need to keep the machine after delivery for fixes. Let us know whether you build occasionally or every day so we can help compare daily, weekly, monthly, and quarterly rentals.
Concurrent clients

Tell us how many clients will be active at the same time, whether each has a separate certificate, and whether builds can queue. The number of clients doesn’t determine the number of machines you need; simultaneous use and isolation requirements do.
Main framework

Let us know if you use native tools, Flutter, React Native, or Unity, and whether your project has multiple targets or large asset directories. Project size helps us recommend a Mac mini M4 or Mac mini M4 Pro.
Preferred region

Choose from Singapore, Tokyo, Seoul, and Hong Kong. Tell us where your team and clients are located. If you’re undecided, let us know whether remote desktop responsiveness or build artifact transfers matter more.

Suggested Email Subject

“Project Mac Rental Enquiry | Expected Start Date | Concurrent Clients”. Cover the four details above, then add your main question—for example, rental duration, separate machines, or storage expansion.

For client projects, use internal project codes. Never send login passwords, private keys, full payment card details, or usable signing credentials.

Discuss Plans by Email; Link Tickets to Orders

Planning to Rent, or Already Using a Machine?

Contact us by support email or through console tickets. Choose the right channel based on whether your question needs to be linked to an existing machine. There’s no need to submit the same issue through both.

Planning a Rental

For studios that haven’t ordered yet and need to confirm rental duration or machine count. Email us your timeline, framework, and concurrent client needs to discuss how many machines you need, which model, and for how long.

For a one-off build, rent by the day or start with a week?
For multiple clients, rotate machines or rent one for each?
How large are your project and assets, and will you need extra storage?

We’ll reply in the same email thread. Response times aren’t guaranteed by a fixed number of hours; if your delivery date is close, include your deadline in your first email.

Email Us About Your Project

Technical Issues with a Rented Machine

For remote connection failures, interrupted builds, or reinstall requests. Sign in to the console, open a support ticket, and tell us which machine is affected and where you are in the project.

Include the machine ID, region, and when the issue occurred.
Describe the expected result, what happened, and how to reproduce it.
Attach screenshots or error logs with sensitive details redacted.

We’ll share progress in the ticket. If the issue is still delaying delivery, add its impact and the time of the most recent failure to the same ticket.

Orders and Billing

For questions about payment status, billing records, renewal periods, or expiry dates. For an existing order, use a console ticket to keep the issue linked to the relevant record.

Include the order or invoice number and what you’d like us to check.
Tell us the payment method and payment date.
If you can’t sign in, email us from your account email address.

We’ll respond through the ticket or by email. Opening your email app doesn’t submit a request. Check payment status in the console.

Support email:support@vmssd.com

Your email app sends the message; clicking the email button won’t send it automatically. If your email app doesn’t open, compose a message in your usual email service and enter the address above.

Match Your Machines to Client Deliveries

Running Multiple Machines? Plan for Isolation

Each dedicated physical Mac mini is assigned to one customer; it’s not a virtual machine. Your studio can rent separate machines for each client or rotate a machine by the day when projects don’t overlap.

If Delivery Dates Overlap, Use Separate Machines

When several clients need builds or testing at the same time, separate machines keep code directories, certificates, and keychains apart—and prevent one build from holding up another client’s delivery.

In your enquiry, list each client’s project code, start and delivery dates, and expected machine model. If one project runs late, extend only its machine’s rental; there’s no need to renew the whole group.

A good fit: clients with separate data-handling requirements or genuinely overlapping build times. Not a good fit: small projects with no concurrent builds and only occasional compiling.

Need to Link Machines? Let’s Plan the Work

The Thunderbolt 5 multi-machine setup add-on costs $1.2/dayper machine. For a multi-machine workflow, tell us how many machines are involved, which regions you need, and how you’ll divide the work so we can confirm the connection setup.

Linking machines doesn’t automatically make apps run faster across them or combine their memory. First check whether your tools can split tasks. If you’re simply building for different clients, separate machines are usually the better place to start.

A good fit: you already have a multi-machine workflow and need to confirm setup requirements. Not a good fit: you expect a single build to speed up automatically without changing your workflow.

Mention Project Wrap-Up in Your First Email

Your rental stops at the end of the term unless you renew, with no cancellation fee. Allow time before delivery to export build artifacts, certificates, and essential configuration. If you need more time, renew for a suitable term in the console. Don’t use a machine after it expires as a project archive.

Confirm Payment Terms Before You Pay

We accept USDT-TRC20 and Visa, Mastercard, or Amex via Stripe. All payments are in US dollars (USD). Available payment options depend on the gateways returned by the backend.

For payment checks, provide your order number and payment date. For USDT-TRC20, you can also include the transaction hash. Never send your full card number or security code. Check renewals and billing records in the console.

Once Your Timeline Is Set, Rent for the Project

Choose a model, region, and rental term, then get started the same day after payment. Still deciding how to assign machines? Explore a delivery scenario similar to yours.

Rent a Cloud Mac Explore Use Cases