Complianz system overview
At a glance
- Summary
- Mental model of the product: what is client-side, server-side and third-party.
- Objective
- Provide a mental map before going into API detail.
- Who this page is for
- Architects, tech leads, integrators.
- Prerequisites
- General web architecture concepts.
Application layers
Presentation, orchestration, persistence, observability — each layer has input/output contracts documented in the “Flows” and “API” pages.
Simplified diagram
[ Browser / App ]
│
▼ HTTPS
[ API Gateway ]
│
┌────┴────┐
▼ ▼
[ Services ] [ Files / logs ]
│
▼
[ Storage ]
Info
Detailed diagrams will be versioned (v1, v2) when several generations coexist.