Choosing a VPS is a handful of decisions made in the right order. Get the location and size right and you’ll rarely need to move; get them wrong and you’ll be migrating within months. Work through these steps.

Step 1: Describe your workload

Write down:

  • What will run (website, app, database, VPN, game server, containers)?
  • Where are the users?
  • Expected traffic now and in a year?
  • Any special needs: Windows, email sending, many IPs, China access, large storage?

Step 2: Choose the location

Location is the hardest thing to change later (IPs, DNS, firewall allow-lists all depend on it).

Users mainly in Good choice
North America, Europe, Latin America USA (Los Angeles, New York, Chicago, Miami)
Mainland China Hong Kong with CN2 + BGP
Japan, Korea, Taiwan, wider Asia-Pacific Tokyo or Hong Kong
Southeast Asia Hong Kong (or a Singapore dedicated server)

Test before buying: ping and traceroute each location’s test IP from your users’ networks. See USA vs Hong Kong VPS and Singapore vs Hong Kong.

Step 3: Size CPU and RAM

Workload Starting point
Static site, small app, VPN, bot 1–2 vCPU, 2 GB RAM
WordPress / CMS with caching 2 vCPU, 4 GB
WooCommerce, several sites, small database 4 vCPU, 8 GB
Several containers, CI, moderate databases 4–6 vCPU, 8–12 GB
Windows Server 2+ vCPU, 4 GB+, 50 GB+ disk
Game servers See game server VPS guide

RAM is usually the first limit. Start where you need to be today, with headroom, and upgrade when monitoring shows sustained pressure.

Step 4: Storage

  • SSD at minimum; check random I/O, not just capacity.
  • Size for OS + application + data + logs + local backups, with 30% free.
  • For large media or backup archives, a high-capacity plan like a Storage VPS is cheaper than scaling a general plan.

Step 5: Bandwidth

Understand the model — port speed, monthly transfer or unmetered — and estimate your monthly traffic. See VPS bandwidth explained.

Step 6: Operating system

Step 7: IPs and email

  • Need several IPs (multiple SSL sites on separate IPs, SEO hosting, proxies)? Check additional IP pricing or a Multi-IP VPS.
  • Sending email from the server? You need open outbound SMTP ports and rDNS. On VPS.DO, that’s the USA VPS only — see Email VPS. Otherwise, use a transactional email service.

Step 8: Virtualization and control

  • KVM for a full VM with your own kernel (Docker, custom firewalls, Windows).
  • A control panel with reboot, OS reinstall and VNC console — essential when SSH fails.
  • Root/administrator access.

Step 9: Provider policies

  • Support: how to reach them, response times.
  • Refund policy: a money-back window lets you test real performance.
  • Acceptable use: mail, proxies, high CPU, crypto — know the rules.
  • Upgrades: can you resize without migrating?
  • DDoS: what happens during an attack, and is protection available?

Step 10: Test during the first days

Run your real workload, check steal time (top), disk I/O and latency from your users. Our cheap VPS value checklist has a quick test script.

VPS.DO at a glance

  • KVM VPS in the USA, Hong Kong and Tokyo, with test IPs for every location
  • SSD storage, instant setup, VNC console and OS reinstall in the control panel
  • Windows Server on plans with 50 GB+ disk (180-day trial licence)
  • Plan upgrades by ticket; 24/7 ticket support
  • 7-day money-back guarantee (once per customer per data center)
  • Dedicated servers in Silicon Valley, Hong Kong, Tokyo and Singapore when you outgrow a VPS

Summary

Decide location first, then size RAM/CPU/storage for today with headroom, pick the OS your software expects, check IP and email needs, and use the refund window to test. Next: VPS hosting from first login to production.

  • VPS
  • Buying Guide