| Cost model |
Choose daily, weekly, monthly, or quarterly billing; costs follow the project term. |
Pay for the equipment upfront, then continue paying for space, networking, and routine management. |
Usually billed by instance term, but verify shared-resource limits and configuration definitions. |
| Delivery readiness |
Choose the machine, location, term, and add-ons in the console; delivery records stay centralized. |
Complete purchasing, receiving, cabling, remote access, and device registration. |
Usually quick to create, but the underlying resources and host environment depend on the provider. |
| Isolation |
Each order maps to a dedicated physical node; compute and local storage are not shared with other tenants. |
Your team controls the equipment, with clear resource boundaries. |
Resources may run in a shared host environment and are not equivalent to a dedicated physical machine. |
| Upgrade flexibility |
Choose a different plan, location, or extra capacity for the next term. |
Upgrading usually means adding equipment, replacing hardware, or redeploying. |
You can switch instance sizes, but must revalidate performance, storage, and environment consistency. |
| Best suited for |
Project-based development, continuous CI, temporary scaling, remote experiments, and teams that need physical resource boundaries. |
Teams with stable long-term workloads, equipment management capabilities, and a need for on-site control. |
Workloads that do not require physical isolation and can accept a shared environment. |