homepage
One clean start page for every service you self-host, built from YAML files rather than plugins.
What it is
homepage is a self-hosted dashboard: a single page listing links to all your services, with live status, resource usage and widgets pulled from each one. It replaces the browser bookmarks folder you accumulate after running a dozen containers.
Its distinguishing choice is that everything is configured in YAML files inside a config directory, not through a web UI. You declare groups, services and widgets in text, and if a config file is missing it writes a commented example for you to fill in. The widget system has built-in integrations for well over a hundred services — Plex, qBittorrent, AdGuard, Proxmox, Pi-hole and many more — each showing real data such as active torrents or blocked queries.
It is aimed at the person running a home lab or a small stack of containers who wants a single tidy entry point. Because the configuration is files, it slots into a config repository alongside your compose files.
Why we recommend it
It works from files, not clicks
Configuration lives in YAML in a mounted directory, so it can be versioned, diffed and copied between machines. Rebuilding the dashboard is restoring a folder, not re-entering settings in a form.
Widgets show real state, not just links
A widget can display download progress, disk usage or active sessions straight from the service. The dashboard becomes a monitoring surface rather than a page of icons.
It reads the Docker socket for you
Once it can see the daemon, service status and ports update automatically as containers start and stop. You add the container, not the container details.
The result looks deliberate
Default layout, typography and dark mode are handled. It is one of the few self-hosted dashboards that does not look like an internal tool.
How it scores
These are our editorial ratings, not benchmark results. We score on how the project behaves in practice — how long it takes to get running, how good the documentation is, how responsive the maintainers are, and how well it holds up over time. The licence and star count above are read from GitHub and are a snapshot.
Pros and cons
Strengths
- A very large library of built-in service widgets
- Configuration as YAML files that can be version-controlled
- Automatic service discovery through the Docker socket
- Polished default design with sensible dark mode
- Published as a container image, so deployment is a compose entry
Trade-offs
- GPL 3.0 is a copyleft licence — if you distribute a modified version, the source of your changes must be released under the same terms
- Everything is configuration-driven, so there is no web UI to add a service and widgets require reading the integration docs
- A YAML syntax error typically shows a blank or broken page rather than a precise message pointing at the offending line
- Widgets need API keys or credentials per service, which adds setup work as the dashboard grows
How to get it
One-line install
Prefer the terminal? Copy a command and you are done.
docker run -d --name homepage -p 3000:3000 -v /path/to/config:/app/config -v /var/run/docker.sock:/var/run/docker.sock:ro ghcr.io/gethomepage/homepage:latest
Source and documentation
At a glance
| Category | DevOps |
|---|---|
| Licence | GPL 3.0 |
| Written in | JavaScript |
| GitHub stars | 32,499 |
| Repository | gethomepage/homepage |
Licence and star count were read from the GitHub API when this page was generated and are a snapshot. Check the repository for the current figure and the authoritative licence text.
Other DevOps tools
We are not affiliated with homepage or its maintainers. We list it because it is genuinely useful and genuinely free. If you plan to build a commercial product on top of it, read the licence on the repository first.