
Core takeaway
- What self-hosting means: a VPS is an always-on computer reachable from anywhere, so it can run your own file sync, bookmarks, analytics or Git server instead of a company running them for you.
- Know the cost: the guide covers what each kind of application costs in memory and effort, and what not to host on a small VPS.
- Run them safely: use the safe pattern for several applications side by side, with a worked example, and decide who can reach each one.
- Rule: self-host what you will maintain, and back up what you cannot replace.
Disclosure: con1ainer.com participates in affiliate programs. This article contains no affiliate links. See the Affiliate & Commercial Disclosure.
Two quick looks at how a self-hosting plan grows past the plan.
A VPS can host a website, and that is how most people use theirs. But a VPS is a general-purpose computer that is switched on all the time and reachable from anywhere. That makes it a good home for a long list of other programs: your own file sync, your own bookmarks, your own analytics, your own Git server.
Running those yourself, instead of paying a company to run them for you, is called self-hosting. This guide covers what is worth self-hosting, what each kind of application costs in memory and effort, what you should not host on a small VPS, and the safe way to run them side by side. Every term is explained as it appears.
What Self-Hosting Means
Self-hosting is running software on a server you control, rather than using the same service from a company’s servers. Instead of storing your files with a cloud storage company, you run an open-source file-sync program on your VPS. Your data lives on your server, and you decide who can reach it.
People do it for four reasons:
- Control. Nobody changes the pricing, removes a feature, or shuts the service down on you.
- Privacy. Your data is not on someone else’s system, to be scanned, analysed, or lost in their breach.
- Cost. Several small services on one VPS can cost less than several separate subscriptions.
- Learning. You understand how services work because you run them.
There are honest reasons not to as well, and they matter as much:
- You are the system administrator. Updates, security, backups, and repairs are yours.
- You are also the backup department. A cloud service stores your data on redundant systems. Your VPS stores it on whatever you set up.
- Reliability is up to you. A cloud service has a team on call. You have a phone alert.
- Mistakes cost more. Misconfigure a public service and the damage is yours.
The sensible approach is to self-host things you are willing to maintain, and to leave the rest with professionals.
What Will Run on Your VPS
Every application falls roughly into one of three weights. These are approximate and vary with how much you use them, so check each project’s own documentation for current requirements before you install it.
| Weight | Typical memory use | Examples of what fits this weight |
|---|---|---|
| Light | Tens of megabytes up to roughly 200 MB | Bookmark managers, RSS readers, uptime monitors, Git hosting for a few users, a VPN |
| Medium | Roughly 200 MB to 1 GB | Wikis, analytics with a database, workflow automation, file sync with many files |
| Heavy | 1 GB and above, sometimes much more | Photo libraries with machine-learning features, large analytics databases, chat servers, game servers |
A realistic starting guide for how many you can run:
| VPS memory | What fits |
|---|---|
| 1 GB | Three or four light applications, with no heavy database |
| 2 GB | Several light ones and one or two medium ones |
| 4 GB | A mix of light and medium, or one heavy application plus several light ones |
| 8 GB or more | A substantial personal stack, or one demanding application |
These are starting points, not promises. Measure after you install each application, using the checks in How to Monitor a VPS: Uptime, Resources, and Alerts. The reasoning behind memory sizing is in How Much RAM Does a Web Server Need?
What You Can Self-Host
This is a map, not a recommendation to run everything. Each table lists well-known open-source projects, what they do, and their weight. Project details and features change, so check the project’s own site before you commit.
Files, documents, and sync
| Application | What it does | Replaces | Weight |
|---|---|---|---|
| Nextcloud | File storage and sync, with calendars, contacts, and optional add-ons | A cloud storage and office suite subscription | Medium to heavy |
| Syncthing | Keeps folders in sync between your own devices, directly, with no central storage | A file-sync service | Light |
| Paperless-ngx | Scans, reads (OCR, meaning text recognition), and files your paper documents so you can search them | A document scanning service | Medium to heavy |
| BookStack | A wiki for notes and documentation, organized into books and chapters | A hosted wiki or note service | Light to medium |
Passwords and private data
| Application | What it does | Replaces | Weight |
|---|---|---|---|
| Vaultwarden | A lightweight server that works with the Bitwarden apps and browser extensions. It is an unofficial, community-built implementation | A hosted password manager | Light |
| Immich | Backs up and organizes your photos and videos, with search and face recognition | A cloud photo service | Heavy |
These two deserve extra thought. A password vault is the highest-stakes thing you can host, because losing it or exposing it is a disaster. It must run over HTTPS, be backed up off the server, and stay updated. If you are not confident doing all three, use a reputable hosted password manager. Immich changes quickly, and updates sometimes include breaking changes, so read the release notes before every upgrade.
Reading, saving, and personal tools
| Application | What it does | Replaces | Weight |
|---|---|---|---|
| Miniflux and FreshRSS | RSS feed readers. RSS is a format websites use to publish new posts so a reader can collect them | A hosted feed reader | Light |
| Linkding | Saves and searches your bookmarks | A bookmarking service | Light |
| Jellyfin | Streams your own movies, music, and shows to your devices | A media streaming server | Medium, with high CPU use when converting video formats |
If you stream media from a VPS, remember that only content you have the right to use belongs there. Also check the bandwidth and storage limits of your plan, which video can exhaust quickly.
Website tools
| Application | What it does | Replaces | Weight |
|---|---|---|---|
| Umami | Simple, privacy-focused website analytics | A hosted analytics service | Light to medium |
| Matomo | Full-featured analytics, run on PHP and MariaDB | A hosted analytics service | Medium |
| Plausible Community Edition | Lightweight analytics interface that depends on a heavier database underneath | A hosted analytics service | Medium to heavy |
| Ghost | A blogging and newsletter platform | A hosted blog platform | Medium |
| WordPress | The most popular site builder | A site builder subscription | Light to medium |
On WordPress specifically, read WordPress on a VPS: Is It Worth Leaving Shared Hosting?
Developer tools
| Application | What it does | Replaces | Weight |
|---|---|---|---|
| Forgejo or Gitea | Hosts Git repositories (the version history of code) with a web interface | A hosted code platform | Light |
| Woodpecker CI | Runs automated tests and builds when you push code. CI means continuous integration | A hosted build service | Medium |
| code-server | Runs a code editor in your browser, on the server | A cloud development environment | Medium to heavy |
| n8n | Connects apps and automates tasks with a visual workflow editor | An automation subscription | Medium |
code-server gives whoever logs in a full command line on your server. Never expose it to the open internet with only a password.
Monitoring and network tools
| Application | What it does | Replaces | Weight |
|---|---|---|---|
| Uptime Kuma | Checks your websites and services and alerts you when one fails | A hosted uptime monitor | Light |
| WireGuard | A fast, modern VPN. A VPN is an encrypted tunnel between your device and your server | A paid VPN, for some uses | Light |
| AdGuard Home or Pi-hole | Blocks advertising and tracking domains at the DNS level for your own devices | Browser-based ad blocking, for some uses | Light |
If you run a DNS blocker on a public VPS, restrict it to your own devices, for example by allowing only VPN connections. A resolver open to the whole internet is abused by attackers to amplify attacks on other people, which can get your server blocked.
Games and communities
| Application | What it does | Weight |
|---|---|---|
| Minecraft or similar game servers | A multiplayer game for you and friends | Heavy. Needs generous memory and strong single-core CPU speed |
| Matrix Synapse, Mattermost | Private chat for a team or community | Medium to heavy |
What You Should Not Self-Host on a Small VPS
| Do not host | Why |
|---|---|
| Your own email server | Deliverability is hard. Messages from new servers are routinely rejected or sent to spam. Many providers block the outgoing mail port by default, and you must constantly manage blocklists, SPF, DKIM, DMARC, and spam filtering. Use a hosted email service |
| A public DNS resolver | Attackers abuse open resolvers to amplify attacks on other networks |
| Anything whose only copy is on the VPS | A server can be lost to a mistake, a provider fault, or an attack. Keep copies elsewhere |
| Admin tools exposed to the whole internet | Database managers, dashboards, and code editors are common targets. Put them behind a VPN or an allow-list |
| Anything your provider’s rules forbid | Providers publish an acceptable use policy. Public proxies, VPN exit nodes, mass mailers, torrent seeding, and cryptocurrency mining are commonly restricted. Read it first |
The last row matters more than people expect. A provider that suspends your VPS over a rules violation takes everything on it offline together.
The Safe Pattern for Running Several Applications
One approach scales cleanly from one application to ten.
- Run each application in its own container, described in its own Compose file. Containers keep applications and their dependencies separate, and a file describes each setup exactly. See Docker on a VPS: A Practical Starting Point.
- Publish each application’s port on
127.0.0.1only. That keeps it off the public internet, and it avoids Docker’s habit of bypassing the firewall. - Put one reverse proxy in front of everything. Nginx on the host receives visitors on ports 80 and 443 and passes each request to the right application, chosen by its address.
- Give each application its own subdomain, such as
links.example.com. A subdomain is a name added in front of your domain, set up with its own DNS record. - Issue an HTTPS certificate for each, with Certbot.
- Decide who may reach each one. The next sections explain how.
A worked example: Linkding
Linkding is a small bookmark manager, so it is a safe application to practice on.
Create a folder and a Compose file:
mkdir -p ~/linkding && cd ~/linkding
nano compose.yaml
services:
linkding:
image: sissbruecker/linkding:latest
restart: unless-stopped
ports:
- 127.0.0.1:9090:9090
environment:
LD_SUPERUSER_NAME: ${LD_USER}
LD_SUPERUSER_PASSWORD: ${LD_PASSWORD}
volumes:
- linkding_data:/etc/linkding/data
volumes:
linkding_data:
Create the file that holds the login details, using your own long, random password:
nano .env
LD_USER=yourname
LD_PASSWORD=replace-with-a-long-random-password
Start it:
docker compose up -d
docker compose ps
The latest tag is used here because exact version numbers change. Once it works, replace it with the specific version tag shown on the project’s releases page, as the Docker guide explains, so an update never arrives by surprise.
Now make it reachable. First, in your DNS panel, add an A record for links.example.com pointing to your VPS IP address. Then create an Nginx configuration:
sudo nano /etc/nginx/sites-available/links.example.com
server {
listen 80;
server_name links.example.com;
location / {
proxy_pass http://127.0.0.1:9090;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
Enable it, test it, reload, and request the certificate:
sudo ln -s /etc/nginx/sites-available/links.example.com /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx
sudo certbot --nginx -d links.example.com
Certbot adds the HTTPS settings to the file and sets up automatic renewal. Open https://links.example.com and log in. The same four steps work for every other application on this list: container, local port, subdomain, certificate.
Decide Who Can Reach Each Application
Every public address is tried by automated scanners within hours. Match the protection to the stakes.
| Method | How it works | Good for |
|---|---|---|
| Public with strong login and two-factor authentication | Anyone can reach the login page, and only you can pass it | Low-risk applications and ones you need from any device, such as RSS or bookmarks |
| IP allow-list | The web server refuses everyone except listed addresses | Admin tools used from a fixed address |
| VPN only | The application is reachable only through your WireGuard tunnel | Anything sensitive: code editors, dashboards, database tools, password vaults you prefer private |
| Basic authentication in front | The web server asks for a username and password before the application loads at all | An extra layer on a tool with a weak login page |
An allow-list in Nginx is two lines inside the location block:
allow 203.0.113.10;
deny all;
Replace the address with your own public IP. Set up WireGuard once, and it becomes the standard way to reach every private tool, which is worth a dedicated guide of its own. The wider hardening steps are in How to Secure a VPS: Essential Setup Checklist.
Keep Them Updated, Backed Up, and Watched
Three jobs apply to every application you add. The first time you skip one is the day you wish you had not.
Updates. Each application is software with security fixes. A weekly routine works:
cd ~/linkding
docker compose pull
docker compose up -d
Tools exist that update containers automatically, but unattended updates of everything can break an application overnight, especially fast-moving ones. For anything important, update by hand, after a backup, after reading the release notes.
Backups. Each application’s data lives in a Docker volume. Back up the volumes, the Compose files, and the .env files, and export databases properly instead of copying live database files. Keep a copy off the server. Then restore one to prove it works. The method is in VPS Backup Strategy: How to Back Up a VPS and Actually Restore It
Monitoring. Add each public address to your outside uptime check. Watch memory and disk, because every new application adds to both.
Starter Stacks by Goal
| Goal | A sensible set | Suggested minimum |
|---|---|---|
| A first taste of self-hosting | Linkding, Miniflux, Uptime Kuma | 1 GB |
| Replace some subscriptions | Syncthing or Nextcloud, Vaultwarden, a feed reader | 2 GB |
| A developer’s toolbox | Forgejo, Woodpecker CI, n8n | 4 GB |
| Own your site analytics | Umami or Matomo next to your websites | 2 GB |
| A private photo library | Immich, with the rest kept light | 4 GB or more |
Start with one. Add the next when the first is stable, backed up, and updated.
Common Problems and What They Mean
| Symptom | Likely cause | Fix |
|---|---|---|
| Application cannot be reached from the internet | The port is bound to 127.0.0.1 and no reverse proxy exists yet | Add the Nginx block and the DNS record |
| 502 Bad Gateway | The container is not running or is on a different port | Run docker compose ps and docker compose logs, and check the port in proxy_pass |
| Browser warning about the certificate | The certificate was not issued, or DNS points elsewhere | Check the A record, then rerun Certbot |
| Login works but features are broken, or a vault refuses to load | The application requires HTTPS and you are on plain HTTP | Use the HTTPS address |
| Everything slows down after adding an application | Memory is exhausted | Check free -h, set a mem_limit, or remove or resize something |
| Disk keeps filling | Container logs or application data growing | Limit log size, and check docker system df |
Frequently Asked Questions
Is self-hosting safe?
It can be, provided you follow the basics: keep software updated, publish nothing you do not need to, require strong logins with two-factor authentication, and keep backups off the server. The risks come from skipping those steps, not from self-hosting itself.
How much does self-hosting cost?
The direct cost is the VPS and any domain. The larger cost is your time for setup and upkeep. Self-hosting tends to be cheaper when you replace several subscriptions with one server, and when you enjoy the work. It is not automatically cheaper once your time is counted.
Do I need a domain name?
For anything you want to reach over HTTPS with a proper certificate, yes. One domain can serve any number of applications through subdomains.
Should I host at home instead of on a VPS?
A home server has no monthly rent and gives you physical control, but you take on power, internet reliability, and exposing your home network. A VPS is simpler to keep online and does not expose your home connection. Read VPS vs Home Server: Cost, Control, and Practical Trade-offs for the full comparison.
Can I run all of these on one VPS?
Only as many as its memory, storage, and CPU allow. Heavy applications compete for the same resources as light ones. Install them one at a time and watch the numbers.
What if the application I want is not in a container?
Many projects document both a container install and a manual one. Prefer the container, because it keeps the application’s dependencies away from the rest of your server.
Self-Host What You Will Maintain
A VPS can be a home for a lot more than a website. Used carefully, it replaces subscriptions, protects your privacy, and teaches you more about how services work than any tutorial.
Used carelessly, it becomes a collection of outdated programs on the open internet. The difference is the habit of running things one at a time, behind HTTPS, with a back door closed, a backup made, and an update scheduled.
Self-host what you will maintain, and back up what you cannot replace.