Homelab Glance
See your homelab at a glance — containers, health, and start/stop/restart, from widgets on your phone or Mac.
contact
Get help with Homelab Glance
Email is the fastest route, and it always works — the form below is a convenience, not the only way in.
A first reply within two business days, from anmol@ponderance.dev.
Send a message
It reaches the same inbox, tagged with Homelab Glance.
Common questions
Where do the address and tokens go?
Settings → Aggregator. Base URL is the address of your glance aggregator, Widget token is its WIDGET_TOKEN, and Control token is its CONTROL_TOKEN. Both tokens are kept in the system Keychain.
Why is start/stop/restart greyed out?
Those actions need the control token, which is separate from the widget token on purpose — read access and write access are different keys. Add the CONTROL_TOKEN in Settings → Aggregator and the controls light up.
I just want to see what it looks like.
Turn on Settings → Use mock data. Every card, widget, and control then runs on bundled sample data and never contacts a server.
Why does my widget show old data?
iOS budgets how often widgets may refresh, so a widget can trail the app by minutes. Opening the app refreshes it immediately and re-shares the current state with every widget.
How do the widgets reach my server?
The app and its widgets share one private App Group on the device, so the address, tokens, and your card layout are written once and read by both. The widget then talks to your server directly.
It works at home but not away.
A LAN-only aggregator is unreachable off your network by design. Expose it over HTTPS, or put your device and server on the same VPN or Tailscale network and use that address as the Base URL.
Which containers show up?
Whatever your aggregator reports. Choose which of them appear, reorder them, and set widget defaults in Settings → Manage cards.
What do you know about my setup?
Nothing. No server of ours, no analytics, no crash reporting — so a support email needs you to describe the symptom, including what Settings → Test connection reports.
When something goes wrong
in the order it actually failsTest connection fails
- Open the same Base URL in a browser on the same device — if that fails, the app is not the problem.
- Include the scheme and port exactly as your browser does.
- Re-paste the widget token; a rotated or truncated token fails identically to a wrong address.
- Toggle Use mock data on and off — working on mock data narrows the problem to the connection.
Cards are empty or a container is missing
- Check the aggregator directly: if it does not report the container, the app cannot show it.
- Open Settings → Manage cards and confirm the container is not simply switched off there.
- Pull to refresh in the app, which forces a fresh fetch rather than a cached one.
- Confirm the widget token still has access — a rotated token shows as an empty dashboard, not an error.
Your data
- There is no account to delete — Homelab Glance never creates one.
- The aggregator address, both tokens, and your card layout live only on your device.
- Deleting the app removes all of it, Keychain entries included.
- To cut access from the other side, rotate WIDGET_TOKEN and CONTROL_TOKEN on your aggregator.
what you need
Requirements
- iPhone or iPad running iOS 17 or later, or a Mac running macOS 14 or later.
- The open-source glance aggregator running on your own server (a small Docker container) — there is no server of ours in the path.
- The aggregator’s WIDGET_TOKEN, plus its CONTROL_TOKEN if you want start, stop, and restart rather than read-only.
- Nothing at all, to try it: the bundled demo data makes every screen work with no server.