What is VPS hosting?

How virtualisation works

One physical server runs a hypervisor, which divides the hardware into isolated virtual machines. Each VM boots its own operating system and cannot see or borrow another VM's memory. With KVM virtualisation the resources you buy are genuinely reserved, which is why a busy neighbour cannot slow your site down the way it can on shared hosting.

Shared vs VPS vs dedicated

Signs you have outgrown shared hosting

• Response times climb whenever traffic does
• You need a specific PHP, Node or Python version, or a background worker
• You are hitting process, memory or inode limits
• You want staging, deployment keys or a database you can tune
• Compliance requires isolation you cannot get on a shared pool

What you are responsible for

Root access cuts both ways. On an unmanaged VPS, operating system updates, firewall rules, TLS certificates, backups and monitoring are yours. If nobody on the team wants that job, either choose managed hosting or add a management plan — an unpatched server is worse than shared hosting, not better.

# the minimum after first boot
sudo apt update && sudo apt upgrade -y
sudo ufw allow OpenSSH && sudo ufw enable
sudo sed -i 's/^#\?PermitRootLogin.*/PermitRootLogin no/' /etc/ssh/sshd_config
sudo systemctl restart ssh

How to size a VPS

1. 1

   Start from concurrency

   Estimate simultaneous requests, not monthly pageviews. Most brochure sites never exceed a handful.

2. 2

   Match RAM to the stack

   A PHP application with a database is usually happy at 4 GB; add memory before CPU when things feel slow.

3. 3

   Prefer NVMe

   Disk latency is the most common invisible bottleneck on database-backed sites.

4. 4

   Watch for a fortnight

   Then resize once with real data instead of guessing twice.