Skip to content
NexusBook a demo

Product family

One sovereign platform. Complete products for security, AI and governed operations.

Atlas, Cerberus, Sentinel and Shield are complete, deployable products powered by Nexus. Foundry extends the same platform with governed self-service, and Edge carries the traffic infrastructure underneath. Every one of them runs inside your estate, with your identity, your secrets and your evidence.

Book a demo Explore the platform

External assurance

Nexus Atlas

AI application security

Nexus Cerberus

Security operations

Nexus Sentinel

Request-layer protection

Nexus Shield

Governed self-service

Nexus Foundry

Traffic infrastructure

Nexus Edge

Common foundation

Nexus platform: execution, integration and governance

  • Orchestration
  • Integrations
  • Identity
  • Secrets
  • Approval
  • Audit
  • Observability
Each product owns a domain. The platform underneath is what they all execute on.
flagship security products
4flagship security products
shared execution and governance layer
1shared execution and governance layer
self-hosted, sovereign cloud or air-gapped
Sovereignself-hosted, sovereign cloud or air-gapped
audit and approval inherited by every product
Evidencedaudit and approval inherited by every product

Start here

Which product do you need?

Most buyers arrive with a problem rather than a product name. Find the question closest to yours and follow it through to the product that answers it.

01

Do you need continuous assurance over everything you expose to the internet?

Nexus Atlas

Continuous attack-surface mapping, explicitly authorised and consent-gated non-destructive validation, AI-assisted analysis and a cryptographically signed dossier you can hand to a regulator, board or partner.

  • Attack surface
  • CTEM
  • Authorised validation
  • Signed dossier
02

Do you need to secure the AI applications and models you are putting into production?

Nexus Cerberus

Register AI endpoints, red-team them against the OWASP LLM Top 10, tag findings to MITRE ATLAS, scan the model supply chain into an AI-BOM and produce signed risk reporting, with corpora and judge models held locally.

  • AI-SPM
  • Red-teaming
  • OWASP LLM Top 10
  • AI-BOM
03

Do you need detection, investigation and response that never leaves your boundary?

Nexus Sentinel

Security telemetry, open Sigma detection content, MITRE ATT&CK coverage, correlation, cases, investigation and governed response, with approval gates where policy requires them and a full audit record.

  • SIEM
  • SOAR
  • Sigma
  • MITRE ATT&CK
04

Do you need to protect web applications and APIs at the point of request?

Nexus Shield

Request inspection, attack classification, narrowly scoped rule tuning and behavioural decisions such as ban, captcha and throttle, with request-level evidence that Sentinel can correlate.

  • WAF
  • Scoped tuning
  • Behavioural decisions
  • Request evidence

Do you need to publish and govern what internal teams can request?

Nexus Foundry, on the Nexus platform

A governed catalogue across infrastructure, platform services, application services, workflows and AI agents, with request wizards, cost visibility, policy-driven approvals, provisioning and adoption visibility.

Architecture

Six domains. One execution layer underneath.

Each product owns a distinct domain and is sold and supported as a product. They are coherent because they are not separate codebases stitched together: they execute, integrate, authenticate and audit through the same Nexus foundation.

01

Products own the domain

Atlas answers what is exposed. Cerberus answers what your AI applications expose. Sentinel answers what is happening and what was done about it. Shield answers what reached the application and what was enforced. Foundry answers what people can request and on whose authority. Edge carries the traffic those services depend on.

02

The platform owns the operating model

Workflow orchestration, prebuilt integrations, identity with SSO, MFA and RBAC, vault-backed secrets, human approval and the audit record are platform capabilities. Products inherit them rather than reimplementing them, which is why governance looks the same whichever product you start with.

03

Sovereignty is a property of the foundation

Because the foundation is deployed inside your estate on a Kubernetes-agnostic footprint, every product on top of it can run on-premises, in a sovereign cloud or air-gapped, with data, models, credentials and evidence held under your control.

External assurance

Nexus Atlas

AI application security

Nexus Cerberus

Security operations

Nexus Sentinel

Request-layer protection

Nexus Shield

Governed self-service

Nexus Foundry

Traffic infrastructure

Nexus Edge

Common foundation

Nexus platform: execution, integration and governance

  • Sovereign deployment
  • Orchestration
  • Integrations
  • Identity
  • Secrets
  • Approval
  • Audit
