· 03 · TuitionHub
project 3, the working out
SaaS productEvery centre gets its own subdomain.
A SaaS product of my own. Every centre gets its own subdomain and its own data, for classes, fees, materials and a calendar, and parents get in without an account.
- My role
- Full-stack build
- When
- 2026
- Context
- My own multi-tenant SaaS
- Sector
- Education
A separate tenant space per centre, served on its own subdomain.
Classes, schedules and a calendar view.
Fees tracked per student.
Course materials shared per class.
Excel import and export, for moving student and class data in bulk.
Token links that let a parent in without an account, sent over WhatsApp.
Scheduled jobs and automated backups running behind it.
An offline route, for when the connection drops mid-session.
What it is built on
Next.js
TypeScript
Supabase
Tailwind CSS
shadcn/ui- Recharts
Vercel
Where to look
A private system in daily use, so there is no public deployment and the repository is closed. Happy to walk through it.
More of it
10 more screens
The week's calendar, each class colour-coded, a cancelled one struck through
Classes, filtered by stream, subject and grade, each card showing enrolment and what it bills
Students, filtered by status, with the classes they attend and what each still owes
Outstanding fees per student, charged against paid, each row with a WhatsApp reminder
Reports: billed against collected by month, and billed by class
Course materials, grouped by grade and subject
Dashboard on a phone, in the dark theme
The week's classes on a phone, as a list rather than a grid
A student on a phone: balance, attendance, the fee ledger, and the parent link that needs no login
Centre settings on a phone, with the overflow menu open