What Is a VPS?

What is it? #

A VPS is a virtual machine running on someone else's hardware, rented by the month. You get root access, an IP address, and a machine that behaves like your own server.

Physically, one powerful computer is divided into several virtual machines. Each has its own operating system, memory, disk and network address, isolated from the others.

What you get is control: any software, any configuration, any language runtime. What you take on is responsibility: updates, security, backups, monitoring and uptime.

That trade is the whole decision. A VPS is cheap and flexible, and nobody else is going to patch it for you.

Think of it like this #

Renting a flat in a converted building rather than a room in a shared house.

You have your own front door, your own utilities and you can rearrange the furniture. You are also the one who calls the plumber, and if you leave the door unlocked, that is your problem.

Simple example #

You have a web application, a database and a background worker. A single VPS with 2 CPUs and 4 GB of memory runs all three comfortably, for less than the cost of a managed platform.

Code #

What a VPS gives you

root access          install anything, configure anything
dedicated resources  your own CPU share, memory and disk
a public IP          reachable from the internet
full OS control      choose the distribution and the kernel version
predictable cost     a fixed monthly price, not per-request billing

What you are responsible for

security updates     nobody patches it for you
firewall and SSH     default configurations are not production ready
backups              the provider's snapshots are not a backup strategy
monitoring           you find out it is down when someone tells you, unless you set it up
uptime               a single VPS is a single point of failure

Sizing, in practice

1 CPU / 1 GB     a small site, a side project, a staging environment
2 CPU / 4 GB     a real application plus a database, comfortably
4 CPU / 8 GB     moderate traffic, several services, room to grow
8 CPU / 16 GB+   busy applications, or a dedicated database server

Start small. Resizing upwards takes minutes; over-provisioning from
day one costs money for capacity you may never need.

# What you actually have, once you are connected
nproc                    # CPU cores
free -h                  # memory
df -h                    # disk
cat /etc/os-release      # distribution
curl -s https://api.ipify.org    # public IP address

How it works #

A hypervisor divides the physical machine. Each VPS believes it has its own hardware, and the hypervisor enforces the boundaries between them.

CPU is usually shared rather than strictly dedicated. Most providers allow bursting above your nominal share, which is why performance can vary slightly between times of day on cheaper plans.

Memory and disk are genuinely allocated. Exceeding memory triggers the kernel's OOM killer, covered in the Linux processes lesson, rather than silently borrowing from a neighbour.

Snapshots are a provider feature that captures the whole disk. They are useful for rolling back a bad change, and they are not a substitute for real backups — they live in the same account, which can be lost or compromised.

Resizing usually requires a reboot and takes a few minutes. That makes vertical scaling genuinely practical, which is the point made in the system design track.

The IP address is yours while the machine exists. Destroying and recreating gives you a new one, which is why DNS records and TTLs matter during migrations.

Real-world use #

A single well-configured VPS runs a surprising amount. Applications serving thousands of users daily often need nothing more, and the simplicity is a genuine advantage.

The main reasons to move beyond one are availability and scale. One machine means maintenance downtime and no redundancy, so anything where downtime is costly needs at least two plus a load balancer.

Providers differ mainly in price, network quality and managed extras. The Linux inside behaves identically, which is why the skills transfer completely.

The hidden cost of a VPS is your time. Managed platforms charge more and handle patching, scaling and TLS for you. For a team without operations capacity, that can be the cheaper option overall.

Most of this track applies equally to a cloud instance from any large provider — the terminology differs, the work does not.

Common mistakes #

• Treating provider snapshots as a backup strategy.
• Over-provisioning on day one instead of starting small and resizing.
• Forgetting that a single VPS has no redundancy.
• Assuming the provider handles security updates.
• Underestimating the time cost of maintaining a server yourself.

Practice #

List everything your application needs to run: runtime, database, cache, background workers, disk for uploads. Estimate memory for each, then choose a VPS size with headroom. Write down who is responsible for updates, backups and monitoring in your setup.