Hub-Bro pulls numbers from the systems you already run — Prometheus, GLPI, a REST API, a SQL database, a CSV someone emailed you — and puts them on one screen. It runs on your own server, in one container, with your data staying where it is.
Most teams already have monitoring. What they don't have is one screen that answers "is anything wrong right now?" without opening six tabs.
Ticket counts from GLPI next to firewall CPU from Prometheus. Each widget picks its own source, so one dashboard can span systems that have nothing to do with each other.
Read-only share links, plus a kiosk mode that drops all the chrome and refreshes itself — made for the screen on the wall.
An alert speaks only when the state changes. A report arrives at 08:00 whether the news is good or bad — so its silence means something too.
One container, one SQLite file, no external service. Credentials are encrypted at rest and never shown again after you save them.
Each one exists because something real needed it, not to fill a grid.
Instant and range PromQL. Labels arrive as their own columns, so you can filter, group, and join several queries into one table — the thing PromQL itself cannot do.
Sessions and pagination handled for you, filters pushed down to the server, and date maths for contract and licence expiry.
PostgreSQL, MySQL, MariaDB, SQLite, Doris and StarRocks. One
SELECT per widget, read-only, enforced server-side.
Any JSON endpoint. GET or POST with a body, custom headers, and a dot-path to the array inside the response.
DQL and PromQL against the Open API, flattened into rows.
Upload a file and chart it. Sometimes that is the whole requirement.
Line, bar, pie, stat, gauge, table, and markdown text. A stat can carry supporting numbers, a trend, and thresholds that colour it.
Sort on click, search in place, colour cells by value, and draw a bar behind a number so a busy row is visible without reading it.
Click a slice, a bar, or a row and the whole dashboard narrows to it. Click again to let go.
Every distinct layout is kept and restorable, and a second editor gets a warning instead of quietly overwriting your work.
Worth knowing before you install it, rather than after.
Grafana has more panel types, more data sources, and a far bigger plugin ecosystem. Hub-Bro is smaller on purpose: fewer choices, less to learn, and connectors shaped around systems Grafana treats as afterthoughts — GLPI in particular.
It stores no metrics. It queries what you already have, caches the answer briefly, and draws it. If your source is down, so is the widget — and it says so rather than showing a stale number silently.
One workspace, three roles. Dashboards and sources can be private or shared with named people, but there is no notion of separate organisations inside one install.
Hub-Bro