Schools
Koshish gives a school cohort-level learning analytics: which topics a class or batch is weak in, refreshed daily, with institution-scoped data isolation, role-based access and a tamper-evident audit log. It is built on DPDP Act 2023 principles and designed for institutions that need provable data handling without adopting a full school ERP.
Last reviewed 2026-09-26
Capabilities
Performance, progress and comparison reports broken down by student, batch, subject and topic, with weak and strong areas identified for you.
InstitutionReportService — three report types, all implemented
Every query is scoped to the caller's institution membership, so one institute's students can never appear in another's reports.
requireAdminMembership guard on every institution service method
OWNER, ADMIN and STAFF roles with real server-side enforcement on every institution operation, not just hidden menu items.
InstitutionTeamService TEAM_ROLES + requireManagerMembership
Administrative actions are recorded in a hash-chained log — each entry references the one before it, so removal or alteration breaks the chain and a scheduled job detects it.
SHA-256 hash chain with a scheduled chain verifier
A consent ledger, self-service data export, an erasure path and a published grievance officer — the rights a school owes its students, actually implemented.
Consent ledger, export, erasure purge, grievance-officer page
Your logo and a colour theme applied to the portal students use, so the experience reads as your institution's rather than a third party's.
InstitutionBrandingService — logo upload + palette, applied in StudentPortal
Where it lives in the product
Fit
Schools running competitive-exam or senior-secondary batches
Institutions that must show provable data handling to a board or parents
Groups that want analytics without committing to a full ERP migration
Scope
We list these plainly because you will find out during evaluation anyway, and a vendor who names their limits is easier to trust than one who claims everything.
Attendance tracking — no attendance module exists in the product today.
Fee management or fee collection — not built.
Report-card generation — reports are exported by your team.
SSO, Google Workspace or classroom integrations — not built.
A teacher-facing mobile app — staff use the web portal; only the student app is on mobile.
A Hindi-language admin interface — the institution portal is English-only.
FAQ
Data is scoped to your institution, access is enforced by role on the server, administrative actions are recorded in a tamper-evident hash-chained log, and students and staff can export or request erasure of their data. We publish a grievance officer for data-principal requests. This is a real consent ledger and erasure path, not a policy page.
Yes. The audit log is hash-chained: each entry includes a digest of the previous one. If any entry were edited or removed, the chain would not verify, and a scheduled job checks it. That gives you something concrete to show a board or an auditor.
Staff use the web portal, which works on mobile browsers. Only the student-facing app is a native mobile app, and that is the side that benefits most from being offline-friendly.
No. There is no admissions, attendance, fees, timetable or payroll module. If you need those, you will still need an ERP — we would rather point you at the right tool than sell you a replacement for one we do not have.
Tell us your batch sizes and exam mix and we will scope the setup honestly, including what it will not cover.
Talk to our team