← Directory

Homelabdash

A self-hosted dashboard for your homelab, configured in one YAML file.

  • Monitoring & Logging
  • Productivity
  • Tools & Utilities
A self-hosted dashboard for your homelab, configured in one YAML file. Edit /config/homelabdash.yaml and the page follows every save; the first start writes a starter file to begin from. Tiles update live, can graph their last hour, and raise alerts you can dismiss. 16 plugins come built in, among them Tautulli, the arrs, Seerr, qBittorrent, SABnzbd, Docker, Unraid, apcupsd, AdGuard Home and OpenWrt, and you can write your own. There is no login by default, so keep it on your LAN or put it behind a reverse proxy that signs you in.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-10-13
Latest release
v0.1.0
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (xiaodoudou/homelabdash)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • First start & configuration Configure homelabdash entirely in one YAML file. On first start it writes a starter file you can edit at /config/homelabdash.yaml, and the page updates live on every save. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where do I edit the dashboard configuration and does it hot reload?

You edit /config/homelabdash.yaml, and the page follows every save. On first start, homelabdash writes a starter file to begin from.

Do I put API keys and passwords in the main YAML file?

Keys and passwords should go in config/secrets.yaml and be referenced in the main config. They never reach the browser.

How can I check my configuration before it causes problems?

Run homelabdash validate to check the whole folder and print each problem as file:line path: message. If a change is invalid, the last good config keeps running.

Does homelabdash have built-in login?

There is no login by default. Keep it on your LAN or put it behind a reverse proxy that signs you in.

How are live tile updates delivered?

The server polls each service on its own interval and pushes changes over a WebSocket. A service is fetched once even if multiple tiles show it.

Answers sourced from github.com

Community

Collected today - public community threads