BabyBrain
A marketplace connecting parents with children's activities and classes in Singapore. Two Vite single-page apps (a parent app and a vendor portal) share a single Next.js backend (API routes + webhooks) on top of Supabase, with GetStream for chat and Stripe for payments.
app/ — Next.js API routes, webhooks, and middlewarefrontends/parent/ — parent-facing Vite SPA (served at /app/)frontends/vendor/ — vendor portal Vite SPA (served at /vendor/)lib/, supabase/ — shared server helpers and database migrationsdocs/ — architecture notes
See docs/backend-architecture.md and docs/vendor-architecture.md for detail.
Documentation index
| Doc | Covers |
|---|
| docs/backend-architecture.md | Parent/backend data model, RLS, triggers, recommendations |
| docs/vendor-architecture.md | Vendor portal backend, roles, bookings/waitlist, attendance |
| docs/SETUP.md · docs/vendor-setup.md | First-time setup, env, Stripe/Stream/Resend wiring, API contract |
| docs/vendor-scraping.md | Apify-based vendor directory refresh (with WordPress fallback) |
| docs/OPERATIONS.md | Ops runbook, scheduled jobs, maintenance schedule, incident playbooks |
Messaging architecture
Chat runs on GetStream. There are three flows, all gated by Supabase auth, with every client minting its token from /api/vendor/chat/token:
| Flow | Parent UI | API route | Who's in the channel |
|---|
| 1:1 enquiry (personal query) | EnquiryChat.tsx | /api/vendor/chat/start | parent + provider staff |
| Class group chat | ClassGroupChat.tsx | /api/chat/class-group | every parent booked in the class + provider staff |
| Support | /support | /api/chat/token | parent + BabyBrain support |
The vendor never needs to open a channel explicitly — MessagesPage.tsx lists every channel the vendor is a member of, so both the 1:1 enquiry and the class group appear in its inbox automatically. Creating or joining the class group is gated to parents with a live booking (pending / confirmed / completed); the provider's active staff are added as members so the vendor is present to answer.
Codebase map (Graphify)
The repo is indexed into a queryable knowledge graph with Graphify — 1174 nodes · 2056 edges · 83 communities, built entirely from local AST parsing (no API calls). Outputs live in graphify-out/:
Rebuild and query it (offline, zero API cost):
export PATH="$HOME/.graphify-venv/bin:$PATH"
graphify update . # rebuild after code changes
graphify query "how does booking work" # navigate the repo by question
graphify explain "getStreamServerClient" # explain a symbol and its neighbours
Development
npm run dev # Next.js backend
npm --prefix frontends/parent run dev # parent SPA
npm --prefix frontends/vendor run dev # vendor SPA
