Architecture guides
Reference designs for the way Nexus actually gets deployed.
Five reference architectures covering the control and execution planes, deployment topologies, integration patterns, sovereign AI and a SOC built on Sentinel. Each is shared as a working document with your architects, not a generic diagram.
- reference architectures
- 5reference architectures
- shared with your architects
- On requestshared with your architects
- deployment topologies covered
- 4deployment topologies covered
- and access detail in every guide
- Identityand access detail in every guide
The guides
Five topics, matched to how deployments actually get planned.
Each guide can be requested independently or as a set, depending on where you are in a design process.
Control plane and execution plane
How Nexus separates the control plane, which holds workflow definitions, policy, credentials metadata and audit records, from the execution plane, which runs the actual workflow steps. Covers why this separation matters for scaling and for keeping sensitive execution inside a specific network boundary.
Related page: Platform architecture overview
Deployment topologies
Reference layouts for on-premises data centre, private cloud, sovereign or regulated cloud regions, and air-gapped deployment, including how updates, connector actions and model artefacts move into a disconnected environment.
Related page: Deployment overview
Integration patterns
How Nexus connects to ERPs, CRMs, databases such as MSSQL, Oracle, PostgreSQL and MySQL, SAP RFC, SOAP and GraphQL services, and infrastructure APIs, including patterns for high-volume synchronisation and event-driven triggers.
Related page: Integration patterns
Sovereign AI reference design
A reference layout for self-hosted model endpoints, the model registry, knowledge bases and guardrails, including how retrieval is scoped to existing document permissions and where human review sits in the pipeline.
Related page: Sovereign AI
SOC reference design
A reference architecture for a sovereign security operations centre built on Nexus Sentinel, covering ingestion, detection content, case management and the boundary between automated response actions and analyst-approved actions.
Related page: Nexus Sentinel
What each guide contains
A consistent structure, so architects know what to expect.
Every guide covers the same categories, adapted to its topic, so your team can compare them directly.
- Component diagram
- The systems and Nexus components involved, with data flow direction shown explicitly.
- Deployment notes
- Where each component can run, including constraints specific to air-gapped or sovereign cloud deployment.
- Identity and access
- How SSO, MFA, RBAC and AD/LDAP integration apply to the design, and where vault-managed secrets are used.
- Sizing considerations
- The factors that drive resource sizing for the described topology, described qualitatively rather than as a fixed benchmark.
- Known trade-offs
- What the design optimises for and what it does not, stated plainly rather than glossed over.
Requesting a guide
Shared directly, with a conversation attached.
Architecture guides are detailed enough that they are more useful with someone available to answer follow-up questions.
What to include in your request
Tell us which guide or guides you need, the environment you are designing for (on-premises, private cloud, sovereign cloud or air-gapped), and any constraints already known, such as an existing identity provider or a mandated network segmentation model.
We typically share the guide alongside a short working session with a solutions architect so the document can be applied directly to your environment rather than read in isolation.
Architecture session
Request the guides relevant to your design.
Send us the topology you are working towards and we will share the matching reference architectures along with a solutions architect who can walk through them.