ConfigsApr 17, 2026·3 min read

Homer — Static Server Dashboard with YAML Configuration

Homer is a dead-simple static dashboard for your server services, configured entirely through a single YAML file with no database or backend required.

TL;DR
Homer renders a clean dashboard for all your self-hosted services from a single YAML config file, no backend needed.
§01

What it is

Homer is a lightweight, fully static server dashboard that organizes all your self-hosted services on a single page. It requires no database, no backend runtime, and no API connections. You edit a YAML configuration file, and Homer renders a clean, customizable dashboard in the browser.

Homer is built for homelab enthusiasts and sysadmins who run multiple self-hosted services and want a central start page. It is a static HTML/JS application served by any web server or Docker container.

§02

How it saves time or tokens

Without a dashboard, accessing self-hosted services means bookmarking dozens of URLs with different ports. Homer consolidates them into a single page with optional health checks that show service status at a glance. Adding a new service takes one YAML block, not a database migration or config reload. The entire dashboard loads as static files with no server-side rendering overhead.

§03

How to use

  1. Run Homer with Docker, mounting a volume for the assets directory.
  2. Edit assets/config.yml to define your services and groups.
  3. Open http://localhost:8080 to see your dashboard.
docker run -d --name homer \
  -p 8080:8080 \
  -v /path/to/assets:/www/assets \
  b4bz/homer:latest
§04

Example

A config.yml defining two service groups:

title: 'My Homelab'
subtitle: 'Service Dashboard'
columns: 3

services:
  - name: 'Media'
    items:
      - name: 'Jellyfin'
        url: 'http://192.168.1.10:8096'
        logo: 'assets/icons/jellyfin.png'
        subtitle: 'Media server'
      - name: 'Sonarr'
        url: 'http://192.168.1.10:8989'
        subtitle: 'TV show manager'

  - name: 'Infrastructure'
    items:
      - name: 'Portainer'
        url: 'http://192.168.1.10:9000'
        subtitle: 'Docker management'
      - name: 'Pi-hole'
        url: 'http://192.168.1.10:80/admin'
        subtitle: 'DNS ad blocker'
§05

Related on TokRepo

§06

Common pitfalls

  • YAML indentation errors break the entire dashboard with no helpful error message. Validate your config with a YAML linter before reloading.
  • Health checks hit each service URL on every page load. If a service is slow, it delays the whole dashboard render. Disable health checks for slow services.
  • Custom icons must be placed in the assets directory mounted into the container. Paths are relative to /www/assets/, not the host filesystem.

Frequently Asked Questions

Does Homer require a database?+

No. Homer is a fully static application. All configuration lives in a single YAML file. There is no database, no backend process, and no authentication system. It serves static HTML, CSS, and JavaScript files.

Can Homer check if my services are running?+

Yes. Homer supports optional health checks that ping each service URL and display a status indicator (green/red) on the dashboard. Health checks run on each page load from the browser, so they verify connectivity from your client, not the server.

How do I add a new service to Homer?+

Add a new item block to the services section in config.yml with a name, URL, and optional subtitle and logo. Save the file and reload the browser. No restart or rebuild is needed because Homer reads the config on each page load.

Can I use Homer with a reverse proxy?+

Yes. Homer works behind Nginx, Traefik, Caddy, or any reverse proxy. Serve it on a subdomain or path prefix. Since it is static files, there are no special proxy headers or WebSocket configurations required.

What alternatives exist to Homer?+

Dashy, Heimdall, and Organizr are popular alternatives. Dashy offers more features (widgets, status checks, authentication) but requires a Node.js runtime. Heimdall supports application-level integrations. Homer is the simplest option for teams that want pure YAML configuration and no backend.

Citations (3)

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets