Choosing the best VPS for self-hosting is a sizing question before it is a shopping question. A virtual private server is rented by the month, so every gigabyte of RAM you do not use is paid for again and again, and every gigabyte you are missing shows up as a crashed container at the worst moment.
Black Friday (November 27) and Cyber Monday (November 30) are when hosting companies push their loudest offers. This guide does not list them. Deal pages change by the hour, and we will not say a discount exists unless we have seen it on the provider's own page. What follows instead is a sizing table built from the official documentation of the apps you are likely to run, a checklist for reading any VPS offer, and the list prices one provider published on November 16, 2026, the day everything here was checked.
The Short Answer
How Much VPS Do You Need?
- ✅1 to 2 GB of RAM is a reasonable start for a few single-container apps such as a status monitor or a password manager
- ✅4 GB is the sensible default: room for Nextcloud, an analytics stack and a reverse proxy on one server
- ✅8 GB if you want Immich or a full mail server, because their own documentation asks for 6 GB before anything else is installed
- ✅Full (KVM-style) virtualization, a public IPv4 address, and backups that are stored outside the server
- ✅Judge an offer on its regular monthly price, not on the first-term discount
VPS or Home Server?
A VPS and a box at home solve different problems. A VPS has a public IP address, a data-centre connection and no dependence on your home internet line, which makes it the natural place for anything other people must reach around the clock: a status page, website analytics, a password vault you open from a phone on mobile data. A home server gives you cheap storage and real graphics hardware, which is what photo libraries and video streaming need.
If you are leaning towards hardware you own, read our guide to choosing the best mini PC for a home server.
How Much Server Each App Really Needs
This table quotes only what each project publishes. Where a project publishes no RAM figure at all, it says so rather than inventing one.
| App | What the official docs say | What it means for a VPS |
|---|---|---|
| Uptime Kuma (monitoring) | No RAM or CPU figure published. One container on port 3001; the data folder must be on a local disk, because NFS is not supported | Fits the smallest plans. Keep it on local storage, not a network share |
| Vaultwarden (passwords) | No RAM figure published; the project describes itself as an alternative to the "resource-heavy" official Bitwarden server. The web vault requires HTTPS | Fits the smallest plans. Budget for a domain name and a reverse proxy |
| Umami (analytics) | No RAM figure published. Needs PostgreSQL 12.14 or newer; the official Compose file runs the app plus a PostgreSQL container | Two containers. Small, but count the database |
| Plausible CE (analytics) | At least 2 GB of RAM recommended; the CPU must support SSE 4.2 or NEON, a ClickHouse requirement | 2 GB for this stack alone, so a 4 GB plan if anything else shares the server |
| Nextcloud (files, calendar) | Minimum 128 MB of RAM per process, 512 MB per process recommended; a 64-bit CPU and OS strongly recommended | Several PHP processes plus a database: plan for 4 GB |
| Coolify (deployment panel) | Minimum 2 CPU cores, 2 GB of RAM and 10 GB of free disk, on amd64 or arm64 | 4 GB once you count the apps it deploys |
| Immich (photos) | RAM: minimum 6 GB, recommended 8 GB. CPU: minimum 2 cores, recommended 4. Can run on 4 GB with machine learning disabled | 8 GB plan, and far more disk than a small VPS includes |
| mailcow (mail server) | Minimum 6 GiB of RAM plus 1 GiB of swap, 20 GiB of disk without emails; not supported on OpenVZ, Virtuozzo or LXC | 8 GB plan on full virtualization, and outgoing port 25 must be open |
| Jellyfin (media) | 8 GB of RAM recommended (4 GB may be enough on Linux without a desktop); running without a GPU is not recommended because CPU transcoding is very demanding | Usually the wrong fit: ordinary VPS plans have no GPU |
The documented requirements are per app. They add up, and the operating system, Docker and a reverse proxy need their share too.
The 1 to 2 GB Server: Monitoring and Passwords
Uptime Kuma is the classic first VPS app, because a monitor that lives outside your home network can tell you when your home network is down. Vaultwarden is the other one: a Bitwarden-compatible server written in Rust that you reach from every device. Neither project publishes a RAM requirement, and both run as a single container. Our walkthrough on self-hosting Vaultwarden covers the setup.
Umami belongs in the same group with one caveat: it needs a PostgreSQL database next to it. On a 1 GB plan, add swap and watch memory before you add a third app. That is our judgment, not a figure from the projects.
The 4 GB Server: Files and Analytics
Nextcloud documents its memory per PHP process: 128 MB at minimum, 512 MB recommended. A working instance runs several of those processes plus a database, and the official All-in-One installer adds more containers around it. Four gigabytes leaves headroom; our complete Nextcloud guide goes through the installation.
Plausible Analytics Community Edition recommends at least 2 GB of RAM so that ClickHouse and Plausible run "without fear of OOMs", and Coolify asks for 2 cores and 2 GB for the panel alone. If either shares a server with other apps, 4 GB is the realistic floor.
The 8 GB Server: Photos and Mail
Immich states a 6 GB minimum and an 8 GB recommendation, with 2 CPU cores at minimum and 4 recommended. Its documentation adds that thumbnails and transcoded video increase the size of a photo library by 10 to 20 percent on average, and that the PostgreSQL database should sit on local SSD storage, never on a network share. RAM is the easy part here. Disk is the expensive one: an 8 GB cloud plan typically includes far less space than a family photo library needs.
Mailcow asks for 6 GiB of RAM plus 1 GiB of swap as a minimum, notes that 8 GiB is recommended for roughly 5 to 10 users, and refuses container-based virtualization outright. It also needs outgoing connections on port 25, which leads to one of the checks below.
What to Keep at Home
Jellyfin's hardware guide says that running without a GPU is not recommended, because transcoding video on the CPU is very performance demanding, and that HEVC, VP9 and AV1 can be very demanding even on modern CPUs without hardware acceleration. Standard VPS plans have no graphics hardware. Unless every device you own plays your files directly, media belongs on a machine with an integrated GPU.
What to Check Before You Pay
RAM is the headline number. These are the lines further down the page that decide whether the server is actually usable.
The VPS Offer Checklist
- ✅Virtualization type. Docker-based stacks expect a real kernel. Mailcow, for example, supports KVM, ESX and Hyper-V but not OpenVZ, Virtuozzo or LXC
- ✅Shared or dedicated vCPU. On shared plans the hypervisor distributes CPU time among several virtual servers; dedicated plans reserve it for you and cost several times more. Self-hosted apps that idle most of the day are fine on shared cores
- ✅CPU architecture. Docker Engine supports both x86_64 and arm64, and so do Coolify, mailcow and Plausible (through NEON). Arm plans work for most images, but check each app before you commit
- ✅Disk size and type. Small plans include tens of gigabytes, not hundreds. Databases want local SSD or NVMe storage
- ✅Included traffic. It varies widely by region, even within one provider
- ✅IPv4 address. Confirm whether a public IPv4 address is part of the price or a separate line
- ✅Outgoing mail ports. Many providers block port 25 on new accounts. If you plan to run a mail server, read the policy first
- ✅Backups and snapshots. Find out what they cost, how many are kept, and whether they survive the deletion of the server
- ✅Billing terms. Hourly billing with a monthly cap lets you try a size and change your mind. A long prepaid term does not
A Worked Example: Hetzner Cloud List Prices
To make the checklist concrete, here is what one provider publishes. Hetzner is the provider we have used as a reference in earlier guides. The figures below are list prices in euros, excluding VAT, read from Hetzner's own cloud pages on November 16, 2026. No Black Friday promotion was shown on those pages when we looked. Prices and availability can change at any time, so check the provider's page before you order.
| Plan | vCPU | RAM | Disk | List price per month | Status on November 16, 2026 |
|---|---|---|---|---|---|
| CX23 (Cost-Optimized) | 2 shared, Intel/AMD | 4 GB | 40 GB NVMe | €5.99 | Shown as currently unavailable |
| CX33 (Cost-Optimized) | 4 shared, Intel/AMD | 8 GB | 80 GB NVMe | €8.99 | Shown as currently unavailable |
| CPX02 (Regular Performance) | 1 shared, AMD | 1 GB | 20 GB | €5.49 in Helsinki, €6.49 in Germany | Listed |
| CPX22 (Regular Performance) | 2 shared, AMD | 4 GB | 80 GB | €16.99 in Helsinki, €19.99 in Nuremberg | Listed |
| CPX32 (Regular Performance) | 4 shared, AMD | 8 GB | 160 GB | €30.49 in Helsinki, €35.99 in Nuremberg | Listed |
| CCX13 (General Purpose) | 2 dedicated, AMD | 8 GB | 80 GB | €36.99 in Helsinki, €43.49 in Nuremberg | Listed |
Read that table the way you should read any provider's page:
- The cheapest line is not always for sale. Every Cost-Optimized plan carried the notice "This product is currently unavailable" on the day we checked. A headline price only matters if you can order it.
- Location changes the price. The same plan costs less in Helsinki than in the German data centres.
- Location changes the traffic allowance even more. The European plans above include 20 TB of traffic. The US plans on the same page include between 1 and 4 TB, and the Singapore plans between 0.5 and 3 TB.
- Dedicated cores cost several times more. At 8 GB, the dedicated CCX13 has fewer cores than the shared CPX32 and a higher price. For a personal server that idles most of the day, shared is the reasonable choice.
- The extras are documented. Hetzner's plan pages label prices as including IPv4, while its documentation prices a primary IPv4 address at €0.50 per month and IPv6 at no charge, so confirm the total in the order form. Cloud firewalls are free. Servers are billed until they are deleted, whatever their state, and the bill never exceeds the monthly price cap.
- Mail is restricted. Hetzner blocks outgoing ports 25 and 465 by default on all cloud servers. You can request unblocking once you have been a customer for a month and paid your first invoice, and decisions are made case by case. Port 587 is not blocked.
- Backups and snapshots are different products. Backups are automatic daily copies with seven slots, tied to the server and deleted with it. Snapshots are manual, never deleted automatically, and survive the server. Neither includes attached volumes.
How to Read a Black Friday VPS Deal
We have not verified any specific Black Friday or Cyber Monday offer, so none is named here. These questions apply to whichever ones land in your inbox.
- What is the price after the first term? A VPS is a subscription. Compare the regular monthly price, because that is what you will pay for most of the server's life.
- How long is the commitment? A discount that requires two or three years paid upfront removes your ability to resize or leave.
- Is it full virtualization? If the page does not say KVM or an equivalent, ask before buying. Container-based plans cannot run every Docker stack.
- What is included? Go through the checklist above: IPv4, traffic, disk type, backups, mail ports.
Your First Hour on a New VPS
Whatever you buy, the first steps are the same. Docker's documentation lists Ubuntu 24.04 LTS and 26.04 LTS among the supported releases, on x86_64 and arm64. Docker also provides a convenience script, but states that it is only recommended for testing and development environments, so use the apt repository. These are the commands from the official install page:
# Add Docker's official GPG key:
sudo apt update
sudo apt install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
# Add the repository to Apt sources:
sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
The Firewall Trap
On a home network your router hides your mistakes. On a VPS, every published port is on the public internet. Docker's documentation is blunt about a common assumption: if you use ufw or firewalld, ports that you expose with Docker bypass your firewall rules, because packets are routed before those rules are applied.
Two habits deal with this. Use the provider's network firewall, which sits in front of the server (Hetzner's blocks all inbound traffic that no rule allows), and open only ports 22, 80 and 443. Then publish application ports on the loopback address so that only a reverse proxy on the same machine can reach them. Vaultwarden's own Compose example does exactly that:
services:
vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: unless-stopped
environment:
DOMAIN: "https://vw.domain.tld"
volumes:
- ./vw-data/:/data/
ports:
- 127.0.0.1:8000:80
Replace vw.domain.tld with your own domain. Vaultwarden's web vault only works over HTTPS, and the project recommends putting a reverse proxy in front of it; its wiki names Caddy as the easiest option because it obtains Let's Encrypt certificates by itself. Nginx Proxy Manager does the same job with a web interface.
A First App
Uptime Kuma is a good first deployment because it immediately does something useful. The project's README gives these commands:
mkdir uptime-kuma
cd uptime-kuma
curl -o compose.yaml https://raw.githubusercontent.com/louislam/uptime-kuma/master/compose.yaml
docker compose up -d
The downloaded file publishes port 3001 on all network interfaces. On a VPS, change the port line to "127.0.0.1:3001:3001" and reach the app through your reverse proxy, or make sure the provider firewall does not allow port 3001. Then run docker stats and look at what your server really uses. That number, not a deal page, tells you when to resize.
VPS or Home: Which One for You?
Choose a VPS When:
- 🔵The service must be reachable by other people at all times: status pages, analytics, shared files
- 🔵Your home connection has no public IP address or a slow upload
- 🔵Your apps are light on storage: passwords, monitoring, analytics, a personal cloud of documents
Choose a Home Server When:
- 🟢You stream video and need hardware transcoding
- 🟢Your photo or media library is measured in hundreds of gigabytes
- 🟢The services are for your household only, such as DNS ad blocking
- 🟢You prefer a one-time hardware purchase to a monthly bill
Frequently Asked Questions
Is 1 GB of RAM enough for self-hosting?
For one or two single-container apps, often yes. Uptime Kuma and Vaultwarden publish no minimum RAM requirement, so nothing in their documentation rules out a 1 GB plan. It is not enough for Plausible (2 GB recommended), Coolify (2 GB minimum), Immich (6 GB minimum) or mailcow (6 GiB plus swap). Measure with docker stats before adding more.
Can I run a mail server on a VPS?
Technically yes, if the plan has enough memory and the provider lets you send on port 25. Check the provider's policy before buying: Hetzner, for instance, blocks ports 25 and 465 by default and only considers unblocking after your first paid invoice. Port 587 stays open, which is enough to send through an external relay.
Do I need a domain name?
For anything with a login, effectively yes. Vaultwarden's web vault requires HTTPS, and a reverse proxy needs a hostname to obtain a certificate. Nextcloud All-in-One needs one domain for its setup and can register a free dynamic-DNS subdomain for you if you do not have one.
Are provider backups enough?
They are a good first layer, not the only one. Read what the product covers: Hetzner's automatic backups are deleted together with the server and do not include attached volumes, while snapshots are kept until you delete them. Keep at least one copy of irreplaceable data somewhere that does not depend on the same account.