The attributes behind your decision
- Resource model
- Virtual CPU and RAM
- Storage
- SSD or capacity-focused HDD
- Access
- Root or administrator
- Best fit
- Websites, applications, APIs
Choose resources around your workload
Start with measured memory use, simultaneous requests, and storage growth. Leave headroom for backups, updates, and traffic peaks. CPU count alone does not describe application performance: storage latency, software configuration, and resource contention also matter.
Linux, Windows, and administrative control
Use Linux for compatible websites, APIs, databases, and automation. Choose Windows when your application requires Windows Server or Remote Desktop. Check image availability and licensing in the order system. Root access lets you configure the server; it does not include ongoing administration.
Plan recovery before production
Define how much data you can afford to lose and how quickly the service must recover. Keep a backup outside the active server, test a restore, and document access recovery. Confirm whether backup storage, monitoring, and managed support are included in the selected service.