Singapore
A good first test for teams in Southeast Asia and nearby regions. Check latency, jitter, and packet loss from your actual office network before ordering.
Purchase & Usage FAQ
Get your key Cloud Mac rental questions answered first
No jargon here. Review the physical-node setup, two configuration prices, six available locations, access methods, developer-tool scope, payment channels, and data-migration responsibilities before ordering.
2
Available configurationsM4 and M4 Pro
6
Available locations4 in Asia-Pacific, 2 in the US
4
Billing periodsDaily, weekly, monthly, quarterly
2
Payment categoriesOn-chain transfer or card
Service model
What kind of Cloud Mac is it?
Each order provides a dedicated Apple Silicon physical node. You get remote access, but the underlying machine is not a virtual machine sharing resources with other customers.
Is VMOrbit Cloud Mac a virtual machine?
No. VMOrbit provides dedicated physical machines, with each order assigned to an independent Apple Silicon physical node. The chip, memory, and local SSD are not shared with other customers’ workloads. You access macOS through a graphical interface or command line over the network, while compute runs on the physical device.
What resources are covered by “dedicated”?
Dedicated use covers the selected model’s processor, unified memory, local storage, and system environment. VMOrbit M4 includes an M4 chip, 16GB memory, and a 256GB SSD; VMOrbit M4 Pro includes an M4 Pro chip, 64GB memory, and a 2TB SSD. Shared compute resources are not presented as dedicated configurations.
Which workloads are a good fit for Cloud Mac?
Common uses include Xcode builds, automated testing, xcodebuild and fastlane workflows, self-hosted runner jobs, remote macOS development, and AI experiments requiring Apple Silicon instruction sets and unified memory. For workloads that rely heavily on local peripherals or continuous transfer of large interactive assets, test your actual office network first.
Billing
How are daily, weekly, monthly, and quarterly billing calculated?
The four billing periods use separate catalog prices. Daily pricing is not simply multiplied, and one period’s price is not applied to another.
What are the four VMOrbit M4 prices?
VMOrbit M4 includes an M4 chip, 16GB memory, and a 256GB SSD. Pricing is $21.4/day, $57.7/week, $106.9/month, and $290.8/quarter. Use the listed price for the selected period rather than multiplying the daily rate.
What are the four VMOrbit M4 Pro prices?
VMOrbit M4 Pro includes an M4 Pro chip, 64GB memory, and a 2TB SSD. Pricing is $59.6/day, $160.9/week, $297.9/month, and $810.3/quarter. This tier suits high-concurrency builds, large projects, and memory-intensive experiments.
Can I change the billing period during my rental?
For renewals or period changes, review the available actions in the dashboard and follow the amount and effective method shown on the confirmation page. Do not estimate the new charge from the old period; recheck the model, add-ons, location, and total before submitting.
Location selection
How do I choose among the six locations and check availability?
Both configurations are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the US East, and the US West. Final availability is returned in real time by the dashboard.
Japan (Tokyo)
Useful for Northeast Asian teams comparing remote-desktop responsiveness and code-dependency download routes. No fixed latency is guaranteed.
South Korea (Seoul)
A suitable option for teams whose members are mainly in South Korea or nearby regions. Compare it with Tokyo through parallel network tests.
Hong Kong
Useful for evaluating Asia-Pacific collaboration paths. Consider repository, dependency-source, and user locations when choosing a node.
US East
A suitable test option for teams whose developers, repositories, or build dependencies are located along North American eastern routes.
US West
Suitable for teams in western North America and trans-Pacific collaboration. Test it alongside Asia-Pacific locations before finalizing your workflow.
Can both configurations be ordered in all six locations?
Yes. The VMOrbit M4 and VMOrbit M4 Pro catalogs cover all six locations above, and every combination is generally orderable. Actual availability and delivery details are based on the dashboard and order confirmation.
Should I choose a location based only on geographic distance?
No. Test the network path from key developers, repository location, dependency sources, remote-desktop performance, and CI data flows. Multi-person teams should also identify primary operators and handoff periods.
Payment methods
Which payment methods and settlement currencies are supported?
There are only two payment categories. All orders are settled in US dollars (USD); available gateways are determined by the dashboard.
USDT-TRC20
Transfer the amount to the payment details shown on the order page. Before submitting, verify the network, address, amount, and order identifier. Never send complete payment credentials through general inquiries.
Visa / Mastercard / Amex
Card payments are processed by Stripe. Amounts remain displayed in US dollars (USD), and the available card-processing entry point is determined by the dashboard.
Can I use payment methods not listed on the page?
No. Publicly supported methods are USDT-TRC20 and Visa, Mastercard, or Amex processed by Stripe. If a gateway is not shown at checkout, follow the dashboard for that session and do not transfer funds through unofficial channels.
What information should I provide for a billing issue after payment?
Log in to the dashboard and submit a billing ticket with the order identifier, selected billing period, payment category, time of occurrence, and issue description. Provide only the information needed for verification; never send passwords, private keys, recovery codes, or complete payment credentials.
Remote access
What are SSH and VNC best suited for?
SSH is best for command-line work, builds, and automation; VNC is best for development and troubleshooting that require the macOS graphical interface. Check credentials and network access before using either.
Command-line and automation access
Use it for shell commands, code checkout, xcodebuild, log inspection, runner configuration, and controlled file transfers. Before connecting for the first time, prepare the node address, port, username, and valid credentials.
- Confirm that your local network allows outbound traffic to the target port
- Verify the host, username, and key-file permissions
- If the connection fails, check credentials, firewall rules, and the network path in that order
macOS graphical interface access
Use it for the Xcode interface, simulator checks, and build issues requiring visual feedback. Performance is more affected by latency, jitter, packet loss, and display settings.
- Run a link test from your actual office network first
- Lowering image quality can reduce interaction pressure on weak networks
- For unexpected interruptions, retain the time of occurrence and the minimum necessary logs
Do not include passwords, private keys, or recovery codes in general inquiries. For connection troubleshooting, provide the node region, access method, time, error summary, and reproduction steps.
Developer toolchain
How do Xcode, fastlane, and runners integrate?
Cloud Mac provides a complete macOS graphical interface and command-line environment. Successful operation still depends on project dependencies, versions, signing materials, and CI configuration.
Can I run Xcode and xcodebuild?
Yes. Use Xcode through VNC for graphical development and call xcodebuild over SSH for automated builds. First verify the Xcode version, Command Line Tools, target SDK, project dependencies, and build parameters so version mismatches are not mistaken for node failures.
What should I check first when a fastlane task fails?
Keep the complete stage name and error summary, then distinguish dependency installation, signing materials, test failures, script exits, and network-download issues. Do not submit only the final error line; include the reproduction command, tool versions, time of occurrence, and affected scope.
Can I register a self-hosted runner?
Yes, for CI/CD workflows that support macOS executors. Restrict the repositories and jobs the runner can execute, prevent untrusted changes from accessing controlled credentials, clean the workspace and temporary files after jobs, and rotate access credentials according to your team process.
Should build caches be retained or cleared each time?
Retain controlled caches for stable dependencies and repeated builds to reduce build times. When dependencies change, disk pressure occurs, or unexplained build differences appear, clear derived data, package caches, and workspaces in layers. Confirm required artifacts are synced or backed up first.
Data responsibility
Who manages projects, credentials, and member access?
VMOrbit manages service delivery and node operation. Customers manage project data, team permissions, keys, application configuration, backups, and migration before the rental ends.
Control access scope
Grant team members only the minimum permissions they need, use separate credentials, and never share private keys. Revoke remote access immediately when someone leaves the project or changes responsibilities.
Keep project copies
Include source code, build artifacts, and required configuration in your own version-control and backup processes. A dedicated node does not replace project-level backups.
Protect CI credentials
Store tokens, signing materials, and deployment keys in a controlled secrets workflow. Restrict the runner’s repository scope and prevent sensitive values from appearing in build logs.
Complete migration on time
Finalize renewal decisions, data synchronization, and access revocation before the rental ends. After confirming that required files have been migrated, remove temporary data and unused credentials.
What should I do if I notice signs of unauthorized access?
First stop or isolate suspicious access, preserve the time of occurrence and necessary logs, rotate related SSH keys and tokens, review team permissions, and then sign in to the dashboard to submit a security ticket. Provide only the minimum information needed for investigation.
Quick terminology
Eight common terms for clear communication
These terms appear in plans, connection guides, tickets, and order configurations. Keep the definitions precise and distinguish the underlying service model from the access method.
- Physical node
- An Apple Silicon device that actually runs macOS workloads, not a virtual compute unit carved from a shared host.
- Dedicated
- One order independently uses the selected device’s chip, unified memory, local storage, and system environment without sharing workloads with other customers.
- Cloud Mac
- A remote Mac physical machine accessible over the network for development, builds, testing, automation, and experiments.
- VNC
- A connection method for viewing and operating the macOS graphical interface remotely, suitable for tasks such as Xcode.
- SSH
- An encrypted command-line connection method for build commands, controlled file transfers, log viewing, and automation scripts.
- self-hosted runner
- A CI execution node registered and managed by a team, allowing selected pipelines to run on its rented Cloud Mac.
- Build cache
- Derived data or dependency files retained to reduce repeated downloads and compilation; clean them regularly based on disk capacity and version changes.
- Billing period
- The order’s time-based pricing option: daily, weekly, monthly, or quarterly. Each period has its own price and periods are not combined.
Order changes
How do I confirm renewals, upgrades, and multi-node collaboration?
Order changes do not take effect through verbal chat agreements. Confirm renewal, additional SSD storage, Thunderbolt 5 parallel connections, and location requirements in the dashboard, including available options and pricing.
How do I renew an existing Cloud Mac?
Sign in to the dashboard and open the relevant order to review available periods, the amount due, and the confirmation result. Before renewing, decide whether you still need the current location, configuration, and add-ons, and plan project data and team access in advance.
How much does additional SSD storage cost?
+1TB SSD costs $2.5/day, $6.6/week, $12.3/month, or $33.5/quarter; +2TB SSD costs $5/day, $13.2/week, $24.6/month, or $67/quarter. Read the price for the selected order period; actual options are subject to the dashboard.
What is Thunderbolt 5 parallel connection for, and how is it priced?
It suits workloads requiring collaboration between multiple physical nodes and a clearly planned high-speed device-to-device link. The price per node is $1.1/day, $2.9/week, $5.4/month, or $14.7/quarter. Before submitting, specify the node count, workload relationship, and preferred region, then confirm availability in the dashboard.
Can I switch an existing order directly to another location?
Confirm the node requirement for the current order and target region in the dashboard; do not assume the original order will migrate automatically. If changing regions, prepare project copies, a dependency list, a credential-rotation plan, and validation steps before scheduling migration.
What must I check before submitting an order change?
At minimum, verify the model, billing period, target node, storage add-ons, Thunderbolt 5 parallel-connection needs, total charge, and data-migration plan. For an existing node, also confirm member-access revocation, cache handling, and backups of required files.
Next steps
Your questions are answered—choose the configuration that fits your needs
Determine the workload, location, and billing period first, then start the order. For existing-order issues, sign in to the dashboard and submit a related ticket.