Mirror

Social virtual try-on for real shopping: a Chrome extension (side panel) and a small Next.js web companion, plus FastAPI on Railway and Supabase (Postgres, Auth, Storage, Realtime).

Features

Most people do not buy a jacket because the packshot is perfect. They buy because they saw it on someone. Influencers and celebrities normalize a cut or a brand. Screenshots and “where did she get that” threads are the funnel; storefronts still behave like catalogs. Mirror puts two proofs next to each other on the product page: real people wearing the item or something like it (our Worn by strip from Mirror posts and the wider web), and virtual try-on on your body from reference photos you approve in the web app first. Add fit score against what you already own, optional editorial stills you can share, and Feed / Circle so people you trust can react before you pay.

Components

Surface	Role
Extension	Shop any PDP: Worn by, try-on, editorial (when enabled), fit score, feed, circle
Web app	Sign-in, biometric consent, reference uploads, closet, feed, settings
Backend	FastAPI API plus workers for try-on, reverse search, fit score, editorial, video, etc.

Technical Architecture

Clients talk to Supabase (auth, Postgres, storage, realtime) with the anon key and JWT. They call mirror-api over HTTPS for orchestration (try-on submit, reverse search, fit score, closet saves, etc.). Slow work is written as rows in Postgres; workers poll or subscribe and call external APIs (try-on provider, Gemini, SerpAPI, Apify, etc.). Production web is commonly on Vercel; API and workers on Railway (same Docker image from apps/backend, different start commands).

flowchart TB
  subgraph clients [Clients]
    ext[Chrome extension]
    web[Next.js web app]
    sdk["@mirror/sdk-js"]
  end
  subgraph railway [Railway apps_backend]
    api[mirror-api]
    wTryon[mirror-tryon-worker]
    wAvatar[mirror-avatar-worker]
    wCloset[mirror-closet-enrichment-worker]
    wFit[mirror-fit-score-worker]
    wRev[mirror-reverse-search-worker]
    wEdit[mirror-tryon-editorial-worker]
    wVid[mirror-tryon-video-worker]
  end
  sb[(Supabase Postgres Auth Storage Realtime)]
  ext --> sdk
  web --> sdk
  ext -->|JWT and REST| api
  ext -->|session| sb
  web -->|SSR and client| sb
  web -->|REST| api
  api -->|service role jobs reads| sb
  wTryon --> sb
  wAvatar --> sb
  wCloset --> sb
  wFit --> sb
  wRev --> sb
  wEdit --> sb
  wVid --> sb

Loading

Worker entry points live in apps/backend/pyproject.toml under [project.scripts]. Railway config-as-code examples: apps/backend/railway.toml (API), railway.tryon-worker.toml, railway.avatar-worker.toml, railway.reverse-search-worker.toml, railway.tryon-editorial-worker.toml, railway.tryon-video-worker.toml. Fit-score and closet-enrichment workers use the same image; set start command in the dashboard to mirror-fit-score-worker / mirror-closet-enrichment-worker if you split them out.

Screenshots

Sources under assets/.

Web app

My Closet: tried, saved, and owned items with fit scores.

Chrome extension

Side panel on a retailer PDP (development build).

Worn by — Mirror posts plus matches from the wider web (e.g. TikTok, Pinterest, Instagram) when composite search is configured.

Try-on — Avatar, top, bottom slots; Regenerate and Editorial shot.

Editorial shot — Stylized full-frame try-on result.

Circle — Product-scoped circle score and posts on this item.

Repository structure

Path	Description
apps/web	Next.js 14 App Router
apps/extension-wxt	Chrome MV3 extension (WXT + React)
apps/backend	FastAPI + workers (uv)
packages/sdk-js	Shared TypeScript client helpers
supabase/	Migrations, seed, local config

Extension overview: apps/extension-wxt/README.md. End-user extension flow: apps/extension-wxt/OVERVIEW.md.

Prerequisites

• Node 20+, pnpm 9
• Python 3.12 + uv
• Supabase CLI for local DB

Quick start

1. Copy env templates in each app (see apps/*/.env.example when present) and set Supabase URL/keys.
2. Database: hosted — from repo root supabase login, supabase link --project-ref <id>, supabase db push. Local only — supabase start then supabase db reset. IDE Supabase plugins do not replace db push for repo migrations.
3. pnpm install then pnpm dev:web or pnpm dev:extension.
4. Backend: cd apps/backend && uv sync && uv run mirror-api (see apps/backend/README.md).

Production deploys typically use Vercel for the web app and Railway for mirror-api and workers; configure env vars on each service and keep apps/backend root directory consistent across Railway services.

Demo friend seed SQL template: scripts/seed-demo-friends.sql.

Demo friends (H12)

Replace UUID placeholders in the seed SQL after you create matching Auth users, then run against your project as appropriate for your environment.