Schools I talked to were running grades in one system, attendance in another, fees in a spreadsheet, and parent communication over WhatsApp. schoolmasterhub is an attempt to put the core of that — grades, attendance, fees, and messaging — under one roof.
0. the idea
1. architecture
Stack:
- Node.js (Express) API
- Oracle APEX for internal school-admin tooling and reporting
The system is multi-tenant — one deployment serves several schools, each with its own students, staff, and data, fully isolated from the others.
2. features
What it does:
- Gradebook with a configurable grading scale per school
- Attendance tracking per class
- Fee tracking and payment status
- Parent / teacher messaging
- Auto-generated report cards
3. a challenge — multi-tenancy
The riskiest part of a shared, multi-school system is a query that forgets to filter by school and leaks one school's data into another's view. That's not a hypothetical bug, it's the one that matters most to get right.
Scope every query through a single helper that requires a tenant (school) id, rather than trusting every individual route to remember to filter. Make the unscoped query the one that's hard to write by accident, not the other way around.
4. the code
function forSchool(schoolId) {
return {
findStudents: (filter = {}) =>
Student.find({ ...filter, schoolId }),
findGrades: (filter = {}) =>
Grade.find({ ...filter, schoolId }),
};
}
const db = forSchool(req.user.schoolId);
const students = await db.findStudents({ classId });5. what i learned
The hard part of school software isn't CRUD, it's that 'a term' means something slightly different at every school — different grading scales, different fee schedules, different academic calendars. Getting the data model flexible enough to fit more than one school's idea of a term took more iteration than any single feature.
