A multi-tenant school management platform — 100+ routed React pages with mocked data, a 58-module catalog, role-based access for 8 user types, and a session-rollover wizard.
Schulmate is a comprehensive school management platform designed as a multi-tenant SaaS product. The frontend is fully built with 100+ routed React pages using Vite, Tailwind CSS, shadcn/ui and Mock Service Worker for data simulation. It covers everything from student admissions and attendance to exam management, fee collection, transport tracking, library, hostel, payroll and AI-powered insights — organized into three tiered bundles (Essentials, Growth, Complete). The backend architecture is specified but not yet implemented.
In design 1 December 2025 · SYNIX

Schools manage students, fees, attendance, exams, staff and communications through a patchwork of paper registers, Excel sheets, WhatsApp groups and multiple disconnected apps. There is no single platform that covers the full school operation — and the ones that exist are either too expensive or too rigid for small and mid-size private schools.
Problems like this rarely announce themselves. They show up as Friday afternoons spent on spreadsheets, month-end rushes and “it's never been a priority” — right up until it is.
Who felt it
Small and mid-size private schools in India
The cost of leaving it
Multiple subscriptions, manual data entry, parent communication gaps and no single view of school operations.
Not a demo wrapped in a sales pitch — a working product, built end-to-end and operating in the client's business today.
We designed a modular multi-tenant platform with a unified module catalog of 58 toggleable features, organized into three bundles. The frontend is fully built with role-specific shells for parents, teachers, admins and platform owners — all running against Mock Service Worker for realistic demos. Feature flags work on two axes (per-tenant and per-bundle), the dynamic nav renders from the tenant's enabled modules, and every screen has both desktop DataGrid and mobile card layouts.
100+
Pages built
With mocked data and working navigation
The capabilities shipped with the first release — scoped, built and verified before anyone else touched it.
100+ routed React pages with role-specific shells (parent, teacher, admin, platform)
58-toggleable module catalog with per-tenant feature flags
Three tiered bundles: Essentials, Growth, Complete
Dynamic sidebar and navigation rendered from enabled modules API
Session-rollover wizard (7-step year-end promotion flow)
Student lifecycle: enquiry → eligibility → admission → active → promotion/exit (TC)
RBAC matrix across 8 roles and 12 permission domains
Dual-layout convention: desktop DataGrid + mobile info cards
Mock Service Worker for realistic demo without a backend
i18n ready (English + Hindi seeds, RTL-compatible)
Not screenshots of a design file — the actual screens the operator works with, and what each one's for.

Workspace sign-in with demo personas
100+ routed React pages with role-specific shells (parent, teacher, admin, platform)

Admin overview with growth pillars
58-toggleable module catalog with per-tenant feature flags

Student directory with lifecycle statuses
Three tiered bundles: Essentials, Growth, Complete
Four layers, top to bottom. Expand the diagram for the full view.
Everything in production, grouped by layer. No résumé padding — these are the tools that actually ran the system.
Languages
Frameworks
Frameworks
Data & storage
Data & storage
Infrastructure & deployment
Select any frame to open the fullscreen viewer. Left and right arrow keys move through the set.
This project shipped operations tooling rather than a public walkthrough — explore the catalogue for a similar system you can step through.
No public walkthrough yet
We keep some walks client-side. Ask us to walk you through it — or browse the interactive catalogue for a system you can already step inside.
The honest list. If the answer was easy, someone else would have shipped it already.
58 modules across 8 user roles could easily become 58 separate mini-apps. The dynamic nav engine — rendering sidebar and routes from the tenant's enabled modules — was the architectural decision that kept everything coherent. One registry, one data shape, zero hardcoded menus.
Indian school internet is unreliable. The student attendance module had to work offline-first with a local queue and auto-sync — not as a feature, but as a requirement for the product to be usable at all.
These are the numbers the client's operation actually produced — each one traceable to a specific change this system made.
100+
Pages built
With mocked data and working navigation
58
Module catalog
Organized into 3 tiered bundles
8
User roles
From SuperAdmin to Student
In business terms
One platform replacing paper registers, Excel sheets, WhatsApp groups and disconnected apps — built for real schools, not enterprises.
Same story, no jargon. Who it was for, what it moved, and what it put an end to.
Built for
Small and mid-size private schools in India
The result
One platform replacing paper registers, Excel sheets, WhatsApp groups and disconnected apps — built for real schools, not enterprises.
What it replaces
Multiple subscriptions, manual data entry, parent communication gaps and no single view of school operations.
This project crossed 2 delivery capabilities — Full-Stack Web Development, Business Process Automation.
See how we deliverThe fastest way to know if this can work for you is to sketch your version of it. Tell us what Schulmate would look like in your operation.
direct to synix.apps@gmail.com · no sales team · no cold-call follow-up