Top layer
No model training on customer data
Customer content is processed for requests, not model training.
A three-layer operating model.
Top layer
Customer content is processed for requests, not model training.
Middle layer
Storage, search, and application access boundaries are enforced per organisation.
Base layer
Your organisation controls its data and how it is used.
Source to output in four steps.
Files enter from approved sources.
Content is chunked and indexed in-boundary.
Relevant context is selected per request.
A cited output is returned.
Source files, derived indexes, and access configuration.
Prompts, retrieval context, and model responses.
Controls grouped by domain.
SSO-compatible identity and role-based access.
Short-lived signed tokens scope each embedded experience.
TLS in transit and encryption at rest.
Access rules follow tenant boundaries across storage and search.
Captured events and storage depend on deployment and policy.
A direct comparison of operating models.
Managed
Fastest to deploy
Private
Maximum control
Built on Azure services with established security and compliance programs.
Additional review documentation is available on request, including architecture, data flow, control mapping, and deployment detail.
Next step
We'll align on your scope, deployment model, and what your team needs for a practical security review.