homer
Homer is a lightweight, static homepage dashboard for self-hosted servers that aggregates links to your services via a simple YAML configuration file. It runs as a Vue-based single-page application and requires no backend database or complex maintenance.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | bastienwirtz/homer |
| Owner | bastienwirtz |
| Primary language | Vue |
| License | Apache-2.0 — OSI-approved |
| Stars | 11.5k |
| Forks | 922 |
| Open issues | 169 |
| Latest release | v26.4.2 (2026-04-18) |
| Last updated | 2026-07-05 |
| Source | https://github.com/bastienwirtz/homer |
What homer is
Homer is a Vue.js-based static site generator that compiles to HTML/JavaScript and serves configuration-driven UI dashboards. It supports PWA installation, fuzzy search, multi-page layouts, theme customization, and optional smart card integrations—all from a single YAML configuration file with no runtime dependencies.
Get the homer source
Clone the repository and explore it locally.
git clone https://github.com/bastienwirtz/homer.gitcd homer# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Configuration is YAML-based; changes require file edits and server restart or hot-reload—no runtime UI for config management.
- Runs as static HTML/JS; must be served over HTTP (file:// protocol not supported); Docker or standard web server required.
- Default Docker container runs as uid:gid 1000; ensure config directory permissions match or override with --user flag.
- INIT_ASSETS environment variable can auto-populate example configs and favicons on first run; control via writable assets directory.
- Build from source requires pnpm; pre-built releases available (homer.zip) for faster deployment without Node.js toolchain.
When to avoid it — and what to weigh
- Dynamic User Authentication Required — Homer is a static site; it does not natively handle per-user authentication, role-based access control, or session management.
- High-Volume Data or Real-Time Updates — Dashboard is built for static/reference content; it is not designed to ingest or display real-time metrics or frequently changing data.
- Custom Backend Logic Needed — Homer has no backend runtime; any dynamic behavior or business logic must be built separately or delegated to linked external services.
- Multi-Tenant SaaS Model — Single-instance, single-configuration design; not suitable for serving distinct dashboards to multiple independent tenants.
License & commercial use
Licensed under Apache License 2.0, a permissive OSI-approved license allowing commercial use, modification, and redistribution with liability and trademark protections.
Apache 2.0 explicitly permits commercial use. No restrictive clauses found in license text. However, review your own legal requirements and the license notice requirements (retain headers and provide a copy of the license).
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
Static site with no authentication layer; all content exposed to network access. Deploy behind reverse proxy with TLS, authentication middleware, or firewall rules if sensitive services are linked. No known CVE disclosures in provided data; check GitHub security advisories. YAML config file may contain plaintext URLs or service references—secure config directory permissions and consider environment variable injection for sensitive values.
Alternatives to consider
Dashy
Feature-rich self-hosted dashboard with built-in authentication, widgets, and theme engine; more complex setup and maintenance than Homer.
Organizr
Multi-user dashboard aggregator with SSO/LDAP support and advanced theming; steeper learning curve and requires PHP/database backend.
Portainer
Docker/container management UI with built-in dashboarding; heavier resource footprint and broader scope beyond simple link aggregation.
Build on homer with DEV.co software developers
Homer is production-ready for teams managing self-hosted infrastructure. Get started with Docker, pre-built releases, or build from source.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
homer FAQ
Can I use Homer without Docker?
Does Homer support user authentication?
How do I customize the appearance?
Is Homer suitable for production self-hosted services?
Custom software development services
From first prototype to production, DEV.co delivers software development services around tools like homer. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source devops and beyond.
Deploy a Clean Server Dashboard in Minutes
Homer is production-ready for teams managing self-hosted infrastructure. Get started with Docker, pre-built releases, or build from source.