Defense and national security
Automation designed for the environment where the network is not guaranteed.
Nexus runs inside disconnected and classified environments as a first-class deployment mode, not an afterthought bolted onto a cloud product. Logistics, mission support and security operations keep working when the connection to anything outside does not exist.
- operation as a standard mode
- Air-gappedoperation as a standard mode
- AI, no external inference call
- Self-hostedAI, no external inference call
- connection and identity scoping
- Enclave-awareconnection and identity scoping
- execution and detection records
- Signedexecution and detection records
Operational pressures
Speed and control are both requirements, not a trade-off.
Mission environments cannot accept automation that assumes connectivity, and they cannot accept AI that assumes data can leave the enclave.
Connectivity is intermittent or absent by design
Deployed units and secure facilities operate without a reliable path back to a vendor cloud, and any dependency on that path is treated as an operational risk.
Classification boundaries constrain every integration
Data moving between systems has to respect classification levels, and automation that crosses a boundary without explicit control is a finding waiting to happen.
Security operations run continuously against a capable adversary
Detection and response workflows have to correlate signals across sensors and logs fast enough to matter, without sending that telemetry outside the environment.
Logistics and readiness data spans many independent systems
Maintenance, supply and personnel readiness systems rarely share an owner, and manual reconciliation between them is slow exactly when speed matters most.
Systems typically in scope
What integrations usually need to reach.
- Logistics, maintenance and supply systems, reached through databases, APIs and file interfaces
- Security information sources: sensors, network telemetry, endpoint logs and identity events
- Case and ticketing systems used by security operations and mission support teams
- Infrastructure and virtualization platforms across classified and unclassified enclaves
- Messaging and file transfer mechanisms used to move approved data between enclaves
Worked scenario: readiness logistics
A component nearing failure, resolved before it affects tasking.
Deterministic rules handle scheduling logic. A person still approves the order.
- 01
Trigger
A maintenance sensor reports a component nearing its service threshold.
- 02
Integration
Connector steps retrieve the asset's maintenance history, part availability and unit deployment schedule.
- 03
Rules + Code
Deterministic logic checks readiness thresholds, part lead times and scheduling conflicts against unit tasking.
- 04
Human Approval
A maintenance officer reviews the recommended schedule and approves, adjusts or defers it.
- 05
System Action
The approved work order is written to the maintenance system and the part is reserved in supply.
- 06
Audit
The sensor event, retrieved data, rule outcome, approval and resulting order are retained together for readiness reporting.
Worked scenario: security operations
Detection to contained response, without telemetry leaving the enclave.
Nexus Sentinel provides sovereign detection and response; the workflow layer adds case assembly, AI summarization and the approval gate.
- 01
Trigger
A correlation rule inside Nexus Sentinel flags a sequence of events consistent with lateral movement.
- 02
Integration
Related logs, asset ownership and prior incident history are assembled from the systems involved.
- 03
Rules + Code
Deterministic playbook steps isolate affected hosts within policy limits and open a case.
- 04
Sovereign AI
A self-hosted model summarizes the event sequence into a readable narrative for the analyst, without sending any telemetry outside the environment.
- 05
Human Approval
The analyst reviews the case and the proposed response, then approves further containment or escalates.
- 06
System Action
Approved containment actions are executed against the affected systems.
- 07
Audit
The full detection, decision and response sequence is retained as a signed record for later assessment.
Deployment expectations
Disconnected is a designed mode, not a degraded one.
An architecture that only works with a live connection back to the vendor is not a fit for this sector, regardless of what the data sheet claims about on-premises support.
No call-home licensing
Licence validation and platform operation do not depend on reaching a vendor endpoint. Update and licence handling for disconnected sites is covered in detail on the air-gapped deployment page.
Enclave and classification-aware boundaries
Workspaces, credentials and connections are scoped so that a workflow operating in one enclave cannot silently reach across a classification boundary it was not explicitly configured to cross.
Self-hosted models stay inside the enclave
Model endpoints, knowledge bases and guardrails run on infrastructure inside the same boundary as the data they process. There is no external inference API in the request path.
Evidence and reporting
Signed, retained records for after-action review.
Security and mission assurance reviews need a first-hand record of what happened, produced by the system that did the work.
What the execution record contains
- Trigger, retrieved data, rule outcomes and any model output for each run
- Reviewer identity, decision and reason for every human approval
- Signed reporting from Nexus Cerberus for AI system assessments
- Detection and response sequences retained inside Nexus Sentinel
What Nexus does not claim
- Autonomous decision-making that removes the human approval step
- Guaranteed detection of every adversary technique
- A specific accreditation held by Nexus on the customer's behalf
Use cases
Processes defense & national security teams run on Nexus.
Each combines two or more systems in one governed run, with approval and audit.
ServiceNow + Okta + Microsoft 365
Privileged access change with approval
Privileged access is granted only after named approval, with every change recorded.
View use caseAmazon Web Services + ServiceNow + Jira
Cloud incident to controlled remediation
Cloud events become incidents and engineering tasks, and remediation runs only when approved.
View use caseServiceNow + GitHub + ArgoCD
Configuration change across controlled environments
Configuration changes deploy only after approval, with checks and deployment events tied to the change record.
View use caseWorkday + Okta + Microsoft 365
Secure collaboration onboarding
New staff receive only the identity groups and collaboration spaces their role allows, after approval.
View use caseRelevant capabilities
Where defense deployments usually start.
Sentinel typically anchors the security operations use case; the workflow platform and Sovereign AI extend it into mission support and logistics.
Nexus Sentinel
Sovereign SIEM and SOAR for correlation, detection and orchestrated response.
ExploreSovereign AI
Self-hosted models and knowledge bases with no external inference dependency.
ExploreDeployment
On-premises, private cloud, sovereign cloud and air-gapped deployment modes.
ExploreGovernance and Audit
Identity, RBAC and a per-run execution record.
ExploreProcurement notes
Evaluation in a controlled environment.
Alignment language and evaluator access
Where a tender references a specific control framework, Nexus capabilities can be described as aligned with or mapping to those objectives. Nexus does not claim accreditation on the customer's behalf. Technical evaluators can review the architecture and a deployment in a representative environment before commitment; see technical assurance for how that process typically runs.
Architecture session
Describe the enclave, not just the workflow.
Tell us about the connectivity, classification boundaries and existing security tooling in the environment. We will walk through what deploys, what stays disconnected, and what evidence the deployment produces.