Enterprise ERP that runs an entire educational institution - attendance, fees, academics, and communication in one platform.
Schools, colleges, and coaching institutes were drowning in spreadsheets, WhatsApp groups, and disconnected tools. Attendance was disputed, fee follow-ups ate hours of admin time, and there was no single source of truth for operations.
Apps shipped in one monorepo
Apps in the monorepo
Core ERP modules
Go-live time
Deployment
How the work moved from problem to measurable result
Modelling the institution as a system
We designed Knwdle around the real structure of educational organisations: organisations, audiences (classes/batches/departments), members, content, and finance. Every module connects to this core model - making the data coherent across the entire platform.
Multi-tenant, multi-app architecture
We built a Turborepo monorepo with 5 apps sharing a single API: web admin, student/parent portal, mobile app, platform admin, and the Express/Prisma backend. Complete data isolation between organisations with JWT auth and Zod-validated APIs.
Enterprise-grade modules, not just features
Each module - attendance, fees, timetables, academic content, announcements, and access control - was designed as a state machine. Explicit actions, auditable records, and no silent side effects. Built to be trusted by institutions managing thousands of students.
Inside the platform
"Knwdle needed more than a web app - it needed a complete institution operating system. The architecture decisions made at the start are what let us scale confidently today."