Check the rental details,
then choose your plan

Yes. Mesh M4 comes with a Mac mini M4, 16GB RAM and a 256GB SSD, for $20/day. Mesh M4 Pro comes with a Mac mini M4 Pro, 64GB RAM and a 2TB SSD, for $60.3/day. Both are dedicated physical Macs, not a build-and-deliver service.

If you’ve written your project on Windows and only need macOS to install dependencies, archive with Xcode and export a build, a daily rental is a straightforward place to start. Prepare your project, dependency versions and signing materials in advance so you can spend your rental time getting things done.

For a single build, start with a daily rental. If you’ll test repeatedly during a development cycle, compare the weekly rate. For a team keeping its toolchain available longer, consider a monthly or quarterly rental. Before ordering, check the selected term, add-ons and total. Rental terms are not billed by the hour.

Sign in to the console and check the expiry date and available renewal options for the relevant instance or subscription. Select a renewal term and complete payment. Check the invoice and subscription status in the console to confirm renewal; simply opening the payment page does not activate it.

If you need to keep using your current environment, renew before it expires and make sure you’re renewing the original subscription. Ordering a new machine is not the same as extending an existing subscription. If you have questions about an expiry date or invoice, submit a support ticket in the console and include your order number.

After ordering and activation, sign in to the console, open the relevant machine’s details and launch the browser-based remote desktop. Apps run on the cloud Mac’s physical node; your local computer displays the screen and sends keyboard and mouse input.

Once macOS is open, check that Xcode, dependencies and signing settings match your project. Your Windows project folder won’t appear on the remote disk automatically. Transfer your project to the cloud Mac using a version control system or file transfer tool.

No remote desktop client is needed. Sign in and launch it from the console. It’s useful for one-off builds, graphical settings and checking build results. Keep your network stable and allow keyboard input in your browser.

Closing the browser tab does not end your rental or cancel your subscription. Check billing and expiry status in the console. For long-running builds, keep log files too, rather than relying only on the output currently visible on screen.

Yes. Use SSH for command-line tasks. Get the host, port and login details from the console for your machine—don’t use example connection details as your own. You can connect from a Windows terminal with SSH support and transfer files using SFTP, SCP or your own version control system.

Before building, check your code branch and dependency lockfiles. Afterward, download your archives, exported builds and any essential logs. See the usage support page for connection instructions and troubleshooting.

It’s a dedicated physical Mac, not a virtual machine. During your rental, you use the corresponding physical Mac mini node with full access to the macOS desktop and command line. The browser is simply your remote access method; it doesn’t change the machine’s physical nature.

Choose from Mesh M4 and Mesh M4 Pro. Consider Mesh M4 for building a single project. For parallel builds across multiple projects or local model experiments that need more memory, consider Mesh M4 Pro. Actual build times depend on your code, dependencies, cache and concurrent workloads.

Yes. You can use Xcode and install development tools that support your macOS version and Apple Silicon, such as fastlane, Homebrew and your project’s dependencies. Check which Xcode and macOS versions your project needs before changing your toolchain. Avoid replacing the entire environment just before delivery.

“Can be installed” doesn’t mean every app is compatible out of the box. Before renting, check the requirements for software that needs a specific system version, licence or peripheral. You’re responsible for providing signing certificates and provisioning profiles; installing Xcode won’t configure signing for your project automatically.

Check the order configuration for +1TB SSD and +2TB SSD add-ons. +1TB SSD costs $2.7/day, $7.3/week, $13.6/month or $37/quarter. +2TB SSD costs $5.4/day, $14.6/week, $27.2/month or $74/quarter. Add-on storage is charged separately from the SSD included with the base machine.

When estimating storage, include your project, dependencies, simulators, archives and build caches. If you need to change storage on an existing machine, check the available options in the console or submit a support ticket to confirm how it works. Don’t assume files will be migrated automatically.

If you’ll use the remote desktop frequently, consider a nearby location with a reliable connection. Our locations are Singapore, Tokyo, Seoul and Hong Kong. Distance is a useful starting point, but your actual connection depends on the network between you and the node.

For overnight batch builds, keyboard and mouse responsiveness may matter less. Focus instead on project transfer and team workflows. We don’t publish city-by-city network test results, so we can’t promise a fixed latency for any location.

All nodes operate year-round, 365 days a year, so your rental isn’t limited to local business hours. Access to a specific machine depends on its activation, subscription and network status, as well as the state of the system itself.

If you can’t access the remote desktop, first check that you’re signed in to the right account and that your subscription is active. Then follow the support page’s steps to troubleshoot browser and SSH access. When submitting a ticket, include the location, instance ID, time of the issue and what happened with each connection method.

All prices and invoices are in US dollars (USD). We accept only USDT-TRC20 and Visa, Mastercard or Amex processed through Stripe. At checkout, follow the available payment options, amount due and instructions shown for your order.

For USDT-TRC20, carefully check the network, recipient details and amount. For card payments, complete any required verification on the payment page. Never send your full card number, verification code, private key or other sensitive information by email or support ticket.

Return to the console to check the relevant invoice, order and instance status. Payment, invoice confirmation and machine activation are separate statuses. Don’t assume your machine is ready based only on a redirect in your browser, and don’t pay again before checking the status.

If you need help reconciling a payment, include your order number, payment method, amount and payment time. For USDT-TRC20, you can provide the transaction hash. For card payments, provide proof of payment without sensitive card details. Contact us about billing through a console support ticket or at support@osxmesh.com.

When your rental ends, the disk enters the expiry cleanup process. Don’t use an expired machine as long-term file storage. Don’t rely on an unannounced retention period or assume you’ll still be able to connect and retrieve your project after expiry.

Before expiry, push your source code to your own repository and download any archives, exported builds, build logs and environment notes you want to keep to a secure location. Store signing materials separately in encrypted form. See our privacy policy for more information about data handling.

To keep your current environment, renew the original subscription before it expires, then check the new expiry date and instance status in the console. A new order, system reinstall or machine change does not guarantee that your existing environment will remain unchanged.

Even if you plan to renew, back up your project and key settings, and record your Xcode version, dependency tools and build commands. If your rental has already expired, you’re changing locations or you need a reinstall, submit a support ticket to check the machine’s data status before proceeding.

Include your order number, location, Mac model, steps to reproduce, exact error message and troubleshooting steps you’ve already tried. Redact credentials, personal file paths and other sensitive information from screenshots. For build issues, share the relevant log excerpt rather than your entire source directory.

Never include login passwords, SSH private keys, signing private keys or payment verification details in email. If we need more information to investigate, we’ll confirm what’s needed and how to share it through a support ticket. If you haven’t ordered yet, tell us what you want to do, your expected rental term and the tools you need.