Engineered from the ground up for high-concurrency red team collaboration, Redis-backed multi-vector throttles, and Web Locks API cross-tab synchronization.
Click any component below to explore its data flow, security constraints, and backend specs.
Layer 2: Core API & Context Middleware
Central API gateway parsing global organization headers, validating stateless JWT signatures, and orchestrating permission checks.
Eliminates 401 token refresh race conditions across multiple open browser tabs by requesting a single-flight exclusive lock before POSTing to `/auth/refresh/`.
Dedicated logical databases: DB 0 for model caches, DB 1 for rate-limiting counters & MFA nonces, and DB 2 for Celery background tasks with `volatile-ttl` policies.
Seamlessly handles context switching between User, Organization, and Superuser scopes via `X-Context-Type` and `X-Organization-ID` headers.
