Homepage

What is Homepage?

Homepage is a highly customizable dashboard for self-hosted services. It shows service status, integrates with Docker, media servers and monitoring tools, and is configured through YAML files.

Best for

Home lab users wanting a single launch page for all services

Why choose Homepage

Homepage turns a server full of services into something you can actually use. It is a start page that knows about your containers: it can show whether each service is up, display live stats, pull in recent downloads or upcoming calendar events, and give you one searchable place to launch everything. For self-hosters running dozens of small apps, it is the difference between remembering URLs and having a home screen.

Replaces

• Homer
• Dashy
• Organizr

Key features

• Docker and service integrations
• Live status and stats widgets
• YAML configuration
• Search and bookmarking

What to watch out for

The value depends entirely on how much of it you wire up, and the honest version is that configuration is a YAML project in itself — expect an evening to get from a basic list to a genuinely useful dashboard. Widget support is broad but not exhaustive, and the widgets that look best need API keys and service-specific settings. It also does not include authentication, so if it exposes internal service names and status, decide deliberately how it is reached from outside your network.

How to deploy

• Docker

Getting started

Deploy with Docker and mount three files: the settings, services and widgets configuration. Enable the Docker socket integration early if you want automatic service discovery, but be aware that mounting the socket gives the container significant power over the host — a deliberate trade, not a default to accept blindly. Start with your five most-used services and get their icons and links right before adding widgets. Group services by category from the start, because forty links in one flat list is harder to scan than the reverse proxy it replaced.

Typical setup

It sits on the same server as the services it links to, in Docker, with configuration files mounted from a small directory that is easy to back up. Mounting the Docker socket gives it live container status, which is the feature most people choose it for. Most installations are private — on a home network or behind a VPN — and it gradually becomes the entry point to a whole self-hosted stack, replacing a folder of bookmarks and a lot of memorised port numbers.

Who should look elsewhere

Not worth the effort if you run three services — a bookmarks folder does the same job. It is also inappropriate as a public-facing index: it lists internal service names, ports and status pages, so exposing it without authentication hands out a map of your infrastructure.

Project health

• GitHub stars: 32,927
• Last code push: 2026-10-01
• Open issues: 1
• Status: actively developed

Figures pulled from the GitHub API and refreshed periodically.