A dashboard that behaves like a well-made start page
Glance has a disciplined idea of what a self-hosted dashboard should be. It gathers information you already check, including RSS articles, YouTube uploads, Twitch channels, weather, market prices, releases, Docker health, and server statistics, then renders it as a clean page. It is less interested in becoming a full household portal than Homepage or Homarr. That narrower focus is why it feels quick and coherent.
The implementation supports the pitch. Glance is written in Go, ships as a binary under 20 MB and a similarly small container, and uses minimal vanilla JavaScript. The README says an uncached page usually loads in about one second, depending on the network and widget mix. The layout adapts to mobile, and themes can be changed by adjusting a small set of values.
This makes Glance especially good as a personal browser home page. Pages and tabs prevent the result from becoming one endless panel, while groups let related widgets share the same space.
Setup is short, configuration is the real work
The recommended installation is credible. Download the Compose template, edit its files, and run docker compose up -d. There are also prebuilt binaries for Linux, Windows, and macOS across common x86 and ARM architectures. A manual binary looks for glance.yml beside itself unless given another path. The supplied example gives new users a working structure instead of an empty screen.
Expect to spend most of the first evening in YAML. Pages contain columns, columns contain widgets, and almost every widget has its own options. The documentation is excellent at explaining this structure and includes a long sample worth copying. Configuration files reload automatically on save, so iteration does not require restarting the service. Included files make a large setup manageable, and config:print helps inspect the fully resolved result when an include produces confusing YAML line numbers.
There are operational details behind the pleasant demo. Reloading configuration clears cached data, which can trigger upstream rate limits if done repeatedly. Environment-variable changes require a restart. The README also warns that pages with many widgets can exceed the low DNS request limits commonly configured by Pi-hole or AdGuard Home. Tokens and passwords can be injected through environment variables, Docker secrets, or files, but someone still has to provision and rotate them.
Exposing Glance outside the home network deserves care. Built-in username and password authentication requires a generated secret key, and passwords can be hashed rather than stored as plain text. Behind a reverse proxy, the proxied setting and forwarded headers must be correct so login rate limiting sees the real client address. Glance is approachable, but public deployment is not simply publishing port 8080.
Built-in widgets cover a lot, with clear escape hatches
The standard widget catalog is the strongest reason to choose Glance. It covers news and social feeds, media channels, finance, calendars, bookmarks, repository releases, monitoring, Docker containers, and machine metrics. Cache settings keep slow or rate-limited sources from being called on every view. Preconfigured pages and a separate community-widget repository shorten the path to useful layouts.
When the catalog stops short, Glance offers four escape hatches. An iframe can embed another site, static HTML can present a small hand-built panel, an extension can fetch rendered widget content, and a custom API widget can fetch JSON and render it with a Go template. The last option turns many ordinary HTTP APIs into dashboard panels without modifying Glance itself. It is not a no-code tool: the docs explicitly assume basic programming, HTML, CSS, templates, and project-specific concepts. Extensions that permit HTML also require trust in the provider, a risk the documentation calls out directly.
Glance is not a live monitoring console. Most values are fetched when a page loads and then cached; the FAQ says a refresh is required to update the page, apart from elements such as clocks and relative timestamps. If you need instant alerts, streaming graphs, or incident workflows, keep Grafana or another monitoring product in the stack and use Glance as the calm front door.
The limitations are concrete
Several rough edges affect otherwise sensible uses. Read tracking is browser-local, according to the open request for synchronized mark-as-read behavior. Moving from a desktop to a phone therefore loses that context. Translation support is also still requested, making the English interface a poor choice for some shared households. Built-in authentication uses an interactive form, while an August 2026 request asks for HTTP Basic authentication so non-interactive display software can log in.
Third-party feeds can break independently of Glance. Reddit blocked unauthenticated JSON access from many server addresses. Version 0.8.5 added a bypass, but its release notes warn that it may be temporary or inconsistent. The configuration guide documents app credentials, proxies, and VPN routing as alternatives. Treat social widgets as conveniences, not guaranteed data pipelines.
Healthy interest, but a large maintenance surface
Glance had about 36,000 GitHub stars and 345 open issues and pull requests when researched. The last push to the main repository and release v0.8.5 were both dated May 30, 2026. That alone might look quiet, but open issues and pull requests were still being created and updated in August 2026, covering refresh controls, RSS rendering, container health, and documentation. The evidence points to an active community around a maintainer-controlled release process, not an abandoned project.
The AGPL-3.0 license is friendly to personal self-hosting but deserves review before a company modifies the service and provides it over a network. For its natural audience, Glance is easy to recommend. It stays fast, looks unusually finished, and gives skilled users enough extension points without making every user assemble a web application. Just choose it for a curated start page, not for real-time monitoring or shared information state.