The technology follows the organization. Not the other way around.
Composed per organization. Every system draws on the same engineering disciplines; only what the outcome requires is used.
Canonical data models, entity resolution, knowledge graphs, lineage, provenance and bitemporal state.
Written policy translated into executable rules, eligibility conditions, authority boundaries and evidence requirements.
Statistical models, anomaly detection, classifiers, calibration, simulation and counterfactual testing.
Investigation, supervision, decision and assurance applications built around the actual work.
Language models and agentic workflows where probabilistic systems genuinely improve the outcome, inside approved boundaries.
Inputs, decisions, policies, model versions and approvals preserved so consequential actions can be reconstructed.
Every build is engineered around the organization’s existing technology and designed to operate within its governed environment.
The disciplines compose into one system, deployed as layers inside the organization’s environment.
Inside your environment. Under your control.
Fenori’s current architecture is designed for deployment inside your own cloud environment, within your technology and governance requirements. Fenori operates as a tenant of your environment, subject to its controls. Not a destination for your data.
| Control | Position | Held by |
|---|---|---|
| C01Deployment model | Inside the organization’s own cloud account and network boundary. | Organization |
| C02Data residency | Designed so data remains in the organization’s chosen region, with no egress to Fenori required. | Organization |
| C03Identity & access | The organization’s identity provider, roles and least-privilege permissions. | Organization |
| C04Model access | Only models the organization has approved, reachable only where it permits. | Organization |
| C05Audit & evidence | Decisions, inputs and actions can be preserved so consequential outcomes can be reconstructed. | Organization |
| C06Human authority | The organization defines where judgment stays with a named person. Absolute. | Organization |
| C07Independent assurance | Not yet held. We will publish the scope and the date when it is, and not before. | Not held |
Security documentation, architecture detail and questionnaire responses are available to organizations under review.
Security →AI is a capability. Not the product.
We use AI where it makes the organization more capable. Where it does not improve the outcome, it does not belong. You determine where it is permitted, what it can access, and where human authority remains absolute.
Inside the organization’s own cloud environment. Fenori’s current architecture is designed to operate as a tenant of that environment, subject to its controls, within its technology and governance requirements. Fenori is not a destination for the organization’s data.
No. There is no standard Fenori deployment. Every system draws on the same engineering disciplines, data foundations, policy and control systems, quantitative and model systems, operational applications, applied AI, and evidence and memory, but only what the outcome requires is used. The technology follows the organization rather than the other way around.
As a capability, not as the product. AI is used where it makes the organization more capable, and where it does not improve the outcome it does not belong. The organization determines where it is permitted, what it can access, and where human authority remains absolute.
No. The architecture is designed so that data remains in the organization’s chosen region, with no egress to Fenori required. Access runs through the organization’s identity provider, roles and least-privilege permissions, and only models it has approved are reachable, only where it permits.