Guides / Getting started
Platform overview
The module map and the shared services every module builds on.
Shared foundation
Every module consumes the same core services rather than re-implementing them: identity & RBAC, the active context (organization / school / model / year), the centralized Payment Service, the AI platform, notifications and analytics.
Module map
| Area | Modules |
|---|---|
| Core | Auth, context, system, site (CMS), platform (departments, feature flags, global search) |
| SIS | Students, student lifecycle, guardians, emergency contacts, medical records |
| Academic | Classes, subjects, the timetable engine, pedagogy, grades, attendance, GPA |
| AI | 41 agents + LLM router, chat, automation, credits, AI learning generators |
| Finance | Fees, the centralized Payment Service, payroll, AI credits |
| Smart Transport | Fleet, drivers, vehicles, routes, stops, GPS, boarding, incidents, fuel, AI optimizer |
| Operations | Communication, HR/leave, analytics, extensibility |
Zero data duplication
Modules never copy each other's data. Transport reads students from the SIS; billing reads fees from Finance; the parent app reads grades from the academic module — all through well-defined, school-scoped APIs.