VMOak provides Apple Silicon dedicated physical nodes assigned per order, accessible through remote desktop and SSH. This page explains the two configurations, six regions, exact pricing, the approximately four-minute provisioning flow, billing methods and what happens when service expires.
Confirm the product and configuration first, then review regions, pricing, connectivity and expiration rules. Each entry goes directly to its answer without hiding additional information.
VMOak assigns an Apple Silicon physical node to a single valid order. The processor, memory, system drive and local runtime environment are dedicated to that order, while everyday use takes place through a network connection to the macOS graphical interface or command line.
VMOak Cloud Mac uses a real Apple Silicon physical node. Each valid order corresponds to one dedicated physical machine, with the operating system running directly on that device rather than splitting its processor and memory among tenants. You operate it remotely over the network, but builds, tests, coding and creative work run on the assigned physical node.
Dedicated resources include the processor, memory, system drive and local runtime environment of the device assigned to the order. The node network remains part of the hosted infrastructure. External repositories, third-party developer tools, team accounts and software licenses are managed by you. VMOak provides remote access but does not bundle third-party licenses with the machine.
A remote node suits continuous builds, self-hosted runners, cross-region collaboration, background transcoding and tasks requiring a fixed macOS environment. The main difference is networking: the desktop image must be encoded and transmitted, local USB peripherals should not be assumed to be directly connected, and ultra-low-latency audio monitoring or hardware-dependent work should be tested first. Command-line automation is usually less affected by network fluctuations than high-frame-rate desktop interaction.
A standard order completes configuration confirmation, region selection, physical node assignment and checks, then access-detail generation. The stated time is a normal-process estimate, not an unconditional guarantee.
The four minutes come from four standard stages: about 45 seconds to confirm configuration, 60 seconds to select a region, 90 seconds to assign and check the physical node, and 45 seconds to generate access details. Actual time depends on order completeness, payment confirmation, automated checks and network conditions, so treat it as a normal-condition process estimate.
All nodes operate continuously year-round, 365 days a year. If a node issue occurs, the team checks it before issuing access details.
Access details typically include the order identifier, node information, remote address, account name, temporary credentials and essential connection instructions. They appear in order-related notifications and the console. Update temporary credentials after the first connection, and manage desktop access and SSH keys according to team responsibilities.
Choose based first on peak memory and the number of sustained tasks, then on storage. The page lists only the current two tiers and does not substitute unpublished specifications.
Suitable for single-project builds, standard Xcode work, automation scripts, light self-hosted runners and remote desktop tasks that do not continuously consume large amounts of memory.
Choose VMOak M4 BranchSuitable for parallel multi-project builds, large-project indexing, intensive simulator workloads, large-model inference, high-memory data processing and sustained workloads requiring a larger local workspace.
Choose VMOak M4 Pro CanopyIf your work centers on single-project builds, code editing and short remote desktop sessions, start by evaluating VMOak M4 Branch. If you will run multiple builds, simulators, indexing tasks or memory-intensive tools simultaneously, consider VMOak M4 Pro Canopy. The key metrics are peak memory, concurrent processes and cache usage during the same period—not the number of projects alone.
The public catalog currently offers only M4 / 16GB / 256GB and M4 Pro / 64GB / 2TB. Storage can be expanded with the +1TB SSD or +2TB SSD add-on; additional storage does not change the processor or memory specification. For multiple fixed-capacity machines, contact support by email or console ticket with the quantity and delivery schedule.
Catalog regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East and US West. Different network routes or facility labels within one region do not count as additional regions.
| Model | Singapore | Japan (Tokyo) | South Korea (Seoul) | Hong Kong | US East | US West |
|---|---|---|---|---|---|---|
| VMOak M4 Branch | Available | Available | Available | Available | Available | Available |
| VMOak M4 Pro Canopy | Available | Available | Available | Available | Available | Available |
Prefer a region close to your primary operators, code repository or build-artifact destination. Remote desktop performance depends most on round-trip latency and network stability between the operator and node; CI/CD also depends on links to repositories, dependency sources and artifact storage. For distributed teams, identify the primary users first, then confirm with real network tests.
This page shows the public catalog relationship between models and regions. At checkout, actual availability is determined by the real-time response from the console. Both models cover all six regions, and the selector shows orderable regions for the current model rather than asking users to interpret disabled options.
The region is part of the order configuration; switching regions should not be understood as instantly rerouting the same device. If a project must be migrated, back up repositories, build caches, key configurations and artifacts first, then use a console ticket to specify the target region and preferred timing. The team will confirm the available path based on the order status.
Each term has its own fixed price. Longer-term pricing is not simply the daily price multiplied out, so check the selected model, term and add-ons directly before submitting an order.
| Item | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| VMOak M4 Branch | $20.3 | $54.8 | $101.4 | $275.8 |
| VMOak M4 Pro Canopy | $61.7 | $166.5 | $308.3 | $838.6 |
| +1TB SSD | $2.1 | $5.6 | $10.3 | $28 |
| +2TB SSD | $4.2 | $11.2 | $20.6 | $56 |
| Thunderbolt 5 parallel connection (per machine) | $1.4 | $3.7 | $6.8 | $18.5 |
Evaluate a daily term for short compatibility checks, temporary builds and one-off troubleshooting; choose weekly for a sprint expected to last a week; and use monthly or quarterly terms for fixed runners, continuous development environments and long-term creative projects. Select the term based on the task duration rather than assuming the system will switch to another price after expiration.
+1TB SSD, +2TB SSD and Thunderbolt 5 parallel connections are priced independently by selected term and listed in the order details before submission. Additional storage expands the workspace; it does not turn VMOak M4 Branch’s 16GB memory into another capacity or change VMOak M4 Pro Canopy’s M4 Pro / 64GB / 2TB base specification.
First check the public catalog on the plans page, then review the model, region, term, storage expansion and Thunderbolt 5 parallel-connection quantity before submitting. The combination details shown on the order-confirmation page are the basis for this charge. If the term or add-ons are incorrect, go back and edit before submission.
VMOak supports only USDT-TRC20 and card payments by Visa / Mastercard / Amex processed through Stripe. The actually available gateway is determined by the backend response when you submit the order.
No. Models, terms and add-ons are priced and billed in USD. If the card issuer converts the amount on its statement, that conversion is handled by the issuer and does not change the USD amount in the VMOak order.
Submit a console ticket with the order number, billing date, payment method, displayed page status and necessary redacted records. For USDT-TRC20, provide the transaction ID; for card payments, provide the order-status information returned by Stripe. Do not submit a full card number, security code or other sensitive payment data.
Open consoleThe same physical node can handle graphical and command-line tasks, but the two channels respond differently to network fluctuations. Desktop experience depends on latency, jitter and bandwidth; SSH is better suited to scripts, repository operations and continuous builds.
For Xcode’s graphical interface, simulator monitoring, Final Cut Pro timeline work and other tasks requiring visual feedback. Before connecting, check client resolution, color and bandwidth settings.
For pulling repositories, build scripts, self-hosted runners, log checks, cache cleanup and artifact transfers. Use a dedicated key and restrict repository-token permissions.
Do not look only at download bandwidth. Sustained latency, jitter, packet loss and local Wi-Fi stability all affect mouse, keyboard and visual feedback. Start with a region close to the primary operator, disable unnecessary high-resolution display settings, compare wired and wireless performance, then decide whether to move highly interactive work to remote desktop.
The physical node is dedicated to one order, but that does not mean multiple people should control the same graphical session without coordination. Teams can manage access by project, but should avoid simultaneous operations that compete for foreground focus, build directories or local ports. Automation should use separate working directories, clear runner labels and concurrency limits.
A network disconnection is not the same as shutting down the physical node. Whether background processes continue depends on how the task was started, session configuration and application behavior. Start continuous builds, downloads or transcoding through process-management methods suited to long-running work and write logs; do not rely on a single foreground window to determine whether a task is still running.
Update temporary credentials immediately after the first connection, configure a dedicated SSH key and limit access to current project members. Never send private keys or complete access credentials in support requests. Revoke old credentials and reissue only the necessary permissions when a member leaves, a key may be exposed or the sharing scope changes.
Visit the connection support page for step-by-step checks covering remote desktop preparation, SSH keys, repository pulls, build-artifact transfers and common connection issues. If the issue remains unresolved, prepare the order number, region, incident time, client environment and redacted logs, then submit a console ticket.
View connection guideRemote access stops when the term ends. If you need to retain the environment, confirm renewal before the term ends; otherwise migrate repositories, build artifacts, valuable cache data and team configuration in advance.
Use the term and status shown in the order to schedule the final build and migration.
Migrate repositories, artifacts, configuration files and essential logs, then verify that the copies are readable.
Remove repository tokens, SSH keys, automation credentials and permissions belonging to departing members.
If you need to continue using the current environment, review the order status and confirm renewal before the term ends. Do not treat an unconfirmed renewal as active. If renewal details, the term or billing status do not match, submit a console ticket before expiration with the order number and requested action.
Remote access stops after expiration, so file exports, repository pushes, artifact uploads and credential cleanup must be completed before the service term ends. Do not treat the node’s local workspace as your only backup. Keep verifiable external copies and confirm that critical artifacts have left the node.
Cancellation handling depends on the order status, current term and service terms. State the order number, reason, requested end time and whether data migration is complete when submitting the request. The team will update the status through a ticket and will not ask you to submit complete access credentials through a public form.
First submit a console ticket with the order number, event timeline, page status and relevant redacted evidence. You may also email support@vmoak.com. Handling follows the service terms and order records; matters involving applicable law and dispute resolution are handled under the law of the jurisdiction where the platform operator is based and by the competent courts in that jurisdiction.
Choose between two real configurations, then confirm the term, one of six regions and any required storage add-ons. The complete USD billing breakdown is shown before submission.