You don’t need to replace your Windows or Linux computer. Configure your order, pay, find connection details, and manage billing in the console. Once your Mac is ready, connect to your dedicated physical Mac mini from a browser or VNC client.
Configure your order, then wait for the console to show that your Mac is ready. Use the console’s live status and connection details as the source of truth for the address, credentials, and availability.
One Halo M4 configuration is currently available: Mac mini M4, 16GB / 256GB. You get an entire dedicated physical machine, not a virtual machine. Choose the region, billing period, and add-ons when you place your order.
Choose from six regions: Singapore, Tokyo, Seoul, Hong Kong, US East, and US West. If you’ll often move windows, edit, or preview content, consider a region close to you. For builds, exports, and background tasks, also consider where your code, assets, and collaboration services are hosted.
The region name tells you where the machine is located, not the measured latency from your network. Your experience also depends on your local connection and remote display settings.
For a quick macOS app test, a short billing period may be all you need. For ongoing project work, choose a period that matches your expected usage. Before you submit, check the period and its price—don’t compare prices for different billing periods as if they covered the same length of time.
Choose an additional +1TB SSD or +2TB SSD if you need more space. If you need Thunderbolt 5 daisy chaining, check the relevant option and device count in the configurator. Estimate the space needed for projects, dependencies, caches, and exports before adding extras.
Monthly pricing: +1TB SSD is $10.8/month, +2TB SSD is $21.6/month, and Thunderbolt 5 daisy chaining is $8.5/month per device. Check other billing periods in the order configurator, and include all add-ons in your order total.
Orders are billed in USD. Payment methods include USDT-TRC20 and Visa / Mastercard / Amex via Stripe. The payment gateway actually available is determined by the backend.
Make sure Halo M4, the region, billing period, and add-ons match your plan. Check the SSD options and daisy-chain device count carefully—don’t proceed based only on the base configuration price.
For USDT, confirm that you’re using the TRC20 network and follow the payment page instructions. For card payments, complete checkout through Stripe. Never enter connection credentials or project keys in payment notes.
Return to the console to confirm your invoice and order status, then check whether the instance is ready. If payment hasn’t been confirmed, review the billing record first. If you need help, submit a support ticket with your order details; don’t assume payment failed just because you closed the payment page.
Once your Mac is ready, open its details in the console to check the node status, connection method, and credentials. You’re getting remote access to a dedicated Mac mini—not a macOS image to download to your local computer.
Compare the region and specifications shown for the instance with your order. If you manage multiple tasks, confirm which machine you’re connected to before uploading files, so they don’t end up in the wrong work environment.
Check the region and specsUse the instance details as the source of truth for the connection address and credentials. Store credentials in a password manager you trust—not in a code repository, public screenshots, or persistent team chat messages.
Share credentials only with people who need themSubmit a support ticket in the console with the instance, time and time zone, error message, and steps you’ve tried. You can also email support@vmhalo.com. Don’t include your full password in an email.
Open the console to submit a ticketWe recommend connecting in a browser first. Make sure you can see the desktop, type, and open apps before transferring large files or setting up automation. If you need a standalone client, use the VNC connection method supported by your instance.
| What to check | Browser connection | VNC client |
|---|---|---|
| Getting started | Sign in to the console and use the browser connection option in the relevant instance details. | Check the VNC connection details provided for your instance, then open a client on your local computer. |
| Connection settings | Follow the instructions for the connection option. If credentials are requested, use the current details shown for that instance. | Enter the address, port, and authentication details as provided. Don’t reuse settings from another machine. |
| Display and input | Check that the display updates and that keyboard and mouse input work. See whether browser shortcuts are intercepting your input. | Check the keyboard mapping, display scaling, and resolution. Start with image quality that suits your current bandwidth. |
| If the connection is slow or unreliable | Check your local network and any error messages on the page, then check the instance status. | Check the address and authentication settings, then adjust the resolution, color depth, or compression options. |
Once you’re in macOS, create a test file, type a few lines, and open an app you plan to use. This helps you distinguish connection or input issues from project dependency or build errors. If the display lags, lower the remote resolution and image quality first. Don’t repeatedly launch the same demanding task to test your network.
If only one app stops responding, note its message and what you were doing. If you can’t connect to the desktop at all, record the client error and instance status. Describing which issue you’re seeing makes troubleshooting easier than simply saying “the machine doesn’t work.”
Whether you’re migrating from a local Mac or using macOS from Windows for the first time, work through data → toolchain → CI integration. Check the result at each stage before moving on. This helps avoid changing your connection method, dependency versions, and automation setup all at once.
Start with source code, configuration files, and a small set of assets, then transfer larger files. Note project paths and file permissions, and check that important files are intact. There’s no need to migrate caches that can be regenerated right away.
Handle keys and signing materials separately; don’t put them in a public repository. Keep a local copy during migration, and don’t delete the originals as soon as the first upload finishes.
Check: project files open correctlyCheck your current Xcode version against the project requirements. Install or switch toolchains as needed, then configure dependencies, signing certificates, and the macOS apps you use. An app launching successfully doesn’t mean the project environment has been fully migrated.
Build or export the same small project, and record the tool versions, commands, output directory, and any errors. Confirm that the resulting artifact works as expected.
Check: you have a verifiable build artifactRegister the node as a self-hosted runner and connect it to your existing pipeline. Configure the correct working directory, permissions, and credentials for the job, then trigger a small task and check its logs and artifact path.
Don’t let multiple jobs write to the same working directory. Isolate files and caches by project, and make sure you can find logs, stop a failed job, or run it again.
Check: the pipeline can find its artifactsTerms in the order configurator and connection page each refer to a specific choice or action. If you’re unsure, check whether a term affects machine location, usage time, or connection method.
Nodes run 24/7, 365 days a year. Builds, exports, and other tasks started on your remote Mac don’t depend on your home computer staying on. But disconnecting from the remote desktop and ensuring an app keeps running in the background are two different things—check the task itself before you leave.
First, make sure the task has started and isn’t waiting for confirmation in a dialog. Check that its files are on the node and that it doesn’t rely on a temporary file path provided by your local computer. Finally, confirm that logs and artifacts are being written to a specific directory on the remote machine. For command-line tasks that depend on an interactive session, follow the tool’s instructions for running in the background and saving logs.
Try a short task first: start it, disconnect from the remote session, then reconnect and check its progress. Once you’ve confirmed that the workflow works, schedule longer tasks. To leave the remote desktop, don’t quit the app, log out of macOS, or shut down the remote machine.
After reconnecting, check the completion status, logs, and output files—not just whether the desktop is still open. Copy important artifacts to your own storage promptly. As your billing period nears its end, back up your projects, configuration, and essential data in advance. Don’t leave your only copy on a rented node.
Choose a region and billing period, review your order, then open the desktop from the console. Start with a small task to confirm the connection, environment, and artifacts are all as expected.