Singapore, Tokyo, Seoul, and Hong Kong. Every location provides a dedicated physical Mac mini—not a virtual machine. Start by deciding how you'll connect, then choose where to run your builds.
Apple Silicon M4 / M4 Pro · From $20.1/day · Check the control panel for real-time availability
All four data centers offer Glide M4 and Cruise M4 Pro. The coverage areas below are a starting point, not a guarantee of routing by any specific carrier. For remote desktop performance, consider the full path between your team's network and the node.
Serving teams in Singapore and across Southeast Asia. If your team regularly connects to a desktop, checks the simulator, or downloads build artifacts from this region, start by testing this location.
Serving teams in Japan and nearby regions. If you often debug Xcode, review interfaces, or inspect UI test results from a desktop, first check the connection from your team's network to Tokyo.
Serving teams in Korea and nearby regions. If you regularly open simulators, inspect failure screenshots, or have engineers take over the runner directly, put Seoul on your shortlist for testing.
Serving teams in Hong Kong and nearby regions. Alongside desktop responsiveness, check the locations of your code repository, dependency sources, and artifact destination. Optimizing just one leg of the network path may not be enough.
Round-trip measurements depend on the network you're connecting from. We don't publish unverified latency figures. Use the four locations below to identify the paths and workloads to test—geographic distance alone doesn't determine latency.
| Node | Primary coverage | What to check for round-trip latency | Workflows to test |
|---|---|---|---|
| SIN · Singapore | Singapore and Southeast Asia | Connect from your team's office network and check interactive responsiveness and jitter at different times of day. | Remote desktop, build execution, artifact downloads. |
| TYO · Tokyo | Japan and nearby regions | Test desktop input, screen updates, and connection stability from the network you normally use. | Xcode debugging, simulator checks, unattended builds. |
| SEL · Seoul | Korea and nearby regions | Check the interactive connection between your team and the node, and record file transfer times separately. | Remote desktop access, UI test reviews, log and artifact transfers. |
| HKG · Hong Kong | Hong Kong and nearby regions | Test the paths from your office network, code repository, and artifact destination to the node separately. | Collaborative development, continuous builds, code and artifact sync. |
These are testing guidelines; actual results depend on your network. A single round-trip measurement doesn't represent sustained throughput or predict Xcode compile times. Consider cross-carrier routing, packet loss, and jitter as well.
Use the same client, network, and project for each test. For desktop checks, measure input response and screen updates. For builds, record checkout, compile, and upload times separately. Don't mistake a slow dependency download for insufficient physical machine performance.
Glide M4 comes with Apple Silicon M4, 16GB memory, and a 256GB SSD. Cruise M4 Pro comes with Apple Silicon M4 Pro, 64GB memory, and a 2TB SSD. Choose a model for your workload, then select a data center based on connectivity—there's no need to learn a different model lineup for each location.
| Physical Mac model | Singapore · SIN | Tokyo · TYO | Seoul · SEL | Hong Kong · HKG |
|---|---|---|---|---|
| Glide M4 | Available | Available | Available | Available |
| Cruise M4 Pro | Available | Available | Available | Available |
Both models are dedicated to one customer. Xcode and the simulator run directly on physical Apple Silicon. Choosing a data center doesn't turn the node into a shared runner or add a virtualization layer.
A team that works at the desktop all day has different network needs from one that only collects build results overnight. List your most common tasks, then compare locations, models, and billing periods.
Start with the node closest to your team, then test input response and screen updates over your actual office network. Simulator debugging, layout reviews, and interactive troubleshooting are more sensitive to jitter. Proximity is a good starting point, not a final verdict.
When there's little hands-on interaction, round-trip latency may matter less. Focus on repository checkout, dependency downloads, and artifact upload times, then compare the available models and billing periods. Glide M4 is $100.7/month and suits an initial test of a typical single-app pipeline. Run your own project to confirm it meets your build times.
For Unity exports, multi-target archives, and long-term artifact retention, consider memory, SSD capacity, and transfer paths together. Cruise M4 Pro offers 64GB memory and a 2TB SSD. For large transfers, measure the full upload and download time rather than relying on a single round-trip test.
Choose a location based on the people who use the desktop most, and send build artifacts into your team's existing storage workflow. Start with daily billing to test during a release week; there's no need to migrate your entire pipeline first. Once you've confirmed your toolchain, signing, and artifact paths, decide whether to deploy long term.
Each node is a physical machine, not a virtual instance on a shared host. The entire Mac mini is assigned to one customer, who manages their own code, build credentials, and artifacts. Plan for backups and end-of-rental data handling as part of your team's workflow.
For the rental period, the entire machine is assigned to one customer. Your team can use the macOS graphical interface and command line to run its own toolchain. The machine's storage and physical network interface aren't shared with other tenants.
Nodes run year-round, 365 days a year. Check the control panel for service status and account instance details.
When a node expires without renewal, service stops and its entire disk is erased. Back up your code, environment configuration, certificates, and any build artifacts you need to keep. Don't leave your only copy on a rented node.
Test that your backups can be restored before expiry; confirming that files have been copied isn't enough.
Moving to another data center requires a new node, with data sync handled by your team. Set up your toolchain and runner, run a build, tests, and archive, then switch your pipeline to the new target.
Migration doesn't move your existing machine, and data won't appear in the new data center automatically.
Your primary users' locations, where code and artifacts will be transferred, and your preferred model and billing period. For help choosing a location, email support@vmfly.com. If you already have an account, submit a support ticket in the control panel with the node ID and time the issue occurred.
Four Asia-Pacific locations, each with a dedicated physical Mac. From $20.1/day. Confirm your node and billing period on the configuration page.