Chat on WhatsApp
Back to projects
School Management SaaS homepage

Project Details

Education / LMS

School Management SaaS

school-management-web-ivory.vercel.app

Most schools in Bangladesh still manage students, classes, results and fees with spreadsheets and paper registers, and off-the-shelf software is usually single-school, expensive to host and hard to customize. I built a School Management SaaS where one platform serves many schools (tenants). Each school gets isolated data, its own users and roles, a branded dashboard, and a public website at /school/[slug]. The platform owner (Super Admin) manages every school, subscription plan and invoice from one control panel. The project is a pnpm monorepo with a NestJS 11 REST API (/api/v1), a Next.js 15 frontend, and shared TypeScript packages for types, environment config and Zod validation schemas, backed by PostgreSQL (Prisma, 30+ models) and Redis. Core platform phases 0–4 are complete and billing is live; enrollment, attendance, exams and school fees are next on the roadmap. Repo: https://github.com/SR-Rony/school_management

Role

Full-Stack Developer (Architecture, Backend, Frontend, DevOps)

Duration

2025 – 2026

Next.jsReactNestJSTypeScriptPostgreSQLPrismaRedisTailwind CSSZodDockerSSLCommerzbKash

Product screens

Four different product surfaces — homepage, article, video news and category — across dark/light themes and Bangla/English, plus admin and auth screens from production.

SaaS homepage — English
SaaS homepage — Bangla
Super Admin — platform overview
Super Admin — schools & branding
School Admin — KPI dashboard
School Admin — student roster
Public school website (/school/demo-school)
Pricing plans
Features page
Admin sign in
School Admin registration

Key Features

Multi-tenant architecture — one platform, many schools, each with isolated data, slug, branding colors, campuses and settings

Five role-based portals: Super Admin, School Admin, Teacher, Student and Parent

Super Admin control panel for platform stats, schools, plans, subscriptions and revenue

School Admin KPI dashboard with Recharts bar, line and pie charts

Phone + password login with secure HTTP-only session cookies and role-based portal redirects

Forgot / reset password flow with expiring tokens

Dynamic roles and permission catalog (e.g. students.view, academics.manage) with guards on every API endpoint

Permission-aware sidebar navigation and audit log for security-relevant actions

Academic years, terms, calendar, classes, sections, subjects and teacher assignments

Student CRUD, bulk account generation, teacher/parent listings and parent–student relationships

SaaS billing: monthly/yearly plans, subscription lifecycle, PDF invoices (PDFKit) and renewal reminders

Online payments via SSLCommerz and bKash, plus a mock provider for testing

Themeable public website per school with hero slider, notice ticker, facilities, teachers and contact sections

SaaS marketing site: Home, Features, Pricing, About, FAQ, Partner and Contact

Bangla / English dashboard, switchable at runtime and saved per user

pnpm monorepo with shared @sms/types, @sms/config and @sms/validation packages

Docker, Docker Compose and Nginx setup, with web and API deployed to Vercel

Problems & Solutions

Real production challenges faced while building this project — and how they were solved.

01

Problem

Many schools share one database, so a single missing filter could leak data between tenants.

Solution

Scoped users to schools through an access-scope model, resolved the school context on every request, and combined role + school scope + resource ownership in the API permission guards.

02

Problem

Hardcoded roles don't fit every school's staff structure.

Solution

Built a Role ↔ Permission ↔ User model with a permission catalog so school admins can create custom roles; API guards and frontend navigation read from the same permission set.

03

Problem

Keeping API contracts in sync between the NestJS backend and the Next.js frontend by hand is error-prone.

Solution

Moved shared types and Zod schemas into workspace packages, so a contract change breaks the build on both sides instead of failing at runtime.

04

Problem

Bangladeshi schools pay through local gateways, not Stripe.

Solution

Wrote a provider-agnostic payment gateway service with SSLCommerz and bKash adapters and a mock provider, tied into subscription invoices and payment status tracking.

05

Problem

Deploying a pnpm monorepo with a separate API and web app on Vercel.

Solution

Set up separate Vercel builds that compile shared workspace packages first, generate the Prisma client, and run prisma migrate deploy during the API build.

Outcomes

  • ▸Shipped a live multi-tenant SaaS at school-management-web-ivory.vercel.app with four demo schools
  • ▸Completed core platform phases 0–4 plus SaaS billing with SSLCommerz and bKash
  • ▸Designed 30+ Prisma models across platform, identity, academics, people, records and billing domains
  • ▸Delivered a fully bilingual Bangla/English experience across the marketing site and dashboards
  • ▸Open-sourced the codebase at github.com/SR-Rony/school_management

Want something similar?

I can help you design and ship scalable web or mobile products end-to-end — including news, media and content platforms.