I bought a VPS — now what? A beginner's first steps

So you rented a server. Maybe it was cheap, maybe a tutorial told you to, maybe you just wanted to stop paying every month for something you could host yourself. Either way, the welcome email arrived with an IP address, a password, and… that's it. No dashboard, no obvious next step.

If you're staring at that email wondering what you actually bought — this is for you.

What a VPS even is

A VPS — a "virtual private server" — is just a computer you rent that's always on and always connected to the internet. That's the whole idea. It lives in a data center instead of under your desk, it never sleeps, and it has a public address (the IP) so other people's browsers can reach it.

That's what makes it useful: anything you put on it is available to the world, around the clock, without your laptop having to stay open. A website, a blog, a password manager, a small app — all things a server is good at.

The catch is that a fresh server is empty. It doesn't come with any of that. You have to put it there. And that's where most people hit the wall.

The four things every new server needs

No matter what you eventually run, the setup has the same shape. Every server needs:

1. A safe way to get in. Right now, anyone with the password could try the door. Step one is locking it down properly.
2. Something to run. The actual point — a website, an app, a tool you want to host.
3. A name and a padlock. People shouldn't have to type an IP address. You point a domain at the server and turn on HTTPS so visitors get the secure padlock.
4. A safety net. Backups, so that if something breaks — or you break it — you can get back.

Four things. None of them optional. All of them, traditionally, their own little project.

The hard way vs. the shortcut

The traditional path means learning a new vocabulary for each of those four: SSH and firewalls for access, web servers and Docker for running things, DNS and certificates for the domain, and some backup routine you'll probably set up once and forget. It's not that any single step is impossible — it's that there are a lot of them, each fails in its own quiet way, and the error messages tend to assume you already know the answer.

The shortcut is to skip the vocabulary. With Server Manager you connect the server once, then describe what you want in plain English — "lock this server down", "put a WordPress site here", "point my domain at it" — and the assistant does the sysadmin part. You stay in charge of what happens; it handles how.

Your first fifteen minutes

If you want to actually do something today, here's a sensible order:

• Secure the front door first. Before anything else, get access locked down. Everything else sits behind it.
• Put one thing on it. Pick a single, concrete goal — a personal site, a blog, a tool you've wanted to self-host. (If it's WordPress, we wrote a step-by-step: how to host WordPress without touching the terminal.)
• Give it a real address. Point a domain at the server and switch on HTTPS so it looks and feels legitimate.
• Turn on backups. Future-you will be grateful the first time something goes sideways.

You don't have to do all four at once. Do the first, watch it work, and the rest stops feeling abstract.

It's your server — keep it that way

The reason to go through any of this — instead of renting a fully-managed box where someone else holds the keys — is ownership. Your provider, your data, your costs, your choices. The goal was never to become a system administrator; it's to get the benefits of running your own server without having to. That's the point: the server stays yours, and the hard parts stop being your problem.

If you want to see how each piece works in more depth, the help guides walk through them one at a time.