Trust and control
Trust is enforced by the database
Security is built into the data layer, not added on top. Roles are set per building, tenants are kept apart by the database itself, corrections never overwrite the original, and nobody can edit the audit log. The AI follows exactly the same rules.
Security controls
Roles per building
Admin in one tower, Viewer in the next. People see and change only what their role in that building allows.
An audit log nobody can edit
Every change is recorded, append-only. Not even a Super Admin can alter or remove an entry.
Each customer walled off
Row-level security in the database keeps tenants apart, so one customer's query can never return another's data.
Corrections never overwrite
The original reading or invoice stays. Who corrected it, when and why are logged beside it.
Secure by default
Encryption and secure device connections. Sign-in locks after 5 failed attempts, with short sessions and rotating refresh tokens.
AI inside the same rules
Chat and agents see only what a user's role allows, and every action they take lands in the audit log.
For heads of security and IT
Questions your security review will ask
We'll walk your team through the architecture, the data flows from meter to cloud, and how deployments run in the cloud or on site.
Book a security walk-throughWhere does our data live?
In the cloud, or on an on-site box for buildings that must keep data on premises.
How do devices connect?
Over secure device connections from gateways and brokers you approve; nothing on site is rewired.
Who can see what?
Only the buildings and functions a role allows, enforced in the database, for people and AI alike.
Next step
Smarter data. Smarter energy. Smarter urban living.
Tell us about your buildings. We'll show you the products on data like yours.