Answer in brief: Glance is a self-hosted dashboard written in Go that pulls RSS feeds, subreddit posts, Hacker News, weather, YouTube and Twitch channels, market prices, Docker container status, and server stats into YAML-configured pages. Based on a source and documentation review on 2026-08-11 at v0.8.5, it is a strong fit for homelab operators and technical small teams who want a lightweight startpage and accept self-maintenance, but only if you can live without auto-refresh, SSO, and guaranteed third-party widget availability. Treat it as a display tool rather than an alerting or monitoring platform, and check deployment details such as DNS-based timeouts, health checks, and the AGPL-3.0 license before production.

This is a repository, documentation, release-note, and issue review. No local installation or runtime test was part of the evidence, so performance, widget behavior, and security posture are unverified here.

key facts

what Glance is and what it is not

The maintainers describe Glance as a lightweight, highly customizable dashboard that displays feeds in a streamlined interface. The repository lists widgets for RSS feeds, subreddit posts, Hacker News, weather forecasts, YouTube channel uploads, Twitch channels, market prices, Docker container status, and server stats, plus custom widgets. Configuration is YAML-based, with multiple pages and tabs, custom CSS, themes, and mobile layouts.

The README also makes performance claims that are not verified by this review: low memory usage, few dependencies, minimal vanilla JavaScript, a single binary under 20 MB, and uncached pages that usually load within about one second depending on internet speed and widget count. Treat these as maintainer claims until you measure them on your own hardware.

What Glance is not: an always-on monitoring or alerting system. The project FAQ states that no background requests are made and information is only fetched when a page is loaded, then cached per widget. A page refresh is required to update content. If your goal is alerting when a service goes down, you want a dedicated uptime monitor, not a dashboard.

who should consider Glance

Glance is most clearly a fit for homelab and self-hosting users: people running a small server, NAS, or mini PC who want a personal startpage that combines RSS, weather, markets, and container status without a heavy stack. The maintainers recommend a Docker compose template for installation, and precompiled binaries are available for Linux, Windows, and macOS across x86 and ARM architectures, with a systemd service as a documented pattern for a bare binary.

Small businesses and technical founders can also use it for an internal team dashboard, under conditions: you are comfortable editing YAML, you can run Docker or a systemd service, and you accept responsibility for updates, configuration backups, and reverse-proxy authentication. If the dashboard will hold business-critical status information, Glance alone is not enough, because it does not refresh in the background and does not send alerts.

deployment concerns to check first

Configuration comes first. Glance expects a glance.yml file at startup; an open roadmap issue asks the maintainers to generate a default configuration on first run, so plan to create and version your own config. A documented error occurs when a pages key appears inside an included page file, so keep the structure clean when you split configuration across files.

DNS and timeouts are the most likely early failures. The README common issues section says requests timing out is usually caused by Pi-Hole, AdGuard Home, or other ad-blocking DNS services with low rate limits, and recommends raising those limits. A separate open issue reports weather and monitor widgets timing out inside Docker, so if you deploy on a Raspberry Pi or behind container networking, test outbound HTTPS to the widget endpoints before relying on the dashboard.

Health checks changed in v0.8.4: the Docker image health check was removed. If your orchestration or reverse proxy depends on health checks, you will need to provide your own, which matters for anyone automating restarts.

Authentication is your responsibility. An open feature request asks for OIDC support, and none of the release notes in this evidence mention it; if SSO is a requirement, verify before committing. If you expose Glance beyond your local network, put it behind a reverse proxy with authentication. This review did not include a security audit, and no security conclusions should be drawn from it.

maintenance signals

Glance was created in April 2024 and, as of the review date, had 36,293 stars and 1,403 forks, with 345 open issues. The repository was pushed on 2026-05-30, the same day v0.8.5 was published. The evidence covers releases v0.8.1 through v0.8.5 between May 2025 and May 2026, so expect a steady but not frequent release cadence; the roughly twelve-month gap between v0.8.4 and v0.8.5 is the notable pattern.

The biggest maintenance risk is third-party widgets. Reddit removed unauthenticated access to its JSON endpoints, and issue #1016 tracks the resulting 403 errors. The maintainer released a workaround in v0.8.5, described it as very fragile, and stated he expects Reddit to continue making changes that may break it. Another open bug report shows YouTube feeds intermittently returning 404 for some channels. If Reddit or YouTube widgets matter to you, plan for periodic breakage and upgrades.

The project manages scope explicitly with roadmap, backlog, and icebox labels. Examples from the evidence: creating a default config file is on the roadmap, Proxmox monitoring is in backlog, while translation support and a ping option for the monitor widget are in the icebox, meaning no current plans. That is a useful signal: do not expect niche monitoring features to arrive soon.

limitations you should know about

• No auto-refresh. The FAQ says a page refresh is required; the request for interval-based refresh remains open. If you keep the dashboard open all day expecting fresh data, it will not update itself.
• Fetch-on-load caching. There are no periodic background requests. Every page load triggers fetches that are then cached with per-widget, configurable lifetimes, so heavy widget counts mean every browser refresh is a burst of outbound requests.
• Monitoring is display-only. The monitor widget reports status when the page is loaded, and ping-based checks are in the icebox. Do not build an outage response workflow on it.
• Custom widgets take work. Iframe, HTML, extension, and custom API widgets exist, but anything beyond defaults means writing templates or fetching external HTML and JSON, which is development and maintenance effort.
• AGPL-3.0 license. This is a strong copyleft license. If you modify Glance and make it available over a network, review your obligations, especially if you intend to distribute or sell a modified version.

alternatives and evaluation questions

If Glance does not fit, evaluate tools by category rather than by name. For a startpage or team dashboard, compare other self-hosted dashboard projects. For feed reading with read and unread state, a dedicated RSS reader is a better fit. For alerting on outages, use an uptime monitoring tool alongside or instead of a dashboard. This review includes no benchmarks or runtime comparisons of those alternatives, so base the decision on your own requirements.

Questions to answer before you commit:

• Do you need the page to update itself, or is a manual refresh acceptable?
• Which widgets are essential, and do they depend on services that change their APIs?
• Can you maintain a YAML configuration and a versioned upgrade process?
• Who will authenticate, and will you terminate TLS and authentication at a reverse proxy?
• Does AGPL-3.0 fit your organization’s licensing policy?

verdict: solid for homelabs, conditional for production

As of v0.8.5 (reviewed 2026-08-11), Glance is a well-scoped, actively maintained self-hosted dashboard. Most homelab users will find it useful if they accept YAML configuration and the volatility of third-party widgets. For production or multi-user use, it is conditional: deploy it behind authentication, supply your own health checks, budget time for upstream API breakage and upgrades, and pair it with a real monitoring tool if the data matters operationally.

sources

• Glance repository (glanceapp/glance)
• Glance v0.8.5 release notes
• Glance configuration documentation
• Issue #1016: Reddit widget 403
• Issue #290: Glance timing out (monitor and weather)
• Issue #327: auto-refresh request
• Issue #589: create a default glance.yml on first start

how I can help

I am Xiang Peng at XP812. If Glance looks right for your setup, I can handle the Linux deployment side: writing the systemd unit or Docker compose file, wiring a reverse proxy with authentication, setting up health checks and configuration backups, and keeping the dashboard updated as upstream releases land. If you need custom widgets or a different dashboard, I can evaluate options against your requirements before anything is installed.