Verified product boundaries
This page states only the controls the current product supports today.
Each customer has a separate installation. Settings, connected-system logins, and operating data are not shared between customers.
Opero reads only the systems deliberately connected for the agreed workflow and site boundary.
Customer operating data is not used to train a model shared with other customers.
A fresh deployment starts in observation mode. Write-back is enabled deliberately, per site and action category.
Recommendations, approvals, changes, and reversals are added to the audit history with their actor and channel.
A kill switch pauses the system, and changes to your systems can be switched off per site without removing read access.
Bring the systems, sites, and actions you have in mind. We will map what Opero reads and where you decide.