| Upfront cost |
Pay for the selected term without taking on the full hardware purchase upfront |
Requires an upfront hardware purchase plus accessories, networking, and hosting arrangements |
Typically billed as a resource plan; confirm sharing and usage limits |
| Delivery time |
After selecting the configuration, node, and term, proceed to checkout; use the real-time status returned by the console |
Depends on purchasing, shipping, acceptance, networking, and remote-access setup |
Usually quick to create, but it is not an independent physical node |
| Resource exclusivity |
Every order maps to a dedicated physical machine, not a virtual machine |
The buyer has exclusive use of the equipment |
Underlying resources and isolation depend on the service implementation |
| Management responsibility |
VMKeep handles node-side operation and remote recovery assistance; users handle code, data, credentials, and the application environment |
The buyer handles equipment, networking, remote access, troubleshooting, and replacement |
The platform manages the virtualization layer; users still manage the system and application environment |
| Upgrade flexibility |
Choose a different configuration and term from the three-plan catalog in your next order |
Upgrades usually require a new purchase, hardware replacement, or redeployment |
Plans may be adjusted, but available resources and performance limits depend on platform rules |
| Best for |
iOS/macOS builds, self-hosted runners, MLX inference, and remote graphical work |
Long-term fixed workloads and self-managed internal infrastructure |
General workloads that do not require dedicated physical resources |