Start with the workload, not the plan name
Document the application runtime, expected traffic, database size, storage growth, background jobs, control-panel requirement and whether email will run on the same system. This prevents paying for capacity that does not solve the real bottleneck.
Compare resources honestly
CPU, RAM and NVMe storage describe different constraints. CPU affects concurrent processing, RAM affects application and database working space, and storage affects both capacity and I/O. Network allowance and port speed are not the same thing.
- Check vCPU, RAM, NVMe and transfer allowance
- Select the required billing period
- Confirm whether IPv4 is included or optional
- Leave capacity for updates, logs and temporary files
Understand the managed scope
The order identifies the operating baseline and selected support level. Application development, third-party software repair, content work and emergency recovery are separate unless explicitly included.
Configure add-ons deliberately
Operating system, control panel, network options, backups and enhanced support remain separate line items. A licensed panel can add recurring cost. A backup product must state retention and restore scope.
Review the cart and invoice
Confirm the domain, billing cycle, recurring charges and one-time work before paying. Cryptocurrency quotes can expire even when the USD invoice remains open.
Payment confirmation
Broadcasting a transaction does not immediately provision a server. The invoice remains pending until the provider reports the required confirmations or staff verifies a manual transaction. Use only the asset and network shown.
Provisioning and delivery
After confirmation, staff reviews capacity, operating-system compatibility, licensed software and migration requirements. Credentials and service details are delivered through the protected account workflow.
First-login checklist
- Change temporary credentials where instructed
- Store recovery data in a password manager
- Confirm SSH, console or panel access
- Apply application-specific security controls
- Test the backup and recovery path
- Report discrepancies before production traffic moves
Plan for change
Upgrades can require a restart, maintenance window or migration. Keep independent backups and current DNS documentation.