Blog / Tutorials / How to Build a Private Homelab on a Single VPS

How to Build a Private Homelab on a Single VPS

A homelab is a personal set of self-hosted services — media, photos, files, automation, monitoring — run for learning, privacy, and control rather than convenience. This guide covers planning one: storage, networking, and monitoring, plus sizing a single VPS to run it, as an alternative…

6 min read

A homelab is a personal set of self-hosted services — media, photos, files, automation, monitoring — run for learning, privacy, and control rather than convenience. This guide covers planning one: storage, networking, and monitoring, plus sizing a single VPS to run it, as an alternative to buying local hardware.

What Is a Homelab?

A homelab is a small set of servers and services you run yourself, for yourself — the point isn’t to replicate a company’s production environment, it’s to learn how the pieces work and keep your own data under your own control instead of a subscription service’s. That could mean one VPS running three Docker containers, or a rack of repurposed hardware in a closet; the label applies at any scale.

Why Run a Homelab on a VPS Instead of Local Hardware?

A VPS-based homelab skips the parts of the hobby that are about hardware rather than software: no equipment to buy, power, or cool, and no router port-forwarding fight to make a service reachable from outside your home network — a VPS already has a public IP and real bandwidth. The trade-off is exactly what you’d expect: no physical hands-on tinkering, and you’re renting rather than owning the hardware. For anyone whose interest is in the software side — self-hosting, Docker, networking concepts — that trade is usually a good one.

Planning Your Homelab: Storage, Networking, and Monitoring

Storage

File storage and a photo or media library are usually the first services people run — they’re immediately useful and low-risk to experiment with. Contabo’s guides to self-hosted photo management apps cover the current options (Immich, PhotoPrism, and others) in depth if you’re picking one.

Networking

Give each service a static internal IP so you’re not hunting for it after every reboot, and put a reverse proxy in front of everything so each service gets a clean subdomain instead of a bookmarked IP:port combination. For reaching your homelab remotely without opening ports directly to the internet, Contabo’s guide to Pangolin covers zero-trust remote access in detail.

Monitoring

Know a service is down before a family member tells you. Uptime Kuma is the most commonly recommended starting point — lightweight, self-hosted, and enough for most homelab-scale monitoring without standing up a full observability stack.

Choosing Your Starting Stack

Pick one service per category to start rather than deploying everything on day one — a homelab that grows one working service at a time is far easier to keep running than one that arrived fully formed and half-understood.

Common Homelab Services by Category A starting map, not a complete list — pick one service per category rather than all of them on day one.
CategoryCommon toolNotes
MediaJellyfinSelf-hosted streaming for your own media library
PhotosImmichGoogle Photos-style library with face/object search
FilesNextcloudSync and share, Google Drive-style
Automationn8n / Home AssistantWorkflow automation / smart-home control
PasswordsVaultwardenSelf-hosted Bitwarden-compatible vault
Git hostingGiteaLightweight, runs on modest hardware
PaaS / deploysCoolifyGit-push deploys with managed databases
VirtualizationProxmox VERun multiple VMs/containers on one host
AI toolingComfyUI / custom MCP serversImage generation / custom LLM tool integrations

For deeper detail on any one of these, Contabo’s guide to the most popular open-source apps to self-host covers per-app VPS sizing, and the Proxmox and Coolify setup guides walk through those two specifically step by step.

Sizing a Single VPS for a Homelab

One or two lightweight services (Vaultwarden, Gitea) run comfortably on a small Core VPS. Add a photo library with machine-learning search (Immich) or several services running concurrently, and the extra RAM headroom of a Performance VPS starts to matter. A homelab that’s outgrown a shared-core VPS entirely — running its own hypervisor, or several resource-heavy services side by side — is the point where a Cloud VDS’s guaranteed cores earn their keep.

Securing Your Homelab

Never expose a service directly to the internet with no authentication in front of it — a homelab has no ops team watching for intrusions, which makes this more important here than on a managed production system, not less. Use a VPN or a zero-trust tunnel for remote access instead of opening firewall ports one at a time, keep the firewall default-deny, and actually apply updates — a homelab you forget about is a homelab running months-old, unpatched software.

Why Build Your Homelab on Contabo

Start on a Core VPS for a light, single-service homelab; move to Performance VPS once machine-learning-heavy apps like Immich or several concurrent services enter the picture; and step up to Cloud VDS once the homelab has genuinely outgrown a shared-core server. Every spoke of this pillar has its own deeper guide — the open-source apps listicle for what to run, Pangolin for remote access, and Proxmox and Coolify for the two most-requested setup walkthroughs.

FAQ: Homelab Basics

What is the purpose of a homelab?

To learn how self-hosted infrastructure actually works, and to keep your own data — photos, files, passwords — under your own control instead of a subscription service’s, rather than to replicate a company’s production environment at home.

Can I run a homelab entirely on a VPS instead of physical hardware?

Yes — a VPS-based homelab is a fully valid approach, and it skips buying, powering, and cooling equipment. The trade-off is no physical hardware to tinker with, which matters if that’s specifically what you’re after.

How do I secure remote access to a homelab?

Use a VPN or a zero-trust tunnel rather than opening firewall ports directly to the internet for each service. Contabo’s Pangolin guide covers setting up zero-trust remote access in detail.

What’s the best software for homelab automation?

n8n for general workflow automation across services and APIs, and Home Assistant specifically if smart-home devices are part of the setup. Both are common starting points and run comfortably alongside other homelab services.

Disclaimer: Product specifications, features, and prices mentioned in this article are subject to change and may vary by region, billing term, and active promotions. Please check each provider’s or brand’s official website for current figures, pricing, and local currency rates.