
Faineant — In-Home Beauty Marketplace
Two-sided marketplace connecting Chicago clients with beauty practitioners who travel to them. pnpm + Turborepo monorepo: Next.js 15 web, Expo React Native mobile, and 12 Deno edge functions for Stripe, Resend, and Google Calendar. No ORM and no app server — SQL migrations are the source of truth and invariant-heavy writes go through Postgres RPCs, with pgTAP proving them.
A Marketplace Where the Database Is the Source of Truth
Faineant connects clients with independent beauty practitioners who travel to them. Two-sided marketplaces are mostly a scheduling and money problem wearing a booking UI, and the architecture is shaped around that.
The deliberate omissions
There is no standalone application server and no ORM. SQL migrations are the source of truth; web and mobile talk to Postgres directly through Supabase, and any write with an invariant worth protecting—double-booking, payout math, availability windows—goes through a Postgres RPC instead of application code. The rule is that a migration, its pgTAP coverage, and the regenerated database types land in one commit. Fewer places to be wrong beats more layers to be wrong in.
Shape of the monorepo
- Web: Next.js 15 App Router with Tailwind and Radix UI, behind a launch gate that flips the site between pre-launch waitlist and full marketplace
- Mobile: Expo + React Native with Expo Router, sharing schemas and design tokens with web via a single
@faineant/sharedpackage - Edge: 12 Deno functions covering Stripe payments, Resend transactional email, Google Calendar sync, and ICS generation
- Verification: lint, typecheck, unit, Playwright e2e, pgTAP database tests, and
deno checkon every function
The brand is an editorial dark-first system with champagne accents, driven by shared design tokens rather than per-screen colors—so web and mobile can't drift apart visually.
My role: CTO and sole engineer — schema, RPCs, both clients, edge functions, payments, and the design system.