The math first: one cheap VPS against a commercial VPN

A mainstream commercial VPN runs $5 to $10 a month, so $60 to $120 a year, and the price climbs if you want more than a handful of simultaneous devices. A VPS big enough to run WireGuard costs $10.49 a year at the bottom of the market. That is not a rounding error. It is a 6x to 12x difference for something you can set up in twenty minutes and then forget about.

The catch, and there is one: a self-hosted VPN gives you exactly one exit IP in exactly one location. Whether that trade is worth it depends on what you actually use a VPN for. This guide walks through the numbers that hold in November 2026, the plans worth buying, and the ways these setups break.


What WireGuard needs from a server

Almost nothing, which is the whole point. WireGuard is roughly 4,000 lines of code, against 70,000-plus for OpenVPN, and it has shipped inside the Linux kernel since version 5.6. It runs over UDP only, encrypts with ChaCha20-Poly1305, and handshakes complete in under a second on hardware from any era.

  • CPU: one core at 3.0 GHz pushes well over 1 Gbps of encrypted traffic. Any KVM slice qualifies.
  • RAM: 512 MB is comfortable for a personal endpoint with a handful of peers. The kernel module itself costs a few megabytes.
  • Disk: 10 GB is plenty. WireGuard stores keys and configs, nothing else.
  • Network: the real constraint. Look at monthly transfer and port speed before anything else on the spec sheet.
A WireGuard server is the rare workload where the cheapest plan is genuinely enough. The bottleneck is the network, not the box.

Verified plans for a WireGuard endpoint, November 2026

Prices below were checked in mid-November 2026. The BuyVM numbers come from the provider's own site, read directly on November 16. The RackNerd figures come from a third-party price tracker that re-checks stock daily, because racknerd.com sits behind an anti-bot wall. Treat anything older than a few weeks as unverified.

  • BuyVM SLICE 512 — 1 core, 512 MB RAM, 10 GB SSD, unmetered bandwidth, 1 IPv4, $24.00 per year, Las Vegas, New York or Luxembourg. DDoS protection included. The SLICE 1024 at $3.50 a month doubles everything if you want headroom.
  • RackNerd 768 MB KVM special — 1 core, 768 MB RAM, 30 GB SSD, 3 TB monthly transfer, $10.49 per year, US locations. The 1 GB special at $21.99 a year is the one most people should buy. Both renew at the same price, which is unusual in the annual-deal market and worth saying out loud. Checked November 15.
  • Hetzner entry cloud server — about 4 euros a month for an ARM or x86 instance in Germany or Finland. Community-tested pricing, since Hetzner's cloud page renders its prices behind JavaScript. Clean IP space and EU jurisdiction make it the default European pick.
  • Hostinger KVM 1, Black Friday — 1 vCPU, 4 GB RAM, 50 GB NVMe at $6.49 a month on a 24-month term ($155.76 up front), renewing at $11.99. Live until December 14, 2026. Frankly overkill for WireGuard alone, but if you want the VPN and a dozen Docker containers on one box, it fits.

For reference, this site carries long-form reviews of BuyVM and RackNerd, covering the same plans under sustained load. Worth reading before committing years of prepaid service to either.


Jurisdiction and IP reputation matter more than price

Two things decide whether a self-hosted VPN is pleasant to live with, and neither appears on the spec sheet.

First, where the server legally sits. Luxembourg, where BuyVM operates a location, is known among self-hosters for relatively relaxed takedown handling. Germany and Finland give you GDPR-style privacy law. A US location gives you neither, though for a personal exit node that matters less than people assume.

Second, IP reputation. The dirtiest IP blocks on the internet belong to ultra-budget hosts whose ranges are hammered by spammers day and night. Route your browsing through one and you inherit the reputation: CAPTCHAs on every login form, streaming platforms that refuse to play, retailers that quietly decline the card. In our testing RackNerd's ranges sit mid-pack; Hetzner and BuyVM run clean. Before settling on a provider, connect once and run the exit IP through a blocklist checker. A minute of work saves a year of annoyance.


The setup, compressed into six steps

On a fresh Ubuntu 22.04 or 24.04 install the whole thing is six steps.

  1. Install: apt update, then install the wireguard package from the default repositories.
  2. Keys: wg genkey and wg pubkey for the server and each client. Curve25519 pairs, no certificates, no password database to leak.
  3. Server config: /etc/wireguard/wg0.conf with Address = 10.0.0.1/24, ListenPort = 51820, and firewall MASQUERADE rules in PostUp so client traffic actually reaches the internet.
  4. Forward packets: enable IPv4 forwarding in sysctl. Skipping this is the single most common cause of a broken tunnel.
  5. Clients: one [Peer] block per device. AllowedIPs = 0.0.0.0/0 on the client side for a full tunnel, or a narrower range if you only want selected traffic routed.
  6. Import: qrencode turns a client config into a QR code for the iOS or Android app. PersistentKeepalive = 25 keeps NAT mappings alive on mobile networks.

One-click install scripts and web dashboards such as wg-easy exist if you would rather not touch a config file. They work fine. Still, manual setup once teaches you enough to debug anything that breaks later, and something always breaks eventually.


Five failure modes that hit cheap nodes hardest

  • UDP blocked on the client network. Some carriers, hotels and corporate networks drop UDP entirely. Move the listen port to 443/udp, or wrap the tunnel in a TCP WebSocket with wstunnel.
  • No TUN device. OpenVZ and NAT-based "VPS" products often lack a real TUN interface. Buy KVM with a dedicated public IPv4; this rules out the very cheapest offers, which share one IPv4 between dozens of tenants by design.
  • IPv6-only servers. An IPv6-only VPS is useless as an exit for IPv4-only clients, and most mobile carriers still qualify. We cover this trade-off in detail in our IPv6-only VPS guide.
  • Handshake succeeds, nothing loads. Almost always a missing forwarding setting or NAT rule. wg show reports an active peer anyway, which makes it genuinely confusing the first time.
  • Transfer caps. 3 TB a month sounds endless until every video in the house routes through the tunnel. Unmetered providers like BuyVM win here; read the fair-use wording before assuming unlimited means unlimited.

When you should just pay for a commercial VPN

Self-hosting loses in three situations. You need exit IPs in many countries, because each location means another VPS to feed and patch. You need the provider not to know who you are, which a card-paid VPS under your own name cannot deliver. And you want streaming geo-unblocking at scale, where a single datacenter IP fights a losing battle against platform detection. For everything else, a $10-to-$25-a-year slice and twenty minutes of setup covers a household's phones and laptops indefinitely, and the exit IP belongs to you alone.