glance
Glance is a self-hosted dashboard written in Go that aggregates multiple feed sources (RSS, Reddit, YouTube, weather, markets, etc.) into a single customizable interface. It emphasizes low resource usage, fast load times, and flexible configuration via YAML, making it suitable for homelab deployments.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | glanceapp/glance |
| Owner | glanceapp |
| Primary language | Go |
| License | AGPL-3.0 — OSI-approved |
| Stars | 35.7k |
| Forks | 1.4k |
| Open issues | 329 |
| Latest release | v0.8.5 (2026-05-30) |
| Last updated | 2026-05-30 |
| Source | https://github.com/glanceapp/glance |
What glance is
A lightweight Go application that serves as a feed aggregator and dashboard with support for multiple widget types, caching mechanisms, and responsive design. Deployment options include Docker, binary installation, or package managers; configuration is declarative YAML-based with support for custom CSS.
Get the glance source
Clone the repository and explore it locally.
git clone https://github.com/glanceapp/glance.gitcd glance# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- AGPL-3.0 license obligates source disclosure if deployed as a network service; ensure legal/compliance team reviews before production deployment.
- Configuration is YAML-based and static; dynamic configuration reloading behavior is not documented.
- External feed sources (Reddit, Hacker News, YouTube, etc.) are subject to rate limits and API changes; monitor for breakage.
- No built-in authentication or access control mentioned; network access control must be managed via reverse proxy or network policy.
- Caching behavior is configurable per widget but no global cache invalidation mechanism is described.
When to avoid it — and what to weigh
- Proprietary/closed-source requirement — Glance is licensed under AGPL-3.0; any modifications or commercial distribution require source disclosure or licensing review.
- Need for persistent user accounts with authentication at scale — No multi-tenant user management details provided; suitability for large-scale multi-user deployments is unclear.
- Heavy reliance on third-party API integrations — While many widgets are supported, integration stability and rate-limit handling depend on external services; no SLA documented.
- Enterprise compliance/audit requirements — Security posture, audit logging, and compliance certifications are not documented; requires thorough internal security review.
License & commercial use
AGPL-3.0 (GNU Affero General Public License v3.0). This is a strong copyleft license requiring that any modifications or derivative works distributed over a network must have source code made available to users. Commercial use is not forbidden, but modifications must be open-sourced or licensing arrangements negotiated.
AGPL-3.0 permits commercial use, but with important caveats: (1) if you modify the code and deploy it as a service, users must be able to obtain the modified source; (2) internal-only use without network distribution may be exempt from source disclosure requirements; (3) seek legal counsel before commercial deployment. This is not a permissive license like MIT or Apache-2.0.
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 |
No formal security documentation provided. Key considerations requiring review: (1) network access control—no built-in authentication documented; deployment assumes trusted network or reverse proxy protection; (2) external API dependency—credentials for Reddit, YouTube, market data, etc. must be securely stored; (3) YAML configuration injection risks if user input reaches config files; (4) cached data handling and potential information disclosure; (5) no mention of HTTPS enforcement, CSRF protection, or CSP headers. Internal security audit strongly recommended before production deployment.
Alternatives to consider
Heimdall
Another self-hosted dashboard written in PHP; more UI-focused with drag-and-drop interface, but heavier resource footprint.
Homer
Static, file-based self-hosted startpage; simpler configuration but fewer aggregation features and real-time updates.
Organizr
Unified homelab dashboard with tab management and SSO support; more complex but offers granular access control for multi-user scenarios.
Build on glance with DEV.co software developers
Deploy Glance in minutes using Docker Compose or a precompiled binary. Review AGPL-3.0 licensing if commercial use is planned.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
glance FAQ
Can I use Glance commercially?
Is authentication/multi-user support built in?
What happens if an external API (Reddit, YouTube) breaks or rate-limits?
How much compute resources does Glance need?
Software development & web development with DEV.co
Need help beyond evaluating glance? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source devops integrations — and maintain them long-term.
Ready to unify your feeds?
Deploy Glance in minutes using Docker Compose or a precompiled binary. Review AGPL-3.0 licensing if commercial use is planned.