Built for Indian institutions
Not a global product with an India checkbox.
Rupees in paise, boards that are not all the same, a payments stack that actually clears through Indian rails, and a privacy law with a specific exemption for children's data that a vendor does not get to inherit. Every one of these shaped a real decision in the code, not a line in a brochure.
DPDP Act 2023 posture
We are a Data Processor, and act like one.
Under the DPDP Act, your institution is the Data Fiduciary and holds the Fourth Schedule exemption for processing children's data. That exemption does not travel to the vendor — NexusGrade is the Data Processor, and the code enforces the boundary rather than a policy document promising it. We never process child data for our own purposes: no cross-tenant benchmarking, no model training on it, no analytics on minors.
Built as a module, not a promise
- Consent capture at the point of collection, scoped to what is actually being collected.
- Rights requests — access, correction, deletion — as a real workflow a parent or student can start themselves.
- Retention schedules and legal holds enforced automatically, so a deletion request cannot destroy a record you are required to keep.
- Breach workflow with the notification obligations the Act actually specifies, not a generic incident template.
Boards & regulators
Configured side by side, not chosen once at setup.
CBSE, ICSE, state boards, IB and university grading and credit structures run alongside each other in the same tenant — a group with a CBSE school and an IB campus does not need two separate systems that happen to share a login page.
Configurable for CBSE, ICSE, state boards, IB, NEP 2020 credit structures, UGC and AICTE reporting, NAAC/NBA cycles, autonomous colleges, deemed and state universities.
UPI & Razorpay
Payments that clear through Indian rails
Cards and UPI settle through Razorpay; the settlement report reconciles itself against the bank file, so a fee office is not matching two spreadsheets by hand at month end. Cash, cheque and DD collection at the counter never depends on the gateway being up — they post straight to the ledger and reconcile once the settlement report is back.
Multi-campus
One roster, many campuses
One fee head, one staff roster, one examinations authority — many campuses, each with its own timetable and registers. Multi-tenant is not a later migration here: every table already carries an institution boundary, which is what makes a group's shared roster and campus-local schedule both work at once.
Multilingual data
A guardian's name is not always spelled in one script.
Names, addresses and notices are stored and displayed the way an Indian household actually writes them — a student record that holds a name in more than one script does not have to pick one and lose the other. The parent and student portal ships in English and Hindi today, and notifications go out in the guardian's own preferred language rather than whichever one the office typed in.
See how the same posture shows up in every module.
See all modules