Back to services

Homer

Dead simple static homepage to expose your server services, with an easy yaml configuration and connectivity check.

View alternatives to Homer
Suggest edit
Open source
Self-hostable
Apache-2.0
Recent reviews

Alternatives

Tech stack

No tech stack added yet. Sign in to suggest some

Note: We couldn't fetch the official page (the GitHub repository) this time. The content below is based on my existing knowledge of the project, so please refer to the repository README for the exact details.

Overview

Homer is an open-source static homepage and dashboard, aimed mainly at self-hosters and homelab enthusiasts. It brings the various web services running on your server (such as media servers, download tools, monitoring dashboards, router admin pages and so on) together on a single page for quick access.

Main features

  • YAML configuration: The page title, logo, groups, service links, icons and more are all defined in the config.yml file. Edit it, refresh the page, and the changes take effect.
  • Purely static page: It generates static files, so it needs no database or backend service and can be deployed on any web server.
  • Groups and tags: Services can be grouped by category, and each entry can have a tag, a subtitle and an icon (Font Awesome icons or custom images are supported).
  • Search and keyboard shortcuts: A built-in search box lets you filter and open services quickly from the keyboard.
  • Themes and layout: Built-in light and dark themes, support for custom colors and CSS, and the option to switch between list and card layouts.
  • Smart cards: Some services (such as Pi-hole) can display status information or run online checks.
  • PWA support: It can be installed as a progressive web app on your phone or desktop.

Target users and use cases

Suitable for individuals who self-host multiple services, homelab users and small-team operations staff. It can serve as a browser start page, a navigation page for internal network services, or an entry page for a team's internal tools.

Key strengths

  • Very lightweight, using almost no resources
  • No backend required, so the attack surface is small and deployment is simple
  • The configuration file is plain text, making it easy to put in Git for version control

Installation and deployment

Docker (recommended):

docker run -d \
  -p 8080:8080 \
  -v /your/local/assets/:/www/assets \
  --restart=always \
  b4bz/homer:latest

Once it's running, just edit config.yml in the mounted assets directory.

Static files: Download the prebuilt archive from GitHub Releases, extract it into the directory of any web server such as Nginx, Apache or Caddy, and then edit assets/config.yml.

Technical requirements

  • A web server that can host static files, or a Docker environment
  • A modern browser

Things worth noting

Homer has no graphical configuration interface, so every change has to be made by editing the YAML file. If you want to edit directly in the browser with drag and drop, consider alternatives such as Heimdall, Homarr or Dashy.