Each product owns a domain. The platform underneath is what they all execute on.

Flagship products

Four complete security products.

Each is bought and deployed on its own, and each carries the same sovereign operating model. Follow any one through to its product page for the full capability detail.

01

Sovereign offensive assurance

Nexus Atlas

Atlas gives security leadership a continuously maintained, evidence-backed picture of the external attack surface, from discovery through explicitly authorised validation to a cryptographically signed dossier.

Explore Nexus Atlas
  • Continuous external attack-surface mapping and enumeration
  • Consent-gated, non-destructive active validation within an authorised scope
  • AI-assisted analysis with human review before findings are issued
  • Chain of custody and a cryptographically signed dossier
Built for
CISOs, national CERTs, government and defence, regulated enterprise continuous assurance programmes.
Primary outcome
A defensible, current statement of external exposure that stands up to scrutiny.
02

Sovereign AI application security and posture management

Nexus Cerberus

Cerberus treats AI applications as assets to be inventoried, tested and evidenced, with attack corpora, detectors and judge models running inside your environment.

Explore Nexus Cerberus
  • Registry of AI endpoints, models and their owners
  • Red-teaming against the OWASP LLM Top 10, tagged to MITRE ATLAS
  • Model supply chain and dependency scanning into an AI-BOM
  • Signed risk reporting for auditors, regulators and customers
Built for
AI security and AppSec teams, model governance functions, institutions adopting AI under regulation.
Primary outcome
Evidence of what your AI applications expose, produced without sending prompts or models outside.
03

Sovereign SIEM and SOAR

Nexus Sentinel

Sentinel centralises security telemetry, detection, correlation, investigation, case management and governed response in one product that operates entirely within the customer estate.

Explore Nexus Sentinel
  • Telemetry ingestion, search, retention and lifecycle under your policy
  • Open Sigma detection content with MITRE ATT&CK coverage visibility
  • Correlation, cases, observables and analyst investigation
  • Runbooks with retries, failure policy and approval gates on impactful actions
Built for
SOC teams, national CERTs, defence, critical infrastructure and regulated enterprise.
Primary outcome
Detection and response capability with the logs, cases and evidence kept inside your boundary.
04

Sovereign web application firewall and behavioural protection

Nexus Shield

Shield inspects and enforces at the request layer, then records what was inspected, classified and blocked so tuning is a documented decision rather than a blanket exception.

Explore Nexus Shield
  • Request inspection with pass, block, deny and drop outcomes
  • Attack classification across injection, abuse, scanner and bot activity
  • Scoped rule tuning by URI, argument and host, each with a stated reason
  • Behavioural decisions such as ban, captcha and throttle, with expiry
Built for
Application security and platform engineering teams protecting internet-facing services, portals and APIs.
Primary outcome
Precise request-layer protection with evidence Sentinel can correlate against other signals.

Platform module

Nexus Foundry: governed self-service across everything an institution offers.

Foundry is not a fifth security product. It is the governance and self-service layer on the Nexus platform, for institutions that want internal teams to request capability through a controlled front door instead of a queue of tickets and side agreements.

Catalogue

Five service classes in one place

Infrastructure services, platform services, application services, workflows and AI agents are published as certified catalogue items, each with an owner, parameters, eligibility and cost visibility.

Request

Wizards, policy and provisioning

Requests are made through structured wizards, routed through policy-driven approvals and provisioned by Nexus workflows, so what was requested, approved and delivered is one continuous record rather than three disconnected ones.

Measure

Adoption visibility, read carefully

Foundry shows which departments are requesting and using services, workflows and AI agents. That comparison helps leaders invest where demand is proven and investigate where enablement, training, policy or service design may need attention. It is departmental usage visibility, not employee scoring, and it does not assert why adoption is low.

Foundry lifecycle

  1. 01

    Publish

    Certify a service, workflow or agent into the catalogue.

  2. 02

    Request

    Structured wizard captures scope, parameters and cost.

  3. 03

    Approve

    Policy decides who approves and on what authority.

  4. 04

    Provision

    Nexus workflows deliver the request end to end.

  5. 05

    Audit

    Every step is retained as an inspectable record.

  6. 06

    Measure

    See where adoption is growing across departments.

Built for platform teams, enterprise IT, public sector organisations and internal developer and service portals.

Supporting infrastructure

