Self-hosting means renting a small virtual server (a VPS) and running open-source software on it yourself, in place of paying a company to run it for you. You swap a subscription for your own time and responsibility: updates, backups, security and uptime all become your job.
That's a good trade if you enjoy the tinkering, or if you need control over where your data lives. It's a bad trade for anything where an outage or lost data would cost you customers. If your only goal is a smaller software bill, count your hours first. Plan on about a day for a first setup, and the server needs a little attention every month after that.
If you still want to do it, the rest of this guide is the short path: pick a server, lock it down, run one app behind HTTPS, and back it up.
What's worth self-hosting, and what isn't
Start with tools that only you use, where a few hours of downtime is an annoyance. Four that suit a one-person business:
| Tool | What it does | Licence |
|---|---|---|
| Uptime Kuma | Alerts you when your sites go down | MIT |
| Plausible Community Edition | Cookie-free site analytics | AGPLv3 |
| n8n | Workflow automation | Sustainable Use License |
| Vaultwarden | Password vault server | AGPLv3 |
Some notes on each. Uptime Kuma is the easiest first app, but it can't warn you about an outage on the server it runs on, so use it to watch your other sites. Plausible's self-hosted edition gets two releases a year and leaves out a few features of the paid cloud version; my guide to privacy-friendly analytics options covers when the hosted plan is the better buy.
n8n isn't open source in the strict sense. Its licence allows free use for your own internal business purposes, which covers most solo operators. If you haven't automated anything yet, learn the basics on a hosted tool first; this introduction to connecting apps without code is the place to start.
Vaultwarden is an unofficial server that works with the Bitwarden apps and isn't affiliated with Bitwarden. I'd host it last. A password vault is the one item on this list where losing the data hurts badly, so wait until your backups are tested.
Two things I'd tell any beginner to leave alone:
- Email. Running a mail server is easy; getting Gmail and Outlook to accept what it sends is the hard part. Deliverability depends on IP reputation and on DNS records that take experience to get right. Pay a mail provider.
- Anything that stores customers' payment data. Use a hosted checkout such as Stripe or PayPal so card numbers never reach your server.
I'd add your main money-making site to that list until you've run a server for a few months without drama.
Choose a provider and an operating system
Hetzner, DigitalOcean, Akamai Cloud (formerly Linode) and Vultr are all established and all sell small servers billed by the hour or month. Prices and plan names change often, so compare them on each provider's pricing page. For sizing, Plausible's documentation recommends at least 2 GB of RAM, and that's a sensible floor for a server running two or three small apps.
For the operating system, pick a current long-term-support release. As of October 2026 that's Ubuntu 26.04 LTS, which gets standard security updates until April 2031 according to Ubuntu's release notes, or Debian 13. Either works with every command below. Ubuntu has more beginner tutorials written for it.
Before you create the server, make an SSH key on your own computer and paste the public half (the .pub file) into the provider's "SSH keys" field:
ssh-keygen -t ed25519
Lock the server down on first login
A new server starts receiving automated login attempts soon after it goes online. These four steps take about fifteen minutes.
1. Create a regular user. Log in with ssh root@YOUR_SERVER_IP, then create an account with sudo rights and give it a copy of your key. I've called it deploy; use any name.
adduser deploy
usermod -aG sudo deploy
cp -r /root/.ssh /home/deploy/
chown -R deploy:deploy /home/deploy/.ssh
Keep that window open. In a second terminal, confirm that ssh deploy@YOUR_SERVER_IP works and that sudo -v accepts your password. Don't go further until both do, because the next step closes the door you came in through.
2. Turn off root and password logins. As deploy, run sudo nano /etc/ssh/sshd_config.d/00-hardening.conf and add:
PermitRootLogin no
PasswordAuthentication no
KbdInteractiveAuthentication no
Then check the file for mistakes and restart SSH. The third command should print no for both settings.
sudo sshd -t
sudo systemctl restart ssh
sudo sshd -T | grep -E 'permitrootlogin|passwordauth'
3. Enable the firewall. Allow SSH and web traffic, and nothing else.
sudo apt update && sudo apt install -y ufw
sudo ufw allow 22/tcp
sudo ufw allow 80,443/tcp
sudo ufw enable
4. Turn on automatic security updates. Ubuntu usually ships with this enabled; running it again does no harm.
sudo apt install -y unattended-upgrades
sudo dpkg-reconfigure -plow unattended-upgrades
This patches the operating system only. Kernel updates still need an occasional reboot, and your apps are updated separately (see below). The wider habits around passwords and two-factor logins are in my account security guide for creators.
