# Product overview

Drape is a **two-sided marketplace** built around one hard-to-fake moment: seeing a
real garment on your own body before you buy. Shoppers get try-on confidence;
independent brands get a try-on-enabled storefront and a discovery channel.

> *"Try on the culture."* — *"Check your fit before you commit."*
> *"See how clothing fits, drapes, and moves on your body before checkout."*

(The internal tagline "Try it on without trying it on" describes the same idea; the
live marketing voice is "Try on the culture.")

## Two audiences, one marketplace

```mermaid
graph TB
    subgraph "Shoppers"
        S1["Discover independent brands"]
        S2["Upload one body photo"]
        S3["Try on → fit / drape / movement"]
        S4["Checkout on Drape"]
    end
    subgraph "Brands"
        B1["Apply + get approved"]
        B2["Branded storefront on {slug}.drape.to"]
        B3["Catalog · try-on · analytics"]
        B4["In-store QR + website widget"]
    end
    S4 -->|marketplace fee| B3
    B2 --> S1
```

The marketplace framing is deliberate: *"Shoppers discover, try on, and checkout on
Drape — your storefront is where the sale happens."* Brands do not run a parallel
checkout elsewhere; the sale closes on Drape and the brand gets a branded surface,
Stripe Connect payouts, and analytics.

## The three value pillars

Drape markets itself on three pillars, and each maps to something real in the
architecture:

| Pillar | What backs it |
|---|---|
| **AI-powered try-on** | The [try-on pipeline](../architecture/try-on-pipeline.md) — Fashn.ai + fal.ai, garment masking, per-body caching |
| **Independent brands** | The [brand offering](./for-brands.md) — curated, culture-forward labels, not big-box retail |
| **Your data stays private** | The [security model](../architecture/security.md) — BIPA consent, private storage, server-side body-photo handling |

## Where each audience is served

- **Shoppers** use the [mobile app](./consumer-app.md) (iOS/Android, currently
  waitlist) and land via the [marketing funnel](./marketing-funnel.md) at
  drape.to.
- **Brands** apply and operate through the [brand offering](./for-brands.md) — a
  desktop portal (`brand.drape.to`) and a mobile brand portal, over the same
  backend.
- **Internal ops** run through the [admin tooling](./admin-tools.md) at
  admin.drape.to and the autonomous cron agents.

## What makes it hard

- **Biometric data.** A body photo is BIPA-regulated. Consent is enforced at the
  backend, storage is private, and the photo is never accepted from the client on
  a try-on request. See [security](../architecture/security.md).
- **AI that is right often, not always.** The pipeline routes between models and
  post-processes garments, and can still "succeed" with a wrong render. See the
  [try-on pipeline](../architecture/try-on-pipeline.md).
- **A platform mid-migration.** The web tier runs on Postgres while the mobile app
  is still on Mongo — see [backend evolution](../architecture/backend-evolution.md).
- **Solo operations.** One founder runs product, backend, four surfaces, and ops —
  so the system leans on monitoring, rate limits, and audit docs to stay safe.