Trust Center
Operational deployment paths, air-gapped architecture, and verifiable security signals for enterprise buyers and security architecture teams.
Air-gapped · Zero-telemetry by default
Prompts, tool arguments, and action payloads are evaluated inside your VPC, cluster, or on-prem boundary. The data plane does not require Nexus Cloud, third-party LLM APIs, or outbound product telemetry for governance decisions and UAR sealing.
Nexus Shield never exfiltrates prompt or action payload data to Nexus-operated systems.
Governance flow (customer boundary)
Every governed attempt follows the same isolated pipeline; Security Engines are optional supporting layers, not a substitute for action receipts.
┌────────────────── Customer infrastructure (air-gap capable) ──────────────────┐ │ │ │ Agent ──► Intent ──► Authority ──► Policy ──► Decision ──► Action ──► UAR │ │ (declare) (RBAC) (engine) (ALLOW/…) (execute) (SHA-256) │ │ │ │ ◄── No required egress to Nexus Cloud · optional local LLM only ──► │ └─────────────────────────────────────────────────────────────────────────────────┘
Deep dive: Architecture whitepaper · Data plane vs control plane
Deployment experience
Helm & Kubernetes
One helm upgrade --install deploys the Fast API governance plane, optional ML security engine, ingress, and health probes — suitable for EKS, AKS, GKE, and private clusters (GitOps / Operator-style lifecycle via Helm + ExternalSecrets).
Docker Compose (fast PoC)
Reference stack nexus-reference-app and docker-compose.nexus-reference.yml spin up the sidecar, mock MCP, and policy path in minutes for labs and light deployments.
Secret management
API keys and sensitive config bind to Kubernetes Secrets, HashiCorp Vault (External Secrets Operator), or AWS Secrets Manager via the same ESO pattern — never committed to git.
Helm values (externalSecrets) →Four security signals (low cost, high trust)
Data privacy commitment
Nexus Shield does not leak prompt or action payload content to Nexus-operated services. On-prem and air-gapped modes keep inspection and UAR sealing on your metal.
Transparent threat model
CISO-ready architecture, control-plane separation, and benchmark vs production proof lanes — see the architecture whitepaper.
architecture-whitepaper.md →Open-source credibility
Governance runtime (MIT) and evaluation harness (Apache 2.0) are source-available for audit; container images support standard SBOM tooling (Syft, Trivy) in your registry pipeline.
harness repository →PoC-first sandbox
Try policy and sandbox flows without API keys: production landing playground (/api/sandbox) and local reference stack on :8090.
Open playground →