Our Combined Stack
Side-by-side comparison of what Fasai and Mix each bring to the table, plus where we overlap.
Fasai's Tools
- Claude Cowork (AI assistant)
- Claude Code Desktop
- Notion (databases, content, planning)
- GitHub Pages (static hosting)
- Vercel (deployment)
- n8n (automation / workflows)
- React / HTML / CSS / JS
Mix's Tools
- Claude Code CLI (native, 207 sessions, v2.1.76)
- VS Code + Claude Code + Copilot + ChatGPT extensions
- Node.js v24.12.0 + npm 11.6.2
- Python3 (basic packages)
- Git 2.39.5
- Google Cloud SDK 550.0.0 (Cloud Run, GCP)
- Express.js, PostgreSQL (Azure), Google Calendar API
- Jest 30.2.0, Vitest 4.1.0, ESLint 8.57.1, Prettier 3.7.4
- Playwright 1.58.2, Cypress 15.12.0
- Promptfoo 0.100.0 (LLM testing)
- Slack (notifications)
- GitHub Actions CI/CD
Shared / Overlapping
- Claude (both use Claude — Cowork vs Code)
- GitHub (both use repos)
- JavaScript / Node.js ecosystem
- React (Fasai uses React, Mix can use it)
- HTML / CSS / JS fundamentals
Recommended Stack for FJ App
Based on what both team members have access to and are comfortable with.
| Layer | Recommendation | Why |
|---|---|---|
| Frontend | Next.js (React) + Tailwind CSS | Fasai knows React, Mix knows Node.js. Next.js gives SSR + API routes. Tailwind for rapid UI. |
| Backend / API | Next.js API Routes or Express.js | API routes built into Next.js. Express as fallback if needed. |
| Database | PostgreSQL (Supabase free tier) | Mix has PostgreSQL experience. Supabase gives free hosting, auth, and a dashboard both can access. |
| ORM | Prisma |
Type-safe, great migrations, works with Supabase + Vercel. |
| Hosting | Vercel (frontend) + Supabase (DB) | Fasai already uses Vercel. Free tier sufficient for MVP. |
| Design / UI | shadcn/ui + Tailwind |
Beautiful components, copy-paste (no dependency), works with Next.js. |
| Testing | Jest + Playwright | Mix has both. Jest for unit, Playwright for E2E. |
| CI / CD | GitHub Actions | Mix already has experience. Auto-deploy to Vercel on push. |
| Auth | Supabase Auth or NextAuth.js | Built into Supabase. Handles email/password + social login. |
| Automation | n8n | Fasai's tool for workflows (reminders, notifications). |
Architecture Diagram
How the pieces fit together and who owns what.
Fasai's Zone
Mix's Zone
Shared / Handoff
External / User
User-Facing Flow
User (Senior)
→
Next.js Frontend
Vercel
→
Vercel
API Routes
Next.js / Express
→
Next.js / Express
Supabase
PostgreSQL
PostgreSQL
Admin / Trainer Flow
Trainer / Admin
→
Admin Dashboard
Next.js pages
→
Next.js pages
API Routes
Auth-protected
→
Auth-protected
Supabase
PostgreSQL
PostgreSQL
Automation Layer
n8n Automation
Fasai's workflows
→
Fasai's workflows
Notifications
Reminders
Reminders
Collaboration & Handoff
Fasai
Frontend, Content,
UX, Notion
→
Frontend, Content,
UX, Notion
GitHub
PRs & Code Review
←
PRs & Code Review
Mix
Backend, API,
DB, Deploy, Debug
Backend, API,
DB, Deploy, Debug
↓
Vercel
Preview deploys
Preview deploys
Supabase
Shared DB dashboard
Shared DB dashboard
Notion
Planning & content
Planning & content
Questions for Fasai
Decisions we need to make together before building. Let me know your preferences!
1Supabase vs Vercel Postgres?
Both work. Supabase has built-in auth + dashboard. Vercel Postgres is simpler but fewer features. Which do you prefer?
2shadcn/ui or other component library?
Do you have a preferred React UI library?
3Mobile-first or desktop-first?
Seniors will likely use phones. Should we prioritize mobile responsive?
4Video hosting?
Exercise videos need hosting. YouTube (free, easy embed) or Cloudinary/S3 (more control)?
5User auth method?
Email/password? LINE login (for Thai market)? Google sign-in?
6Notion as CMS?
Should Notion be the content source (via API) or do we build a separate admin panel?
7n8n hosting?
Is your n8n self-hosted or cloud? Can Mix access it for debugging?
8Domain name?
Do we have a domain for the FJ app?
9Design mockups?
Do you have Figma/wireframes, or should we design in code?
10Timeline?
When's the target launch for MVP?