/ platform · govern & protect
Understanding creates a better basis for control.
Inferrex is designed to make technology and data relationships more visible while applying access, protection and audit controls to the platform.
Isolation enforced at the database, not in application code.
Tenant-scoped data is protected at the database layer through row-level security, with release checks designed to verify cross-tenant isolation.
Enforcing it in the database rather than in every query means a missed check is a failed release, not a silent leak.
In transit, at rest, and around credentials specifically.
External surfaces use TLS. Stored infrastructure uses platform encryption, while connection credentials are additionally protected and managed through the platform's secrets architecture.
Scoped, and yours to control where the environment demands it.
Workspace and API access is scoped. Identity and deployment requirements can vary by deployment model, including customer-controlled identity in sovereign environments.
Where inference runs, and on what.
The platform's inference architecture is designed around Inferrex-controlled deterministic and model paths, with customer structural metadata and record content treated differently.
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.
Governance should be a property of the platform.
Not a tax added after the technology is already connected.