/ platform · govern & protect
Understanding creates a better basis for control.
Five capabilities that keep a comprehended estate trustworthy: what changed, what it looked like before, how to get it back, what may act, and what to isolate.
What that removes.
A changed field should fail here, not in a job at three in the morning. A version should be reproducible. A manifest should not go live just because it could. A bad change should stop where it was found, and there should be a record that any of this happened.
The five capabilities.
Governance is a property of the platform rather than a tax added after the technology is already connected.
Change Monitoring
Providers change their APIs without telling you. Inferrex watches the surfaces you depend on and reports what moved, before a pipeline discovers it the hard way.
Version Management
Every understanding Inferrex builds is versioned. You can see what a system looked like before a change, and move between versions deliberately rather than discovering drift.
Backup & Recovery
Comprehension, mappings and configuration are recoverable. Losing the platform should never mean rebuilding the understanding of your estate from scratch.
Manifest Approval
Changes to what Inferrex will act on are proposed, reviewed and approved before they take effect. Nothing reaches a production system because inference was confident.
Anomaly Detection & Quarantine
When data or behaviour departs from what the understanding predicts, it is isolated rather than propagated. A bad payload stops at the boundary instead of spreading through the estate.
The architecture underneath them.
Tenant isolation, encryption and secrets, scoped access and where inference runs are described in full under Platform controls.
Isolation is enforced at the database layer rather than in application code, so a missed check is a failed release rather than a silent leak. Credentials are managed through the platform's secrets architecture. Sovereign and air-gapped environments are designed to avoid external inference dependencies — the boundary you chose is not quietly crossed to answer a classification question.
The full detail is on the technical page and in the security overview.
Governance should be a property of the platform.
Not a tax added after the technology is already connected.