A VPS is just a Linux computer you rent by the month. This walkthrough takes you from picking a plan to a running server you can actually log into — no prior experience required.

If you've never touched a server before, the ordering pages and control panels can feel like a wall of jargon. The good news: you only need to make four decisions to get started, and this guide covers each one.

Step 1: Choose a provider and plan

Every VPS provider sells roughly the same thing — a virtual machine with a set amount of CPU, RAM, and storage — wrapped in different pricing and panels. For a first server, ignore the marketing and look at three things:

  • RAM. 1–2 GB is enough for a first server running one or two small apps. More apps means more RAM.
  • Location. Pick a datacenter close to you or your visitors for lower latency.
  • Billing. Monthly billing is worth the small premium until you know you'll keep the server.

Our hosting comparison walks through how three popular providers differ on resources, billing, backups, and support.

Step 2: Pick an operating system

When you order, the provider asks which operating system to install. Choose a Linux distribution — and for your first server, make it an easy one:

  • Ubuntu LTS — the most documented option on the planet; almost every tutorial assumes it.
  • Debian — slightly leaner, just as well supported by self-hosting projects.
Avoid exotic or minimal images for your first server. The 50 MB you save isn't worth the missing tools when something goes wrong at 11 pm.

Step 3: Find your connection details

Within a few minutes of ordering, the provider emails you (or shows in its panel) the three things you need:

  • The server's IP address — four numbers separated by dots.
  • The root password (or instructions to set one).
  • Sometimes a web-based console link — useful as a backup way in, but slower than a real connection.

Step 4: Log in for the first time

On Windows, use PowerShell or Windows Terminal. On macOS or Linux, open Terminal. Then type:

# Replace the IP with yours; enter your password when asked
ssh root@203.0.113.10

The first time you connect, SSH asks you to verify the server's fingerprint — type yes. You're now standing at the controls of your own server.

Your first five commands

Run these before anything else. They update the system and show you what you have:

# Update the package lists and installed software
apt update && apt upgrade -y

# Check memory, disk space, and uptime
free -h
df -h
uptime

What to do next

Your server works, but right now it accepts password logins as root — the two most common attack targets on the internet. Your next stop is the SSH keys and basic server security guide, which takes about twenty minutes and closes both holes.

After that, the Docker Compose guide gets your first real app running, and the backups guide makes sure a mistake never costs you your data.