Singapore
Suitable for Southeast Asian teams, regional repositories, and cross-border collaboration.
Quick pre-rental checklist
Answers to confirm before renting a dedicated Cloud Mac
From physical-node architecture, two configurations, and full pricing to node selection, VNC access, Xcode builds, and renewal management, this guide follows the real usage flow.
FAQ ROUTING PLATE
Standardized details
Rental decision guide
01 / PRODUCT
Product architecture
Dedicated physical node, not a virtual machine
Verified
02 / CATALOG
Configurations & pricing
Two configurations, four billing terms
Verified
03 / REGION
Nodes & connectivity
5 nodes, VNC graphical interface
Verified
04 / DELIVERY
Delivery & management
Typical provisioning completed in about 4 minutes
Verified
Starting price
$20.3/day
All charges billed in USD
Product architecture
One order maps to one dedicated physical node
VMArm provides always-on dedicated physical Cloud Macs. Compute, memory, and local storage are not shared with other orders, making them suitable for development and build workloads that require a stable environment.
Is VMArm a virtual Mac?
No. Each order exclusively uses an Apple Silicon physical node, with macOS running directly on a physical Mac rather than having compute resources partitioned through a virtual machine. You get fixed chip, memory, and local storage resources—not shared capacity affected by neighboring workloads.
What resources are included in “dedicated”?
The dedicated resources include the selected model’s processor, memory, local SSD, macOS session, and remote connection endpoint assigned to the node. Daily development, archiving, runner jobs, and cache operations all run on the same physical node.
- Compute
- The selected M4 chip is dedicated exclusively to the current order.
- Memory & storage
- Capacity matches the order configuration and is not shared with other orders.
- Runtime
- Supports the macOS graphical interface and command-line workflows.
Which workloads are suited to a dedicated Cloud Mac?
Common uses include everyday Xcode development, iOS and macOS archiving, TestFlight uploads, self-hosted runners for GitHub Actions or GitLab CI, Unity iOS builds, visionOS environment validation, and local AI experiments that require fixed memory and disk capacity.
Available configurations
Only two configurations—no need to compare near-identical specifications
Start with VMArm M4 Core for light maintenance and single-project builds; choose VMArm M4 Plus for multi-project development, parallel builds, and higher memory workloads.
Which models are currently available?
The current catalog contains only the following two Mac mini M4 configurations. All page content and order options are based on these two configurations.
| Configuration | Chip | Memory | Local storage |
|---|---|---|---|
| VMArm M4 Core | M4 | 16GB | 256GB SSD |
| VMArm M4 Plus | M4 | 24GB | 512GB SSD |
How do I choose between M4 Core and M4 Plus?
VMArm M4 Core is usually sufficient for single-project maintenance, code signing, routine archiving, and low-concurrency runners. VMArm M4 Plus is better for parallel Xcode workspaces, continued compilation after Unity exports, visionOS environments, and local model experiments.
- Choose Core:For focused tasks and low concurrency, with 256GB of local storage sufficient for source code, dependencies, and build artifacts.
- Choose Plus:For running multiple build tasks simultaneously, with 24GB of memory and greater base storage needs.
- Add storage:Choose a separate SSD expansion when dependency caches, archives, and model data are growing quickly.
Full pricing
Choose daily, weekly, monthly, or quarterly terms
The starting price for VMArm M4 Core is $20.3/day. Longer terms mean fewer renewal actions; choose based on your project schedule and runner usage duration.
What are the full-term prices for both hosts?
| Configuration | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| VMArm M4 Core | $20.3 | $54.9 | $101.6 | $276.4 |
| VMArm M4 Plus | $39.4 | $106.5 | $197.2 | $536.4 |
Which billing term should I choose?
Daily or weekly terms suit short-term validation, one-off builds, or temporary environment checks. Monthly or quarterly terms are better for ongoing development, fixed runners, and long-term cache environments. Before renewal, recheck the model, node, added storage, and term; the final USD amount appears on the order confirmation page.
Add-ons
Storage expansion and Thunderbolt 5 interconnects priced separately
Add-ons are billed according to the host term. Before choosing, estimate the combined space needed for source code, dependency caches, DerivedData, archives, logs, and model data.
How much do the three add-ons cost?
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.8 | $7.7 | $14.2 | $38.6 |
| +2TB SSD | $5.6 | $15.4 | $28.4 | $77.2 |
| Thunderbolt 5 interconnect (per machine) | $1.2 | $3.1 | $5.8 | $15.8 |
How do I know whether I need additional storage?
Do not judge by repository size alone. Xcode DerivedData, dependency caches, simulator data, multiple archives, Unity export projects, and build logs all consume space over time. Keep headroom for system and temporary files, and maintain separate backups for build artifacts that must be retained long term.
When is a Thunderbolt 5 interconnect useful?
This option is billed per node and suits teams that need a high-speed local data path between multiple physical Macs. Standard single-machine Xcode development, remote desktop use, and single-runner workflows typically do not need it.
Node selection
5 nodes covering Asia and the U.S. West Coast
Both configurations are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the U.S. West. Actual availability is returned in real time by the console.
Which nodes does VMArm provide?
Japan (Tokyo)
Suitable for development teams and code repositories in Japan and East Asia.
South Korea (Seoul)
Suitable for development, builds, and delivery across South Korea and Northeast Asia.
Hong Kong
Suitable for collaboration between South China and Southeast Asia.
U.S. West
Suitable for West Coast teams and local code repositories.
How should I choose a node?
Prioritize a region close to your main operators, code repository, or CI/CD control plane. For daily graphical-interface work, focus on round-trip latency from the local network to the node; for background builds, focus on the network path from the node to repositories, dependency sources, and delivery targets.
- Start with operator location:If you use VNC frequently, prioritize the shortest local network path.
- Then check repository location:Minimize cross-region traffic for dependency downloads and large-repository synchronization.
- Finally, run real-world tests:Record latency, packet loss, repository clone time, and the time required for a complete archive.
Can the node run continuously?
Yes. Nodes run continuously 365 days a year, making them suitable for long-running runners, overnight builds, and cross-time-zone workloads. Save your work before changing system settings, updating development tools, or clearing caches, and keep separate backups of code, certificates, and build artifacts.
Billing & payments
All orders billed in USD
Payment options are limited to USDT-TRC20 and Visa, Mastercard, or Amex processed by Stripe. The final available gateway is returned in real time by the console.
Which payment methods are supported?
You can use USDT-TRC20, or use Visa / Mastercard / Amexprocessed by Stripe. All orders are settled in USD; before confirmation, the order shows the model, term, node, add-ons, and total due.
How do I confirm my order status after payment?
After payment, return to the console to check the order status. Once payment confirmation enters the delivery process, the system completes node allocation, initialization, and connection-information generation. If the status remains unchanged for an extended period, submit a ticket in the console with the order number and payment status.
What information is needed for billing issues?
Provide the order number, selected configuration, billing term, payment method, payment status, and time the issue occurred. For USDT-TRC20 payments, you may include the transaction ID; remove private keys, access tokens, and other sensitive information before submitting.
Remote access
Verify the address and credentials first, then adjust display settings
VNC provides access to the macOS graphical interface. Retrieve connection details from the console; do not share them in public messages or reuse the same credentials across multiple people.
What information is needed for the first connection?
You need the node address, VNC port, system username, and temporary credentials provided by the console. Enter the address and port in a trusted VNC client, confirm the encryption settings, and connect. After the first login, update the temporary credentials and store the new ones in a secure password manager.
How do I adjust resolution, keyboard mapping, and image quality?
Set the remote resolution to a level your local display can show reliably, then adjust image quality, color depth, scaling, and frame rate based on network conditions. If shortcuts behave unexpectedly, check the VNC client’s Command, Option, and Control mappings, and make sure the local input method is not intercepting key combinations.
How do I protect the session when away from the computer?
Lock the macOS session before leaving; do not merely close the VNC client window. Never share connection credentials. For team use, create least-privilege system accounts by role and update passwords promptly when members or devices change.
What troubleshooting sequence should I follow after a VNC disconnection?
- Local network:Confirm that the current network can access external services normally and test for significant packet loss.
- Connection fields:Recheck the node address, port, username, and the client’s encryption settings.
- Session status:Wait for a brief network interruption to recover, then reconnect; avoid creating multiple sessions in rapid succession.
- Client cache:Delete incorrect old connection records, then connect using the current information in the console.
- Support record:If you still cannot connect, save the time of occurrence, client version, error details, and redacted screenshots.
Build environment
Manage versions, signing, caches, and disk space as one baseline
Build issues are rarely caused by a single component. Record the Xcode version, SDK, dependency lockfiles, signing materials, runner labels, and available disk space to reproduce differences reliably.
How should I manage Xcode and target SDK versions?
Document the project’s required Xcode version or encode it in the runner label. Before upgrading, validate compilation, tests, archiving, and upload workflows in an isolated job. Command-line tasks should explicitly select the developer tools path to prevent interactive sessions and background runners from using different versions.
How should signing certificates and provisioning profiles be managed?
Import only the certificates and provisioning profiles required by each project and team, granting access only to accounts that perform signing. Never put signing private keys in repositories, build logs, or ticket attachments. After updating signing materials, run a repeatable archive validation before resuming batch jobs.
What should I check first when a TestFlight upload fails?
Check in order whether the archive uses the correct configuration, the Bundle Identifier matches the provisioning profile, the signing certificate is accessible, the version and build numbers meet the current release workflow, and the earliest valid error in the upload log. Do not capture only the final log line.
How can I keep a self-hosted runner stable?
Give the runner clear node labels and job boundaries, run it as a service, and restrict the execution account’s permissions. After each job, remove temporary keys and one-time files while retaining planned dependency caches. Match concurrency to available memory, disk space, and actual project load.
What are the principles for cache cleanup and disk planning?
Prioritize removing regenerable DerivedData, invalid dependency caches, outdated simulator data, and archives no longer needed. Before cleaning, confirm that no task is reading or writing the relevant directories. For long-running projects, set capacity thresholds, track source, cache, archive, and log usage regularly, and keep separate backups of critical artifacts.
Delivery & management
Typical provisioning takes about 4 minutes
Payment confirmation, node allocation, system initialization, and connection-information generation run in sequence. Once complete, you can view the order, connection details, renewal status, and support tickets in the console.
What steps are included in the 4-minute provisioning flow?
-
About 1 minute
Payment confirmation
Verify the order amount and payment status.
-
About 1 minute
Node allocation
Allocate a dedicated physical node based on the selected model and region.
-
About 1 minute
System initialization
Prepare the system environment and order-specific access settings.
-
About 1 minute
Connection information generation
Generate the node address, system account, and remote connection details.
About 4 minutes is typical for the process. Actual status is returned in real time by the console.
What should I prepare when submitting a technical ticket?
Prepare the order number, node region, time of the issue, system version, Xcode version, reproduction steps, expected result, and actual result. Remove keys, signing private keys, access tokens, connection credentials, and sensitive business data from logs and screenshots before submitting.
Where can I renew and manage my node?
After signing in to the console, you can view the current order, node information, billing term, renewal status, and billing records. Before renewal, confirm the project schedule, storage usage, and required term; if changing the configuration or node, first create separate backups of code, certificates, and build artifacts.
What contact options are available if I still have questions?
For technical, connection, and billing issues related to an order, sign in to the console first, submit a ticket, and link the relevant order. For pre-sales, team purchasing, or console access issues, email support@vmarm.com.
Start your next build
Your configuration is set—move your build environment to a dedicated physical Mac
Choose one of the two available configurations, then confirm the billing term, node, and additional storage. The starting price is $20.3/day.