# Drape AI

> Try it on without trying it on — the engineering & product home for Drape AI.

## Docs

- [AWS system map](https://docs.drape.to/architecture/aws-system-map.md): Live AWS inventory for account 230790682930 — Route 53, Amplify, ALB, ECS, RDS, and what remains off-AWS — reconciled 2026-09-17.
- [Backend (MongoDB monolith)](https://docs.drape.to/architecture/backend.md): The MongoDB FastAPI monolith the mobile app runs on — routers and the API surface, the JWT auth model, rate limiting, and Stripe Connect payments.
- [Backend evolution: Mongo → Postgres](https://docs.drape.to/architecture/backend-evolution.md): 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.
- [Data model](https://docs.drape.to/architecture/data-model.md): 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](https://docs.drape.to/architecture/design-system.md): 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.
- [Mobile app (Expo)](https://docs.drape.to/architecture/frontend.md): The Expo Router mobile app — route groups, providers, state management, the design system, and how screens talk to the backend.
- [Infrastructure & hosting](https://docs.drape.to/architecture/infrastructure.md): 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.
- [Security & privacy model](https://docs.drape.to/architecture/security.md): Drape's security model — MongoDB JWT auth, BIPA biometric handling, the P0 rules that must never regress, and the authorization/RLS posture.
- [System overview](https://docs.drape.to/architecture/system-overview.md): The whole Drape system on one page — every surface, both backend generations, the data and AI services, and how a request flows.
- [Try-on pipeline](https://docs.drape.to/architecture/try-on-pipeline.md): The virtual try-on pipeline end to end — gate checks, model routing, garment masking, the Fashn and FLUX.2 paths, caching, and status polling.
- [Web surfaces](https://docs.drape.to/architecture/web-surfaces.md): The three Next.js web apps — marketing, the multi-tenant brand portal, and the admin dashboard — their routes, auth, and the subdomain model.
- [Dependency & unused-library audit](https://docs.drape.to/audit/dependencies.md): Grep-verified dependency audit — unused frontend packages, large unused backend stacks, the requirements.txt anti-patterns, and a prioritized cleanup plan.
- [Code audit](https://docs.drape.to/audit/overview.md): A senior-engineer read of the Drape codebase — what is healthy, what is debt, and where the cleanup leverage is.
- [Tech debt](https://docs.drape.to/audit/tech-debt.md): Prioritized tech debt — a live CORS finding, doc-vs-code drift, the dual-write body-photo pattern, dormant FLUX.2, silent pipeline failures, repo hygiene, and marketing video delivery (Bunny vs Mux).
- [ADR-XXXX — Short title](https://docs.drape.to/decisions/adr-template.md): Copy this file to start a new ADR. Number it sequentially and set the status.
- [ADR-0001 — Gated CI/CD deploy pipeline for the backend](https://docs.drape.to/decisions/gated-ci-cd-deploy-pipeline.md): Backend deploys are controlled by GitHub Actions via Render deploy hooks — staging auto-deploys when checks pass, production runs the same checks behind a manual approval gate. render.yaml stays autoDeploy:false.
- [ADR-0002 — Migrate the Postgres backend from Lightsail to ECS Fargate + RDS](https://docs.drape.to/decisions/lightsail-to-ecs-rds-migration.md): Migrate the Postgres web backend off the single Lightsail box onto ECS Fargate + ALB + RDS PostgreSQL 16, run two environments (dev + prod, no staging) on a lean ~$118/mo profile, fix the iOS-ATS-blocking TLS cert with ACM, and decommission Lightsail after a rollback window.
- [Drape AI](https://docs.drape.to/intro.md): What Drape AI is, the whole Drape-AI-LLC org on one page, every live link worth having, and how this documentation is organized.
- [Admin & automation](https://docs.drape.to/product/admin-tools.md): Internal admin tooling and the autonomous cron agents — the dashboard and management screens plus the background jobs that test and monitor the app.
- [Consumer app](https://docs.drape.to/product/consumer-app.md): The consumer app screen by screen — fit setup and consent, browsing, the try-on render experience, saved looks, and commerce.
- [Website widget & deep links](https://docs.drape.to/product/deep-links.md): Install the Shop on Drape website button and other deep links that send shoppers into the Drape app.
- [For brands](https://docs.drape.to/product/for-brands.md): The brand offering — what independent brands get on Drape, the plan tiers and pricing, how onboarding works, and the two portals brands operate through.
- [Marketing funnel](https://docs.drape.to/product/marketing-funnel.md): The drape.to acquisition funnel — how the marketing site routes shoppers to the waitlist and brands to the application, plus referral and product-share paths.
- [Product overview](https://docs.drape.to/product/overview.md): Drape as a product — the shopper value, the two-sided marketplace for independent brands, and where each audience is served.
- [Seller portal](https://docs.drape.to/product/seller-portal.md): The mobile seller/brand portal — how a brand manages its catalog, sees analytics and orders, handles billing, and installs the Shop on Drape website button from the app.
- [API & webhooks](https://docs.drape.to/product/webhooks.md): Configure Premium order webhooks — events, HMAC signatures, and how to verify payloads from Drape.
- [The repositories](https://docs.drape.to/repositories/overview.md): The five repositories in the Drape-AI-LLC org — what each owns, its stack, and where it deploys (Amplify org Git, ECS Postgres, Render Mongo).
- [Apple App Store](https://docs.drape.to/shipping/app-store.md): Apple App Store readiness — legal/privacy, the Sign in with Apple question, technical gates, and the biometric-AI review scrutiny to prepare for.
- [Backend deploys (Render Mongo + ECS Postgres)](https://docs.drape.to/shipping/backend-deploys.md): Two FastAPI pipelines — Mongo on Render (this page) and Postgres on ECS Fargate (develop auto-deploys dev; prod is workflow_dispatch).
- [Google Play](https://docs.drape.to/shipping/google-play.md): Google Play readiness — the near-zero starting point, the Android-specific blockers from android.package up, and the Data Safety form.
- [Shipping overview](https://docs.drape.to/shipping/overview.md): Where Drape stands on shipping — the verified build config and a single prioritized list of everything left to reach the App Store and Google Play.
- [Production cutover — api.drape.to → ECS/RDS (2026-08-31)](https://docs.drape.to/shipping/prod-cutover.md): Record of the 2026-08-31 production cutover — api.drape.to moved off the decommissioned Lightsail box onto the ECS Fargate + RDS prod stack, with a valid ACM cert, live-data restore, and end-to-end verification.
- [Web deploys (AWS Amplify)](https://docs.drape.to/shipping/web-deploys.md): How the web tier ships — AWS Amplify in us-east-1, org Git connections, Route 53 custom domains including docs.drape.to, and the branch-to-environment mapping.