Trust center
Sovereignty is an architecture decision, not a marketing claim.
This section describes, in specific terms, how Nexus is built so that data, models, credentials, execution, knowledge, audit records and evidence stay under your control. Nothing here claims a certification on your behalf.
- private cloud, sovereign cloud or air-gapped
- On-premisesprivate cloud, sovereign cloud or air-gapped
- models, endpoints and knowledge bases
- Self-hostedmodels, endpoints and knowledge bases
- secrets and credential handling
- Vault-backedsecrets and credential handling
- of every execution
- Full recordof every execution
What sovereignty means
Seven things stay under your control, not just your data's postal address.
Sovereignty, as we use the term, is broader than data residency. A cloud region inside your country answers a location question. It does not answer who can access the data, what a vendor's support staff can see, or what happens if outbound connectivity to that region is lost.
Data
Stays inside the environment you deploy, not replicated to a vendor-operated service to function.
Models
Self-hosted model registry, endpoints and knowledge bases run inside your deployment boundary.
Credentials
Secrets are held in a vault under your control, not inside individual tool configurations.
Execution
Workflows run on infrastructure you operate: on-premises, private cloud, sovereign cloud or air-gapped.
Knowledge
Retrieval indexes and institutional knowledge built from your operations stay inside your environment.
Audit records and evidence
Execution records are generated and retained inside your deployment, available for your own review process.
Trust center
Read the detail behind each part of the architecture.
Sovereignty
What sovereignty means at Nexus and why regional hosting is not the same thing.
OpenSecurity architecture
Identity, access control, secrets, the control plane and execution plane, and observability.
OpenAir-gapped deployment
Operating with no external connectivity, and an honest account of the constraints.
OpenCompliance
How execution records support regulatory evidence, described in alignment terms.
OpenResponsible AI
Self-hosted models, guardrails, human review and deterministic rules first.
OpenTechnical assurance
Signed reporting, reproducible execution records and testing practices.
Open
Shared responsibility
Nexus provides the architecture. You own the posture.
Nexus is built so the controls needed for a strong security and compliance posture are available inside your deployment. The deploying organization decides how those controls are configured, operated and evidenced against its own regulatory obligations.
Where a page in this section references a framework such as NIS2, GDPR or ISO 27001, it is described as aligned with or mapping to that framework's control objectives. Nexus does not itself confer certification, and the deploying organization's compliance function remains responsible for its own accreditation, filings and audit engagements.
Architecture session
Ask us the sovereignty question directly.
Bring your specific data residency, connectivity or model risk requirement and we will walk through how the architecture addresses it.