Order guidance

Tell us what you run; we will narrow the VPS choice.

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.

Quick answer

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.

Useful inputs

What makes a sizing request actionable

Current environment

Existing CPU/RAM, disk use, OS, web stack and monitoring data if available.

Peak load

Busy-hour traffic, concurrent users, queue depth or job schedule — whichever describes your workload best.

Management

State whether your team wants root-level ownership or expects provider operational support.

Migration constraints

Data size, DNS control, acceptable downtime and target cutover date if you are moving an existing service.

Sizing request

Tell us what you plan to run

A useful recommendation starts with the workload, not a package name. Share current usage, expected traffic and whether you want server administration included.

Do not include passwords, private keys, payment-card data or other secrets.