About

An academic operating system for Indian institutions

AcadiFlow runs admissions, attendance, timetables, fees, homework, exams, report cards and certificates from one student record, with separate portals for administrators, teachers, parents and students.

Six decisions that shaped the product

Most school software differs in the details rather than the feature list. These are the details.

Board rules are data, not code

CBSE reports grades. ICSE does not award divisions. A state board may award one off an aggregate. A university runs semesters with SGPA and carries backlogs. Software that computes one and relabels it for the rest produces marksheets that are subtly wrong in a way nobody notices until a board audit. So the result format, the pass rule and the absence policy live in a rule set the result engine reads — and a school that needs a variation overrides it without waiting for a release.

The register has to be faster than paper

Attendance is the only thing in a school ERP that must be filled in every single day by people who are not administrators. If it takes longer than a minute it gets done in a paper book and typed up on Friday, and every number downstream is a week stale. That constraint shaped the teacher portal more than any other.

Access to a child's record is granted, never claimed

The common shortcut is self-registration against an admission number. An admission number is printed on every document the child carries, so it is not a credential. Guardians are invited by the school against a specific student, and a parent proposing a correction to their own details raises a change request an administrator approves.

A year-end operation you cannot preview is one you should not run

Promotion moves an entire school between sessions. It runs as a dry run first, showing exactly who is promoted, held back or leaving. The same instinct is why a timetable is versioned rather than mutated, and why a substitution is an override on a date rather than an edit to the schedule.

Money is displayed the way the bank prints it

Fee amounts render in the Indian digit grouping — 1,23,456 rather than 123,456 — and stay in Latin numerals even in the Bengali interface. The words are translated; the numbers stay legible next to the money they describe, because a parent reconciles a receipt against a bank statement.

A certificate exists to be verified by a stranger

An admissions office or an employer holding a PDF has no reason to trust it, which is why verification usually collapses into a phone call to the school. Every certificate carries a QR code resolving to a public page, on a URL with no language prefix so a printed code keeps working, and that page is never cached so revocation is immediate.

Who it is for

Schools following CBSE, CISCE, a state board or NIOS; coaching institutes and training centres; and colleges running semester programmes with SGPA, CGPA and backlog tracking. Trusts running several campuses administer them under one organisation.

It is built India-first, and that shows in the parts that are easy to get wrong elsewhere — the boards it ships with, the lakh digit grouping on a fee receipt, Hindi and Bengali interfaces, and Razorpay for online collection.

Decide with the details, not the feature list

Every school ERP lists the same modules. Ask us about the ones that differ — result rules, promotion, parent access — and compare those instead.