English
Glance Hosting
Build a personal dashboard on one page: RSS feeds, weather, service monitors, bookmarks, calendars and more, arranged how you like.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Glance’s official links and original website
Glance Website
More
Tech
- Docker image
- glanceapp/glance:latest
- Default port
- 8080
How Glance works
Glance reads a YAML configuration that defines pages, columns, widgets, appearance, and the external sources each widget should query. A page can combine RSS feeds, calendars, weather, bookmarks, service status, search, video channels, or other supported components into a compact browser dashboard. The server renders the configured view and periodically retrieves data required by those widgets.
The catalogue starts with a sample glance.yml, so useful deployment requires editing that file to match the owner’s sources and layout. Glance does not provide an application login in this configuration. Anyone who can reach the dashboard address can view the material it displays, which makes source selection and surrounding access controls important.
Key Glance features
Pages and columns organise information by topic, while widgets keep feeds, calendars, links, and status summaries visible without opening many sites. YAML makes the configuration portable and reviewable, and themes allow the presentation to fit a personal or team start page. Mobile-oriented layouts keep the dashboard usable on smaller screens.
Widgets depend on outside services remaining available and returning compatible data. Some require API keys, tokens, feed addresses, or public endpoints that the user must supply. A dashboard may expose sensitive calendar titles, private feed items, internal service names, or embedded credentials if the configuration is careless.
Who uses Glance
Developers can combine project feeds and service links, operators can create a read-only status overview, and individuals can build a personal homepage for news, calendars, weather, and bookmarks. It is effective when the information can be presented as a dashboard rather than edited collaboratively.
Glance is not a monitoring backend, password manager, team wiki, or identity service. It displays information supplied by widgets and sources; it does not guarantee the accuracy, privacy, or availability of those external systems.
Self-hosting Glance: requirements and cost
Resource use depends on configured pages, widgets, refresh behaviour, external feeds, concurrent viewers, and the size of returned content. The catalogue does not require PostgreSQL or MariaDB, and the primary persistent input is the YAML configuration. External API limits and provider credentials remain outside the hosting plan.
AvaHost maps Glance to Plan 1 at €2. Glance includes one-click deployment, automated HTTPS for its custom address, application updates, and scheduled backups. The starter configuration must be edited before the page reflects the owner’s needs. Because there is no built-in login in this deployment, the dashboard should be treated as visible to anyone who can access its URL unless protection is applied outside Glance.
F.A.Q
Glance starts at €2 on Plan 1. Page count, widgets, refresh patterns, external feeds, returned content, and concurrent viewers affect resource use. The hosting fee covers the dashboard service and its configuration, while third-party API accounts, data subscriptions, provider rate limits, and credentials remain the customer’s responsibility.
Not required. The catalogue deployment does not add PostgreSQL or MariaDB; Glance primarily reads its YAML configuration and retrieves data for configured widgets. Protect the configuration because it may contain private feed URLs, tokens, internal hostnames, or other sensitive details. Scheduled backups cover the hosted installation, but outside sources retain their own data.
A custom hostname can serve Glance with automated HTTPS after DNS points to AvaHost. Because the application has no built-in login in this configuration, anyone reaching that address may view the dashboard. Avoid displaying private calendars, secret feeds, internal service names, or credentials unless access is protected through an approved layer outside Glance.
The catalogue supplies a starter `glance.yml` file. Edit that YAML to define pages, columns, widgets, themes, feeds, and any required provider credentials, then validate the syntax before relying on the page. External services can fail, change formats, or enforce rate limits, so test each widget and avoid treating the dashboard as the underlying monitoring system.