System overview
The whole Drape system on one page — every surface, both backend generations, the data and AI services, and how a request flows.
Backend evolution: Mongo → Postgres
The central architectural fact today — Drape is mid-migration from the MongoDB monolith to a modular Postgres backend, with the web tier already on Postgres and the mobile app still on Mongo.
Backend (MongoDB monolith)
The MongoDB FastAPI monolith the mobile app runs on — routers and the API surface, the JWT auth model, rate limiting, and Stripe Connect payments.
Web surfaces
The three Next.js web apps — marketing, the multi-tenant brand portal, and the admin dashboard — their routes, auth, and the subdomain model.
Mobile app (Expo)
The Expo Router mobile app — route groups, providers, state management, the design system, and how screens talk to the backend.
Try-on pipeline
The virtual try-on pipeline end to end — gate checks, model routing, garment masking, the Fashn and FLUX.2 paths, caching, and status polling.
Data model
The MongoDB data model — the core collections, their relationships, the body-photo fields on the user document, and why try-on jobs live in Redis.
Design system
Drape's shared design language — the dark-editorial token system (cream in dark, muted-green in light), where it's implemented, and the aspirational brief that does not match the code.
Security & privacy model
Drape's security model — MongoDB JWT auth, BIPA biometric handling, the P0 rules that must never regress, and the authorization/RLS posture.
Infrastructure & hosting
Current production hosting — Amplify plus Route 53 for web, ECS Fargate plus RDS for the Postgres API, Render only for the Mongo mobile backend. Verified 2026-09-17.
AWS system map
Live AWS inventory for account 230790682930 — Route 53, Amplify, ALB, ECS, RDS, and what remains off-AWS — reconciled 2026-09-17.