Proxmox at home vs renting a VPS

Proxmox at home or a VPS: the short answer

Proxmox VE is a free hypervisor you install on hardware you own, so you pay once for the machine and then pay for electricity every month. A VPS (virtual private server) is a virtual machine someone else runs on hardware in a data centre, so you pay rent and they own the power bill, the network and the failed drive. The choice is not really about money, because over three years the two land close together. It is about where your data has to sit, who answers the phone when the machine stops, and whether you need a public IP address.

Most people end up running both. Proxmox at home holds the bulk storage and the experiments. A small VPS holds the parts that strangers on the internet need to reach. The rest of this guide gives you the numbers, the honest strengths of each side, and the point where the hybrid pattern starts to make sense.

What three years actually costs

Hardware cost is easy to see and easy to underestimate, because the electricity bill arrives separately and never mentions the server. Here is the same three year window priced three ways. The figures are illustrative and assume an electricity price of 0.17 dollars per kWh, close to the United States residential average as of July 2026.

[
  {
    "label": "Mini PC, 15W idle",
    "upfront_usd": 450,
    "running_3yr_usd": 67,
    "total_3yr_usd": 517
  },
  {
    "label": "Used tower, 60W idle",
    "upfront_usd": 200,
    "running_3yr_usd": 268,
    "total_3yr_usd": 468
  },
  {
    "label": "Small VPS at 10 a month",
    "upfront_usd": 0,
    "running_3yr_usd": 360,
    "total_3yr_usd": 360
  }
]

The used tower looks like the cheap option on day one at 200 dollars. It is not, because an old desktop draws about four times the idle power of a modern low power machine, and that gap costs 268 dollars in electricity over the same three years. A second hand rack server with two sockets and spinning disks is worse again. When you buy hardware for a homelab, idle wattage matters more than the price sticker, because the machine spends almost all of its life idle.

The table leaves things out on purpose. The home box wants a UPS (uninterruptible power supply) if you care about unclean shutdowns, and it wants backup media somewhere else. The rented machine needs no capital at all, so a project you abandon after two months costs you twenty dollars instead of four hundred and fifty. For a fuller breakdown of what drives the rent side, read what a VPS actually costs per month.

The real difference is your time. A hypervisor at home makes you the data centre: you replace the drive, you chase the power cut, you explain to the household why the internet is slow tonight.

What Proxmox at home is genuinely better at

Data gravity. If you already hold four terabytes of photos and video, moving that into the cloud is slow and renting that much fast storage every month is expensive. Storage attached to a machine in your house is close to free once you own the disk. Media libraries, camera footage and backup targets belong at home for exactly this reason.

Raw resources per dollar. A machine with 64 GB of RAM costs a few hundred dollars once. The same memory rented monthly is a serious line item. If your workload is many idle virtual machines, or one greedy one, the home box wins on capacity.

Learning by breaking things. Proxmox gives you snapshots, cloning and a console on hardware nobody is billing you for. You can wreck a virtual machine at 2am and roll it back in twenty seconds. That freedom is a real reason to own the hardware, and it is why nested virtualisation comes up so often. If you want the same freedom on rented hardware, read running virtual machines inside a VPS first, because not every provider allows it.

Privacy and control. The disks are in your house. There is no provider policy, no shared tenancy and no account suspension. For some people that ends the discussion.

What a VPS is genuinely better at

A stable public IP address and a real uplink. This is the big one. Home connections usually hand out a dynamic address, and many sit behind CGNAT (carrier grade network address translation), which means inbound connections cannot reach you at all, whatever you forward on the router. Upload speed at home is also a fraction of download speed. A VPS gives you a static public address, symmetric bandwidth and control of reverse DNS, which is what a public service needs.

Uptime you did not have to build. Data centre power is backed by generators and the network has more than one path out. Your house has one power feed and one internet line. A ten minute power cut takes the home lab down. The same event does nothing to a rented machine.

Nobody in the room hears it. A server is warm and audible. A rented one is not in your bedroom.

It survives you moving house. Hardware has to be unplugged, boxed and re-cabled. A VPS does not care where you are.

Blast radius. Publishing a service from home opens a path into the network where your laptops and phones live. A rented machine is already outside that network. See what people actually run on a VPS for the shape of those workloads.

The hybrid pattern most people land on

The setup that survives contact with reality looks like this. Proxmox at home runs the storage heavy and private things: the media library, the document archive, the test virtual machines, the backup target. A small VPS runs the public face: the reverse proxy that terminates TLS (transport layer security), a status page, a mail relay, and anything that must answer at a fixed address.

