Level 1 — System Context
The System Context view answers: who interacts with Noxys, and which external systems does Noxys depend on? It is intentionally free of internal detail.
Diagram
Actors
| Actor | Description | Interaction with Noxys |
|---|---|---|
| Employee | End user of generative-AI tools | Sends prompts via browser, IDE, or desktop integration |
| Customer Admin | CISO, IT operations, security ops | Configures policies, reviews alerts, manages users |
| DPO / Compliance | Data Protection Officer, compliance lead | Exports audit trail, DPIA, transparency reports |
| Customer SIEM | Sentinel, Splunk, Sekoia, Elastic, Crowdstrike | Receives streamed audit events |
| Customer IdP | Entra ID, Okta, Google Workspace | Authenticates console users (SSO), provisions accounts (SCIM) |
External systems
| System | Why it matters |
|---|---|
| AI providers (OpenAI, Anthropic, Google, Mistral, …) | The destinations Noxys mediates. Connections happen only after policy evaluation and Risk Signal sanitisation. |
| Stripe | Subscription billing for Pro / Enterprise tiers (see ADR-010). |
| Postmark / SES | Transactional email — invitations, password reset, alert digests. |
Trust boundaries
- Customer organisation — owns Employees, Admins, IdP, SIEM. Noxys is invited in via signed Terms + DPA.
- Noxys SaaS (EU) — the sovereign control plane runs in the EU (OVH /
Scaleway, see
noxys-infra). No customer data leaves the EU. - External AI providers — third parties; Noxys ensures only sanitised payloads cross this boundary, per the customer's policy.
Privacy-by-design promise
Even at this zoomed-out view, the architecture preserves a critical invariant: raw prompts are never persisted by Noxys. Detection happens inline; only a SHA-256 hash plus metadata is stored. The transparent boundary diagrammed above is therefore a policy boundary, not a data lake.