Current environment
Existing CPU/RAM, disk use, OS, web stack and monitoring data if available.
Share the workload, current resource use and management preference. This form does not collect payment and is not a substitute for the final SERVER1 order.
For the best sizing answer, include measured CPU/RAM use, storage data size, peak traffic or concurrency, operating system, control panel, database, backups and whether this is a new deployment or migration.
Existing CPU/RAM, disk use, OS, web stack and monitoring data if available.
Busy-hour traffic, concurrent users, queue depth or job schedule — whichever describes your workload best.
State whether your team wants root-level ownership or expects provider operational support.
Data size, DNS control, acceptable downtime and target cutover date if you are moving an existing service.
A useful recommendation starts with the workload, not a package name. Share current usage, expected traffic and whether you want server administration included.