The two halves are joined by a VPN (virtual private network), so the public side can reach the private side without exposing your home network. A WireGuard tunnel from the VPS to the home box is the standard answer, and it is about forty lines of config. See self-hosting a WireGuard VPN on a VPS for the whole procedure. Traffic arrives at the public address, travels down the tunnel, and is served by a machine with no port open to the internet at all.

This pattern fixes the backup problem in the same move. Home data goes offsite through the rented machine, which means a fire or a theft does not take both copies. Encrypted restic backups are the usual tool for that leg.

Installing Proxmox on hardware you already own

The normal route is the Proxmox VE installer ISO, which lays down Debian and the hypervisor together. If the machine already runs Debian 13, you can add Proxmox to it instead. These are the commands from the official Proxmox wiki, run as root.

wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg \
  -O /usr/share/keyrings/proxmox-archive-keyring.gpg

Then write the repository file at /etc/apt/sources.list.d/pve-install-repo.sources:

Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg

apt update && apt full-upgrade
apt install proxmox-default-kernel
systemctl reboot

The reboot is not optional, because the Proxmox kernel has to be the running kernel before the main package will install cleanly. When the machine comes back:

apt install proxmox-ve postfix open-iscsi chrony

postfix asks how it should deliver mail during the install. Answering "Local only" is fine for a lab, and it matters because Proxmox mails you about failed backups and failing disks. Then remove the stock Debian kernel, so the machine cannot boot back into a kernel without the Proxmox stack:

apt remove linux-image-amd64 'linux-image-6.12*'
update-grub

The web interface answers on port 8006 over HTTPS. It uses a self signed certificate, so the browser warns you the first time.

Do not open port 8006 to the internet. That page is a root login to your hypervisor, so one weak password loses every virtual machine at once. Reach it over the VPN, or over an SSH tunnel.

Clusters, quorum, and the uptime you can honestly promise

People buy a second machine expecting high availability and are surprised by what it takes. Proxmox clusters with pvecm create CLUSTERNAME on the first node and pvecm add IP-ADDRESS-CLUSTER on each node that joins. pvecm status then shows the vote count, and pvecm nodes lists the members.

The catch is quorum. The Proxmox documentation is explicit that you need at least three nodes for reliable quorum before high availability means anything. Two nodes cannot decide which of them is the survivor when the link between them breaks, so a split network leaves both of them refusing to act. A two node cluster can borrow a third vote from a QDevice, which is a small always on machine running the corosync QDevice daemon, and a cheap VPS is a common home for that vote.

So the honest position is this. One Proxmox box gives you virtualisation and snapshots, not availability. Three boxes with shared or replicated storage give you availability, at three times the power draw and much more of your attention. A single VPS gives you neither clustering nor snapshots by default, but the hardware underneath it is already redundant and someone else is paid to watch it.

How to pick

Buy hardware and run Proxmox if you have bulk data, if you want to learn virtualisation, or if privacy is the point. Rent a VPS if the thing you are building has to be reachable from the internet at a fixed address, or if it should survive a power cut you did not cause. If you cannot decide, rent the small machine first. Ten dollars buys you a month to find out whether the project survives, and the hardware will still be for sale later.

FAQ

Is Proxmox at home cheaper than a VPS?

Over three years the totals are close, and the answer turns on power draw. A low power mini PC costs about 517 dollars over three years including electricity, while a small VPS at ten dollars a month costs 360. A second hand desktop looks cheaper on day one and then loses the difference to its idle wattage. Home hardware wins clearly when you need lots of storage or lots of RAM, because those are the resources that are expensive to rent and cheap to buy.

Can I host a public website from Proxmox at home?

Often not directly. Most home connections hand out a dynamic IP address, and many sit behind carrier grade NAT, so no inbound connection can reach you no matter what you forward on the router. Upload bandwidth is also much lower than download bandwidth. The usual fix is a small VPS with a static public address that forwards traffic through a VPN tunnel to the home machine, which keeps your home network closed.

Do I need three machines to run Proxmox?

No. One machine runs virtual machines, containers and snapshots perfectly well. Three is the minimum only for high availability, because the Proxmox documentation requires at least three nodes for reliable quorum. Two nodes plus a QDevice on a small always on machine is the common compromise when you want failover without buying a third server.

Will VPS tutorials work on a Proxmox guest?

Yes, because a Proxmox guest running Ubuntu or Debian is the same Linux a provider hands you. The differences are the ones described above: the network in front of the machine, whether its address is public, and who replaces the disk. Commands, Docker, firewall rules and service files behave the same on both sides.

What should I run at home and what should I rent?

Put the storage heavy and private workloads at home: media, photos, document archives, backup targets and test virtual machines. Rent the parts strangers need to reach: the reverse proxy, a status page, a mail relay, and anything that must answer at a fixed address. Join the two with a VPN so the public half can reach the private half without opening your home network.