Multi-tenant SaaS for coaching institutes
An institute operating system — students, batches, daily attendance and fee collection — isolated per organisation with a Docker and CI/CD pipeline that doubles as our cloud showcase.
Demo project: the business shown is fictional. We built this working product to show how we would solve this problem for a real client in this industry.
The problem
Coaching institutes in Indore still track students in Excel, attendance on paper and fees on WhatsApp. At 200 students that starts leaking money: missed collections, no-shows nobody noticed, and no single place a parent can be shown.
What we built
- A public marketing site with three subscription plans.
- A signed-in workspace: student roster, today’s attendance (present / absent) and monthly fees (due / paid).
- Multi-tenant isolation in Postgres. Every query is scoped by
coach_my_org(), so one institute can never see another’s data even if the application has a bug. - A production Dockerfile (deps → build → runner) and
docker composeso the same image can run on a VPS, Render or Fly. GitHub Actions lints, type-checks and builds on every push.
Try it
Open the live demo, sign in with the published demo owner account, mark attendance and collect a fee.
Taking it to production
Parent login, Razorpay fee links, multi-branch, and SMS/WhatsApp reminders. A first production version is typically 6 to 8 weeks.