School ERP is a single platform that runs an entire school — and a solo project I’m building to learn how to engineer a production-grade, multi-tenant system end to end.

What it does

From one place, a school manages admissions and student records, academics (timetable, attendance, exams, report cards), fees and accounts, HR and payroll, inventory, transport, library, and hostel — with a data-scoped parent portal, and a companion mobile app on the way. It’s mobile-first, built for modest Android phones and patchy networks, and speaks English, Kannada, and Hindi from day one.

How it’s built

Multi-tenant. One deployment serves many schools, each isolated at the data layer on a shared database, with deny-by-default role-based access and per-row data-scoping.
Modular. Around fifteen departments, each an independently toggleable module — a school turns on only what it needs, controlled from a separate provider console.
Open source, no Docker. NestJS, Prisma, PostgreSQL, Redis/BullMQ, MinIO, and Mailpit, all run natively — no paid service required to develop the whole thing.

Status

In active development, and now deployed live on a fully open-source, $0 stack — the backend and database on a cloud VM behind automatic HTTPS, with both web consoles (the provider admin console and the school-facing app) served from the edge. The mobile app is still to come. The consoles linked above are live; demo credentials are available on request.