Architecture (C4 Model)
This section documents the Noxys system using the C4 model by Simon Brown. C4 describes software architecture at four levels of zoom; we publish the three that are most useful to integrators, auditors, and contributors:
| Level | View | Audience | Page |
|---|---|---|---|
| 1 | System Context | Auditors, CISOs, integrators | Where Noxys sits in your IT landscape |
| 2 | Containers | Architects, DevOps, SREs | Deployable units and their relationships |
| 3 | Components — noxys-api | Backend engineers, reviewers | Inside the API service |
Note on notation. Diagrams use plain Mermaid flowcharts styled to evoke the C4 visual language (Person / System / Container / Component). The experimental
C4ContextMermaid block is intentionally avoided because support across Docusaurus, GitHub, and Obsidian renderers is still inconsistent. Plain Mermaid renders everywhere.
Related references
- Platform Architecture overview — narrative summary
- Developer Handbook — Architecture — bounded contexts and ownership
- Security Architecture — threat model and controls
- ADR registry — significant architectural decisions
Repository inventory
The diagrams below reference these repositories owned by noxys-eu:
| Repo | Role |
|---|---|
noxys-extension | MV3 browser extension (Chrome, Edge, Firefox, Safari) |
noxys-api | Go backend — policy, audit, catalog, multi-tenant control plane |
noxys-console | Next.js admin SaaS — IAM, policies, alerts, reporting |
noxys-presidio | Python sidecar — Tier 2 PII / Risk Signal detection |
noxys-ai-forge | Async Small Language Model service — Tier 3 detection |
noxys-vscode | VS Code extension — developer-facing controls |
noxys-pdf-renderer | Service that renders compliance reports and DPIA exports |
noxys-infra | Terraform + Ansible for VPS, staging, production |
noxys-doc | doc.noxys.cloud — this site |
noxys-website | noxys.eu marketing + ADR registry |