MANEXA is not an ERP. It's your operating system.
An ERP is a finance-and-operations suite adapted for education, assembled from separately licensed modules. MANEXA is the system your institution runs on — schools, institutes and colleges — where academics, people, money and operations share one set of records, one hierarchy and one permission model.
What it looks like today.
Modules that were never one system
Finance, academics and HR arrive as separate modules with their own records, so the same student is entered more than once and the numbers never quite agree.
Licences that grow faster than the school
Another module, another department, another set of user seats — the price moves with the org chart instead of with the students you teach.
Control that stops at the report
Roles are a flat list and scope is a filter someone applied to a report, so who could see what is impossible to answer afterwards.
Hierarchy that actually shapes access.
Reporting relationships decide who sees, approves and escalates — not a flat list of users.
- 1Create the institution and its schools
- 2Bring in students, staff and fee structures
- 3Assign roles along the reporting structure
- 4Run academics, finance and operations day to day
- 5Review audited reports at month end
- L0Institution Adminowns the institution
- L1Principal / HOSleads a school
- L2HODleads a department
- L3Teachersreport to the HOD
- L4Class Teachersown a class
- L5Students & Parentssee only their own records
Everything needed, nothing bolted on.
One set of records
Academics, students, fees, HR, transport and communication write to the same records — nothing is entered twice and every number reconciles.
Priced per student
Per active student per month. Staff, teacher and parent accounts are included; there are no per-user or per-module add-ons.
Hierarchy-aware access
Roles follow the reporting structure and are enforced on the server for every read and write, not applied to a report afterwards.
Multi-campus by design
Schools and campuses under one institution, each with its own scope, modules and permissions — with strict isolation between institutions.
Audited as it happens
Every security and money action is written to an audit trail with the actor, the entity and the time.
Live the same day
Create the institution, get its MANEXA ID and start admitting students — no servers and no implementation project.
The difference, line by line.
“Traditional school ERP” describes the common pattern in that category — not any one product. Every MANEXA row is how the platform works today.
- What it isTraditional school ERP
A finance-and-operations suite adapted for education, assembled from modules that are licensed and installed separately.
MANEXAOne operating system for the institution — academics, people, money and operations on a single set of records, one hierarchy and one permission model.
- How you payTraditional school ERP
Per module and per user seat, quoted per deployment. Adding a module or a department means another licence.
MANEXAPer active student, per month. No per-user fees and no per-module add-ons — staff, teacher and parent accounts cost nothing.
- Who sees whatTraditional school ERP
Flat role lists, where scope is often just a filter applied to a report.
MANEXAHierarchy-aware roles enforced on the server for every read and write — a parent can only ever load their own child's records.
- More than one campusTraditional school ERP
A separate installation per school, or every school pooled together with no real boundary between them.
MANEXASchools and campuses sit under one institution, each with its own scope, modules and permissions — and strict isolation between institutions.
- When something changesTraditional school ERP
Reconstructed afterwards from reports; an edited payment or a changed role often leaves no trace.
MANEXAEvery security and money action is written to an audit trail as it happens, with the actor, the entity and the time.
- Getting startedTraditional school ERP
An implementation project — servers, consultants and a rollout measured in months.
MANEXASelf-serve: create the institution, get its MANEXA ID and start admitting students the same day.
- Parents and studentsTraditional school ERP
A bolt-on portal or a separate app, frequently priced per user.
MANEXABuilt in and ownership-scoped — parents and students see their own records only, and they are included in the plan.
Common questions.
No. "ERP" describes a finance-and-operations suite adapted for education, usually assembled from separately licensed modules. MANEXA is a management operating system: academics, people, money and operations run on one set of records, one hierarchy and one permission model. It covers the ground an ERP covers, but it is not built or priced like one.