Before you rent anything, it really helps to understand what you're renting. This module gives you a clear, jargon-free mental model of a VPS — so the next steps feel obvious instead of scary.
Be able to explain, in your own words, what a VPS is, how it's different from other ways of hosting, and roughly what size you need.
The apartment building metaphor
Imagine a big apartment building. The building is one giant physical thing, but inside it's divided into separate apartments. Each apartment has its own locked door, its own space, and its own residents who can't wander into yours.
A VPS works the same way. There's one powerful physical computer (the building) sitting in a data center. Software slices it into several separate "apartments." You rent one apartment. It's yours, it's locked, and the neighbors can't get in — even though you're all in the same building.
That's what the letters mean
Virtual = your "apartment" is created by software, not a whole separate building. Private = it's yours alone, walled off from the neighbors. Server = a computer whose job is to answer requests from the internet.
VPS vs. the other options
A VPS is one of several ways to put a site online. Here's the plain-language version of each, from simplest to most powerful.
Shared hosting — a room in a shared house
The cheapest, oldest option. You and hundreds of others share one computer, and the host controls almost everything. Easy, but limited: you usually can't install your own tools (which we need for Claude). Think "a bedroom in a crowded house — you can't remodel."
A VPS — your own apartment
Your own slice, with full control. You can install anything, run any program, and it stays yours. This is the sweet spot for learning and for the projects in this course, because we need the freedom to install Node.js, Claude Code, and a web server.
"The cloud" — renting from a giant, flexible landlord
Big platforms like AWS or Google Cloud. Enormously powerful and flexible, but also complex and easy to overspend on as a beginner. Honestly, a VPS is a simple, friendly corner of "the cloud" — you just don't have to learn the hundred other buttons yet.
Managed platforms — a hotel
Services like Netlify or Vercel where you hand over your code and they run it for you. Wonderful for certain projects and very hands-off — like a hotel where housekeeping does everything. But you learn less about how the machine actually works, and you can't do the full "own your server" journey. We mention when these are a smart choice, too.
Why a VPS for this course?
Because the goal is for you to understand and control the whole thing — the computer, the code, the address, the security. A VPS is the best classroom for that, and the skills carry over to every bigger system later.
Do you actually need a VPS?
Fair question! Sometimes a simpler option is genuinely better. Here's an honest guide:
- Just a plain, unchanging web page? A free "static host" (like GitHub Pages or Netlify) might be all you need.
- Want to learn how servers really work, run your own programs, and own the whole stack? A VPS. (That's us.)
- Building something huge with millions of users? You'll grow into full cloud platforms — but a VPS is still the perfect place to start and learn the fundamentals.
Decoding the specs (without the headache)
When you pick a VPS in Module 2, you'll see a few numbers. Here's what each one means, using everyday comparisons. A typical small plan reads something like this:
1 vCPU # one "brain" — plenty for a first project
1 GB RAM # short-term memory while programs run
25 GB SSD # storage — like the hard drive on a laptop
1 TB transfer # how much data can flow in/out per month
$5 / month- vCPU — the "brain" that does the thinking. vCPU means a virtual one (a share of the real chip). 1 is fine to start.
- RAM — short-term memory the computer uses while programs are running. More RAM = more things at once. 1 GB is enough for a first project; 2 GB is comfy.
- Storage (SSD) — the long-term "closet" where your files live even when powered off. 25 GB is roomy for a beginner site.
- Bandwidth / transfer — how much data your site can send to visitors each month. 1 TB is a lot — you won't come close early on.
The beginner's answer to "which size?"
The smallest plan (around $5/month) is enough to finish this course. But for a little more — the plan we recommend, Hostinger's KVM 2 (2 vCPU, 8 GB RAM) at $13.99/month — you get real headroom: run your app, a database, and extra projects all at once. Either works; you can always resize later.
✏️ Hands-on: sketch your project
Let's make this real. Grab paper or a notes app and jot down quick answers. This takes five minutes and makes Module 2 painless.
-
What do you want to put online?
One sentence is enough. "A personal homepage about me." "A page with links to my socials." "A tiny tool that does one useful thing."
-
Will many people visit at once on day one?
Almost certainly no — and that's great. It means the smallest server is perfect. (If you ever go viral, resizing up takes minutes.)
-
Circle your starting size.
The minimum that works: 1 vCPU, 1 GB RAM, ~25 GB storage (~$5/mo). Our recommended pick with breathing room: 2 vCPU, 8 GB RAM, 100 GB NVMe (Hostinger KVM 2, $13.99/mo). Write down which one you want — you're ready for Module 2.
You did it
You can now explain what a VPS is and what size you need. That's genuinely the hardest conceptual hurdle in the whole course — and it's behind you.
- A VPS is your own private apartment inside one big shared computer.
- It gives you the freedom to install your own tools — which shared hosting doesn't.
- Specs decoded: vCPU = brain, RAM = short-term memory, SSD = storage, transfer = monthly data.
- The smallest plan (~$5/mo) is right for this whole course.