Control begins
with where it runs.
Cenovel keeps the network record inside your district, with explicit access, signed releases, and a documented recovery path.
Your estate stays close.
The appliance runs inside the district network. The console sends performance measurements to its own local API. Optional identity, email, webhook, and backup services connect to the destinations you configure.
Review deploymentGive people defined access.
Use the local recovery account or configure Microsoft Entra ID sign-in. Access tiers and page permissions control what users can do. Review both group mappings and individual role assignments when configuring access.
Read about accessVerify before you install.
The native deployment uses signed release bundles and a trusted public key. Verification happens before staging; upgrades use preflight checks, migration controls, and a readiness gate.
Read the upgrade procedureMake restoration part of operations.
Native backup artifacts are encrypted and authenticated. Keep the backup keyring separately, configure an off-box copy, and check restore-drill results for the recovery path.
Review backup and restoreKeep a record of the work.
The console includes an audit trail and diagnostics. Operators can check services and readiness and generate a redacted support bundle when investigating an issue.
Review operational checks