What to run on your first homelab: 5 starter services ranked by value

Your first homelab server is finally running. It might be a Raspberry Pi on a shelf, an old laptop that lost its battery years ago, or a used mini PC that arrived in a box barely bigger than a shoelace. You got an operating system installed, fought through SSH, maybe even made Docker work, and then came the question every new homelab owner faces: what do I actually run on this thing? Ask a homelab community for a top ten list and you will get a different answer from nearly every person, and most of those answers assume you already know what the machine is for.

The better approach is to let the value decide. For a starter lab, a service earns its place by dividing the benefit you notice by the effort it takes to reach it. Ad blocking for the whole network costs an hour of setup and pays back every single day. A media server costs an evening and pays back whenever you actually watch something. A monitoring tool costs twenty minutes and tells you when everything else stops working. The five services below are ranked on that ratio, from the one that rewards you first to the ones that quietly pay back as the lab matures.

At a Glance: The Five Starter Services

How This Ranking Works

The ranking runs on one question: how much does this service improve your life, divided by how much setup it demands? Effort matters more than expertise, and not just because you are learning. Your first server is a practice environment, so a service you can install, break, delete, and reinstall without touching the host OS is inherently more valuable than one that demands a permanent commitment. That is a big part of why every pick on this list runs as a container: the failure mode is clean, and the cost of trying something new is tiny.

Read the chart as a guide, not a grade. If you already run one of these, or if one solves a problem you actually have, move it up your personal list. The only ranking that matters is the one that ends with a working, maintained service.

1. AdGuard Home: Ad Blocking for Every Device

Any ranking of first services has to give the top spot to a DNS filter, because it is the only entry that rewards nearly every device you own at the same moment. Install AdGuard Home, tell your router to hand DNS duties to it, and phones, laptops, smart TVs, and consoles all stop loading ad and tracker domains a second earlier than they used to. Nothing gets installed on the clients, no browser extension is involved, and the effect is visible immediately: pages feel faster, the noise disappears, and the network starts to feel like it belongs to you again.

AdGuard Home earns its place over the better known Pi-hole for one practical reason: it ships with its own DHCP server, so a single low power machine can hand out addresses and filter DNS in the same breath. Give it a static address, point the router at it, and spend the first day reading the query log, because that log is the hidden lesson. It shows you which devices phone home, which apps call out at three in the morning, and how much of your traffic was working for someone else’s ad network.

The setup effort is a single evening, and the payoff never stops. Once the router points at it, AdGuard Home quietly becomes infrastructure the whole household relies on, and the query log keeps teaching you about your network for months.

2. Docker and Portainer: The Layer Everything Else Runs On

You could install every service on this list straight onto the operating system, and you would quickly hit the wall that ends most early homelabs: every app wants its own dependencies, its own setup ceremony, and its own rickety uninstall routine. Docker removes that wall by packaging each service with everything it needs, then installing or removing it completely, without touching anything else on the machine. If you have ever been afraid to clean up a badly installed program because it might take the whole system with it, you already understand the appeal.

The engine itself is something you enable once, and the friendlier face of daily use is Portainer, a web panel that lists your containers, shows their health at a glance, and lets you start, stop, and recreate them with a few clicks. It is not the only way to manage Docker, a docker compose file is a perfectly respectable text based alternative, but Portainer removes the black box feeling that stops beginners from experimenting, because you can always see what is running and what failed. Get this layer in place first and every remaining service on this list shrinks from a half hour of manual steps to a single paste.

Docker does not look exciting on its own, and that is the point. It is the least glamorous install on this list and the one that multiplies the value of every service you add after it, which is why it ranks ahead of services that look far more interesting at first sight.

3. Uptime Kuma: Knowing When Things Stop

Self hosted services are like houseplants: absolutely fine while you remember them, mysteriously dead by the time you notice. A DNS filter or a password vault can be quietly broken for days in a lab where nothing sends you an error, because a service that stopped answering does not knock on your door. Uptime Kuma exists to close that gap. You give it the addresses of the services you run, it checks them on a schedule you set, and it pings your phone, your email, or a webhook minutes after anything fails.

It ranks third because it costs almost nothing and changes how you run everything else. The alerts turn a homelab you hope is working into a homelab you know is working, and the built in status page doubles as a dashboard for your own phone when a service feels slow. The habit it teaches is the one professional operations teams live by: define what healthy looks like, monitor the deviation, and let the alarm do the remembering. Add every new service to the monitor list the day you deploy it, and the “is it broken?” question stops being a search through your memory.

4. Home Assistant: When the Lab Meets the House

Somewhere between the third and the tenth service, a homelab usually stops being about the network and starts being about the house. That is where Home Assistant earns its place. It pulls lights, thermostats, speakers, cameras, and sensors from hundreds of different ecosystems into one local dashboard, and it lets you build automations that act across them, so a motion sensor made by one vendor can switch on lights made by an entirely different one, which none of the vendor apps are designed to do.

Home Assistant has the highest ceiling on this list, which is exactly why it sits fourth. The setup itself is no harder than the rest, an install and a few integrations, but the depth of what you can build is basically endless, and it is easy to disappear into YAML automations and dashboard cards for weeks. That is a feature when you want something to grow with you and a trap when it is the only thing you have running. Get the foundation services stable first, then let Home Assistant glue the house together.

5. Vaultwarden: Passwords You Actually Own

The last pick is the least glamorous and one of the most quietly valuable. Vaultwarden runs a Bitwarden compatible password service on your own machine, which means you get a proper password manager with shared vaults, auto fill, and mobile apps, while the database of secrets lives in your homelab instead of someone else’s cloud. For a household the shared family vault is the killer feature: one master password per person, every login organized in folders, and no more hunting through group chats for the guest network password.

It ranks fifth because its benefit is steady rather than dramatic. It protects you every day and you will rarely notice it working, the way you notice ads disappearing. The discipline it installs matters more than the software: unique passwords for every account, real backup habits, and the uncomfortable realization that losing the server now means losing your vault. So do the backup on a schedule, export the vault to a file, and keep that file somewhere separate from the machine running it, because owning your passwords also means owning the responsibility for them.

The Next Tier

Beyond these five, the rest of the homelab canon makes sense once the foundation is solid. Jellyfin turns a folder of movies into a streaming service for the whole house. Immich or Nextcloud give you a private photo and file library instead of a monthly cloud subscription. Gitea hosts your own code when you are ready to learn git properly. Paperless-ngx tames the pile of scanned documents you keep meaning to organize. And if you built your machine around storage, the sharing and backup tools deserve your attention before any of the media apps. None of these are wrong picks, they just answer questions you have not asked yet. Run the five above first, and your next five will choose themselves based on what you actually do with the machine.

Start With One Service

A ranking is only useful if it ends in an action. Pick AdGuard Home for the fastest visible win, or Docker when you want the foundation in place before anything else, and resist the urge to install more than one or two things tonight. The most common reason homelabs get abandoned is not weak hardware, it is a server that accumulated five half finished projects and came to feel like a chore.

A lab with one working service, monitored, backed up, and simple enough to explain is worth more than a lab with ten services you are afraid to touch. Set up your first pick this weekend, watch it run for a few days, and add the next service only when the first one feels boring. Boring is the goal, because a service that quietly does its job is one you will keep running for years, and that is what a homelab is actually for.