I stopped memorizing IP addresses and ports once I set this up for my homelab

One of the pain points in managing a homelab is access to servers. For small infrastructure, it’s easier because you can memorize a few ports and IP addresses, but this is simply not sustainable for scaling. I’ve used and liked Homepage, but I prefer easy access without editing config files. This led me to explore Homarr and, since then, I haven’t had the need to memorize a port or IP.

OS: Linux, Windows, Mac
Price model: Free

Homarr is a beautiful, modern dashboard that gives seamless access to all your apps, containers, and services.

My homelab ran on memory instead of structure

And it only got worse as I added more services

Creating my Homelab board — Afam Onyimadu / MUO

Jellyfin uses port 8096; Sonarr uses 8989; Radarr uses 7878; Prowlarr uses 9696. These are some of the services and ports I had memorized. However, there is an even longer list that I simply can’t memorize. And I was not only trying to keep track of ports, I was also memorizing IP addresses.

The main problem I had using bookmarks was that they were scattered across devices and, because several had become outdated, I often landed on the wrong one. This became an unnecessary source of stress.

Some bookmarks were outdated, for others I only remembered the port, and for some, I had to check my desktop. It was this chaos that revealed my real problem wasn’t several services, but a proper system for reaching them.

What Homarr replaced the moment I set it up

One URL now does what a dozen bookmarks never could

I tried Homarr skeptically; after setting it up from scratch, I liked it. It was a straightforward process where I had to create a new board, drag a tile for Jellyfin or other services I needed. This instantly replaced typing IP addresses and ports. The process of adding services is quite intuitive and works well across devices. Once I set it up, a single URL works on any device, whether it’s a laptop, phone, or tablet.

This is how it felt before and after Homarr:

Task	Before Homarr	After Homarr
Access Jellyfin	Memorize :8096	Click tile on dashboard
Find Sonarr	Check bookmark	Click tile, mobile-friendly
Open Radarr remotely	Type IP + port	Dashboard tile on any device
Share access with someone	Send IP + port	Send one URL with optional auth
Add new service	Create bookmark	Drag-and-drop tile in minutes

The most important thing Homarr did was to replace the way I access my homelab. There was no need to rely on bookmarks anymore. It totally erased that mental stress.

Setting up Homarr

Docker, one compose file, and I was basically done

Since I had Docker running on my homelab, it made installation really simple. I recommend installing Docker first if you don’t already have it. During the entire process, the only YAML file I ever touched was the docker-compose.yml (compose) file. Homarr’s compose file should have the following value:

homarr:

container_name: homarr

image: ghcr.io/homarr-labs/homarr:latest

restart: unless-stopped

volumes:

- /var/run/docker.sock:/var/run/docker.sock

- ./homarr/appdata:/appdata environment: - SECRET_ENCRYPTION_KEY=YOUR_ENCRYPTION_KEY

ports: - '7575:7575'

You should set a unique SECRET_ENCRYPTION_KEY for security, which you can generate with: openssl rand -hex 32. This is optional at first, but recommended once you start using auth and integrations.

Once I was done with it, the rest of the setup was GUI-driven. I did some grouping for services on a drag-and-drop board. You could modify this part according to your preferences. For me, media apps stayed together, I had a cluster for download clients, and I created a section for AdGuard and other network tools. You can enable container status widgets by mounting the Docker socket (optional). I liked this option because it was another layer of visibility.

Setting up Homarr took less time than untangling my bookmark folders. Within twenty minutes, I was done with my setup.

Homarr goes further than a bookmarks page

Integrations and live data made me stop looking for alternatives

I always assumed using dashboards was just a pretty way of clicking bookmarks. With Homarr, you get live data for your services. For Jellyfin or Plex, Homarr shows you the server status along with available media. You see your active download queues along with library updates for Sonarr or Radarr. If you have connected to the qBittorrent or SABnzbd service, it gives you activity for torrents and Usenet at a glance.

These service indicators built into the dashboard allow me to see when services are up or down without actually opening the individual services. Including system info, time, and weather widgets effectively makes the dashboard a complete homelab front page.

If you’re tired of memorizing ports, it’s hard to beat

There are several options aside from Homarr. Homepage and Heimdall are two of the better ones. Homepage is great if you love YAML configs and deep customization, and Heimdall is a nice lightweight option. Homarr is right for a user who wants to sit in the middle of these two; good visuals, easy setup, and a great dashboard view of live data.

This is how they compare stacked against each other:

Feature	Homarr	Homepage	Heimdall
Setup method	UI-first + Docker	YAML config files	UI-based
Ease of use	Very easy	Moderate (config-heavy)	Easy
Live integrations	Yes, UI-configured	Yes, YAML-configured	Minimal
Customization	Visual + flexible	Very high	Basic
Maintenance	Low	Medium–high	Low
Best for	Balance of simplicity + power	Power users who like config files	Lightweight dashboards

I still SSH into my machines for administration and management—Homarr is for access and monitoring, not full server management. Unlike tools like DockPeek, which focus specifically on Docker container management, Homarr is built around accessing and monitoring all your services regardless of how they’re deployed.