Case study

Chrome Micro-SaaS

One cloneable stack so a new browser product is auth, billing, and AI — then only unique logic.

Template real; first product In progress
  • Chrome MV3
  • TypeScript
  • React
  • Vite
  • Express
  • Firebase
  • Cashfree
  • Stripe (optional)
  • Vercel
MV3ExpressFirebaseBillAI

What exists

  • Engineering playbook + Cursor rules
  • Production starter template (Phases 1–8 foundation done as of 2026-08-15)
  • MV3 extension (TypeScript): popup login/logout, Chrome OAuth
  • Express backend: health, /me, auth middleware, Stripe + Cashfree (India default), AI /api/v1/ai/chat
  • Dashboard: six pages, Firebase Auth
  • First product: Review Response Generator — detect → generate → copy (in progress, not a launched store listing)

Architecture

Animated diagram of the system from documented facts.

MV3ExpressFirebaseBillAI

Stack

  • Chrome MV3
  • TypeScript
  • React
  • Vite
  • Express
  • Firebase
  • Cashfree
  • Stripe (optional)
  • Vercel

Status

Template real; first product In progress

Template is real. A KYC/template host is live. It is not a Chrome Web Store listing. Later product slots are placeholders — not shipped.