School software should be boring, fast and honest

Schools do not need another dashboard. They need the fee register to be right, the attendance to take two minutes, and the parent to get the message. Everything we have built is in service of those three sentences.

What we believe

One system, not seven products

The usual way school software is sold is as a bundle of separate applications that share a logo and nothing else. The same child ends up in three databases, none of which agree, and the office spends its year reconciling them. ClassNet is a single system with a single student record. Admit a student and they exist in fees, attendance and the parent app the same instant, because there was only ever one record.

Your data is yours, and the database enforces it

Every school runs in its own isolated tenant. That isolation is not a filter in application code that a single missed line could bypass. It is enforced by the database on every query, for every table, by default. We built it that way because the alternative fails quietly, and a quiet failure in this particular thing is unforgivable.

Speed is a feature, and so is working offline

A teacher marking attendance in a corridor has one bar of signal and thirty seconds. If the app is slow or loses the submission, they will go back to paper and you will have bought nothing. The mobile app assumes the network will drop and retries on its own.

We would rather tell you what is not built

Online fee collection is not in the product yet. Payroll, timetabling and transport are not either. They are on the roadmap, not in the demo, and we will say so before you ask rather than after you have signed. A list of features that quietly includes things that do not work is the most expensive kind of dishonesty in this industry.

Who we are

ClassNet is built by Ironova Technologies, a two-person company in Rajkot, Gujarat. Two engineers, one product, and nothing in between you and the people who wrote the code. There is no sales team to route you through, no support script, and no account manager who has never opened the software. Ask about the fee module and the person who wrote it answers.

Being small also explains the product. Tenant isolation is enforced by the database rather than by application code, because two people cannot hand-audit every query. The mobile app retries on its own, because we will not be awake when a teacher loses signal mid-corridor. A small team either builds things that hold themselves up or it drowns. We build the first kind, and we say plainly which parts are not built yet.

We build for Indian schools specifically: the academic year, the fee structures, the grading schemes, the languages parents actually read, and the timezone every date in the system is calculated against.