Nexus Edge: the traffic layer beneath the applications you protect.

Edge provides load balancing and traffic infrastructure for services running in your estate. It sits under the security products rather than beside them: Shield enforces at the request layer, Sentinel correlates and investigates, and Edge keeps traffic reaching the services in the first place.

What Edge handles

Load balancing and traffic infrastructure for applications and APIs operated inside your environment.

How it relates to Shield

Edge distributes traffic. Shield inspects, classifies and enforces on the requests that arrive. Neither replaces the other.

How it relates to Sentinel

Sentinel remains the place where signals are correlated, investigated and answered under governed response.

Shared foundation

Powered by Nexus, and what that actually gives you.

Products inherit the same sovereign operating model because Nexus is their embedded foundation, not a separate prerequisite purchase.

  • Sovereign deployment

    On-premises, sovereign cloud or air-gapped, on a Kubernetes-agnostic footprint inside your estate.

  • Integration and orchestration

    Prebuilt actions and workflow execution across the systems each product has to reach.

  • Identity and access

    SSO, MFA and role-based access, federated from the directories you already run.

  • Vault-backed secrets

    Credentials and keys held in the platform vault, never scattered across product configuration.

  • Human approval

    Approval gates as a first-class control on actions with operational consequence.

  • Audit and evidence

    A retained record of what ran, on whose authority, against what input and with what result.

  • Observability

    Execution status, timing and health visible from the same governed workspace.

  • One operating model

    Adding a second product extends what you already govern instead of starting again.

Powered by Nexus

Built on the same execution layer we sell as a platform.

Atlas, Cerberus, Sentinel, Shield and Foundry all execute on the Nexus platform: the same workflow engine, approval nodes, vault-backed secrets, identity model and audit record. That is why they keep data, models and evidence inside your boundary, and why the governance you set up for the first product applies to the next one.

You do not need to buy or implement the Nexus platform to run this product. The shared foundation is why the product deploys into your environment, keeps its data local and produces an audit record you can inspect.

Explore the Nexus platform

Combinations

How institutions usually put these together.

Each product stands on its own. These are the pairings that come up most often once a second product is added.

Shield+Sentinel

Protect requests, correlate signals, govern the response

Shield enforces at the request layer and emits request-level telemetry. Sentinel correlates that with endpoint and other sources, opens cases, and can drive enforcement back through governed runbooks where policy allows.

  1. Request
  2. Shield
  3. Telemetry
  4. Sentinel
  5. Governed response
Atlas+Sentinel

External assurance findings that reach operations

Atlas findings arrive with evidence and chain of custody. Where the operating model calls for it, Nexus workflows carry those findings into Sentinel cases and remediation tracking rather than a spreadsheet.

  1. Discovery
  2. Validation
  3. Signed dossier
  4. Sentinel case
Cerberus+Sentinel

AI security findings alongside the rest of the SOC

Cerberus produces registry entries, red-team findings and AI-BOM results. Those can be routed into the same case and workflow layer the SOC already uses, so AI risk is handled through existing operations.

  1. AI registry
  2. Red-team
  3. Findings
  4. SOC workflow
Foundry+Nexus platform

Governed self-service for infrastructure, workflows and AI agents

Foundry publishes what teams may request; the platform provisions it through workflows with approval and audit attached. Adoption visibility then shows where the catalogue is being used.

  1. Publish
  2. Request
  3. Approve
  4. Provision
  5. Measure

Buyer pathways

Where teams like yours usually start.

Pick the pathway closest to your mandate and read the matching solution or industry page before scoping a pilot.

Public sector and defence

Sovereignty, air-gapped operation and evidence that survives scrutiny usually decide the shape of the first deployment.

Regulated enterprise

Compliance evidence, retention under your own policy and a demonstrable approval trail across every automated action.

Platform and automation leaders

A governed front door for internal demand, and automation that reaches the systems and infrastructure you already run.

Security operations teams

Detection, investigation and response with the telemetry, cases and evidence held inside the boundary you control.

AI governance and AppSec

Inventory of AI endpoints, structured testing against known AI weakness categories, and reporting you can defend.

Talk to the team

Not sure which Nexus product fits?

Tell us the problem you are solving first. We will walk through Atlas, Cerberus, Sentinel, Shield and Foundry against your environment and constraints, and help you scope a first deployment that stands on its own.

Book a demo Talk to the team