Glance vs Homer
| Tagline | Highly customizable dashboard that puts all your feeds in one place | Dead simple static homepage to expose your server services via YAML config |
| Category | BI & Dashboards | BI & Dashboards |
| Replaces | Tableau, Looker, Power BI | Tableau, Looker, Power BI |
| GitHub stars | 35k | 11k |
| Language | Docker | Docker |
| License | AGPL-3.0 | Apache-2.0 |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 19 days ago | 2 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Glance
- No built-in database or persistent data store; purely a read/aggregation layer
- No multi-user support or access control
- No data source connectors for business databases or warehouses (unlike Tableau/Power BI)
- No interactive charts, pivot tables, or drill-down analytics
Homer
- Extremely minimal: no service widgets, no data pulled from APIs beyond ping checks
- No built-in authentication or user management
- No analytics, charts, or data visualization features
- Configuration is file-only with no web UI editor
Bottom line
Both are a similar lift to self-host; choose Glance for the larger community and ecosystem. Homer has seen more recent development. Open each guide below for deploy steps and the full feature gap.