Spin up isolated, fully branded monitoring tenants for every customer you serve. Sentrel gives OEMs and integrators a recurring-revenue product to resell, not just a tool to operate.
Most OEMs and integrators face two bad options. Stand up a separate Ignition or InfluxDB+Grafana stack per customer and you inherit a fleet of one-off deployments to patch, secure, and babysit. Or put everyone on one shared dashboard and you leak one customer's plant data into another's view, with your vendor's logo stamped where yours should be. Either way you're billing hours, not capturing recurring revenue, and the platform never feels like your product.
Each customer gets an isolated organization: their devices, schemas, readings, alert rules, and audit trail live behind a hard tenant boundary, so no member of one org can ever see another's data. You theme each tenant end to end -- logo, color palette, and UI -- so your customers log into your product, not a rebadged dashboard. Inside every org, admin and member roles plus module-level permissions let you decide exactly who sees devices, fault analysis, cost estimation, reports, or API/MQTT key management. You provision a tenant in minutes from your console and hand over the keys.
Ignition and AVEVA PI assume one customer running one server -- resell them and you're back to per-site installs and integrator hours. Tulip and Losant hand you a builder and expect you to assemble the product yourself before you can sell anything. Sentrel ships the multi-tenant, white-label platform as the product: one codebase you maintain, an unlimited fleet of branded tenants you bill monthly. You own the customer relationship and the recurring revenue; we keep the broker, ingest, rule engine, and compliance running underneath.
Yes. Every organization is themed independently -- its own logo, color palette, and UI -- so your customers experience the platform as your product, with no Sentrel branding unless you choose to show it.
No. Each organization is a hard tenant boundary. Devices, readings, alert rules, audit trails, and scoped API/MQTT keys are isolated per org, and members of one tenant cannot see or query another tenant's data.
Each org has admin and member roles plus module-level permissions, so you control access to specific modules -- devices, fault analysis, cost estimation, reports, and API/MQTT key management -- on a per-user basis.
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.