Designed for Accountability, Traceability and Control.
RegNexus incorporates governed access, defined authority, controlled automation and traceable operational records across its connected environment.
Authority Is Defined, Routed and Enforced.
Operational permissions reflect defined institutional responsibilities, and sensitive actions can require independent approval.
Institutional access
Access to connected capabilities is governed at the institutional level.
Role-based permissions
Operational permissions reflect defined institutional responsibilities.
Product-specific responsibilities
Each product governs the actions it is responsible for, within its own boundary.
Independent approval where applicable
Sensitive actions can require separate authorisation by another authority holder.
Server-enforced authorisation
Authority is enforced on the server, not assumed from the interface.
Information Is Separated, Authenticated and Traceable.
Institutional information is separated through controlled access boundaries and exchanged through authenticated, governed interfaces.
Tenant isolation
Institutional information is separated through controlled access boundaries.
Governed data exchange
Information moves through authorised interfaces and defined contracts.
Authenticated federation
Connections between products are authenticated before information is exchanged.
Controlled product boundaries
Each product retains responsibility within its own boundary rather than sharing unrestricted database access.
Traceable operational records
Material operational consequences retain supporting provenance.
Automation Must Remain Explainable.
RegNexus distinguishes automated preparation and control evaluation from actions requiring institutional authority.
Automated preparation and deterministic control evaluation accelerate operational work while producing a record of how a conclusion was reached. Actions that require institutional authority remain with the accountable authority holder — automation operates within explicit rules, controls and authority boundaries rather than replacing them.
Material Consequences Retain Supporting Provenance.
Records keep the context required to understand how operational and financial consequences arose.
Source provenance
Material records retain the context of where they originated.
Decision records
Governed decisions retain the basis on which they were made.
Event histories
Operational events are recorded so activity can be reviewed.
Accounting correction trails
Corrections preserve original entries and append reversing records.
Regulatory evidence
Supporting records are retained to inform oversight and review.
We Only Display Independently Verifiable Assurance Claims.
Security is described here as principles and practices. We do not present the following as held or achieved, because we do not claim assurances we have not independently obtained:
- Not claimed: ISO certifications.
- Not claimed: SOC 2 certification.
- Not claimed: External penetration-test approvals.
- Not claimed: FCA product endorsement.
- Not claimed: Regulatory certification of the entire platform.
- Not claimed: Customer security guarantees.
The controls, principles and practices described on this page reflect how RegNexus is designed and operated. Where a specific assurance can be independently verified or evidenced on request, it is presented as such — not as a certification we do not hold.