Product · Dashboards & SCADA

Dashboards you build by describing them

Live operational dashboards and SCADA-style views you stand up and rearrange in plain English. Devices, fault analysis, cost estimation, and reports ship as ready modules. No hand-coded widgets.

Dashboards & SCADA
1

The old way: a screen-building project for every screen

Traditional SCADA and BI tooling makes a dashboard its own mini-project. Someone wires tags by hand, hard-codes each gauge and trend, fiddles with layouts, and ships a static screen that's stale the moment the line changes. Need a new view for a shift lead or a one-off fault investigation? That's a ticket, an integrator hour, and a wait. Most teams end up with a handful of frozen dashboards nobody trusts and a pile of exported spreadsheets doing the real work.

  • Every screen hand-wired widget by widget, tag by tag
  • Layout changes require an integrator or a developer
  • Static views drift out of sync as equipment and thresholds change
  • Fault digs and cost questions end up in throwaway spreadsheets
2

How it works in Sentrel: say the change, see the change

In Sentrel you describe what you want in a sentence — "add a trend of compressor outlet pressure next to the live status tile" or "split this into one panel per pump and flag anything over 80 C" — and the AI editor lays it out against your typed schema, then renders it live over WebSocket. Rearrange, scope, and drill down the same way. Dashboards and full SCADA-style process views share one model, so a tag you're already ingesting is one instruction away from being on screen.

  • Natural-language create and rearrange — no widget config, no code
  • Live data over WebSocket, bound to your validated reading schema
  • SCADA process views and operational dashboards from the same source
  • Scoped by RBAC and module permissions, per role and per tenant
3

Why it beats the alternative: modules, not assembly

Stacks like Telegraf + InfluxDB + Grafana or a ground-up Tulip/Losant build leave you assembling and maintaining the screen layer yourself. Sentrel ships the views you actually need as ready modules: a devices overview, fault analysis, cost estimation, and exportable reports — all reading the same live, integrity-hashed data instead of a separate copy you have to reconcile. You get an Ignition-class operator surface without an integrator engagement or a server you have to run, and white-label branding so you can put it in front of customers as your own.

  • Devices, fault analysis, cost estimation, and reports built in
  • Every panel reads the same audited, integrity-hashed readings
  • No integrator engagement and no SCADA server to operate
  • Full white-label branding for OEMs and integrators to resell
Questions

Dashboards & SCADA, answered.

No. You describe the view or the change in plain English and the AI editor builds and arranges it against your typed schema. There are no hand-coded widgets and no query language to learn — though the underlying data stays fully typed and validated.

They're live. Panels stream over WebSocket and update as new readings arrive, the same real-time pipeline that drives Sentrel alerts. SCADA-style process views and operational dashboards run on that same live, schema-validated data.

Devices, fault analysis, cost estimation, and reports come as ready modules reading your live data — no assembly. You use natural language to compose and rearrange custom dashboards and SCADA views on top, and everything respects RBAC, module permissions, and white-label branding.

Stop integrating. Start monitoring.

Describe what you want to watch, connect the gateway you already own, and be live this afternoon — no integrator, no proprietary hardware, no six-month project.