One System for a School, Built by Two Developers
Elevate ERP ships under the Omniflux name, written by 2 developers in Patna, Bihar. The mandate is narrow: replace the desktop packages, spreadsheets and disconnected point tools a school runs on with one system — and say plainly which parts are not built yet.
- Idea 2020, built from 2024
- 2 developers, Patna
- Your institution is the Data Fiduciary
- We do not sell personal data
Both data statements are commitments in writing rather than certifications. The Data Processing Agreement names your institution as Data Fiduciary and us as Data Processor, and the Privacy Policy states that we do not sell personal data. No regulator or auditor has assessed Elevate ERP against the DPDP Act 2023, and we do not claim otherwise.
School Software Shouldn't Feel Like a Penalty to Use
The software a school is offered is usually a desktop package from another decade, a stack of spreadsheets, and two or three point solutions that do not talk to each other. So the register gets typed once at the classroom door and again into a computer. Fee receipts live in one book and the student's ledger in another, and closing a term means reconciling the two by hand. Parents get told what happened when someone finds time to tell them.
We built Elevate ERP on modern cloud primitives: screens that update as the data changes rather than when somebody presses refresh, online fee collection through Razorpay with receipts posted straight against the student's ledger, a scannable UPI QR built from the VPA your school configures — the amount already filled in when it is shown at the counter — exam papers you lay out question by question, and an AI assistant that works inside the permissions of whoever is signed in.
Engineering Commitments
Our Core Principles
The non-negotiable guidelines that direct every line of code we write.
Educator-First Simplicity
The screens a teacher opens every day are built so the ordinary case costs nothing: the attendance register loads with the whole class already marked present, one letter key changes a single row, and one button changes all of them. We have not run usability studies, so we do not quote a training time.
Statutory Rigor
Nothing about your board is hardcoded into the structure: you define the classes, sections and subjects, and each exam paper carries its own blueprint. The report cards, fee ledgers and transport records an inspection asks for are then produced from the system instead of rebuilt by hand. Two limits, stated rather than discovered: the report card’s grade ladder is fixed at the CBSE A1-to-E cut-offs, and NEP’s 5+3+3+4 stages are not modelled. We do not certify your compliance and cannot.
The Same People Answer
Setup help comes from the 2 people who wrote the software. Grievances are answered within 48 hours; there is no support rota beyond that, and we would rather say so than promise one.
Why Spend An Hour And Your Eyesight On The Old Method, When The Thing That Replaces It Already Exists?
That question is the whole reason Elevate ERP exists. Not a market gap, not a business plan — a specific irritation at watching people spend their evenings on work that a computer should have finished before they got home.
Somebody reads a register aloud at the classroom door, then types the same names into a machine after school. Somebody totals a column of fee receipts by hand, finds it disagrees with the ledger by ₹200, and starts again from the top. Somebody rules up a mark sheet with a pen, works out each percentage on a calculator, and copies the grades across twice because the first copy is for the file. None of that is difficult work. It is just long, and it is done at the end of a day that was already long, by people who are tired, which is precisely when arithmetic errors get made and then trusted.
So we did not set out to modernise anything. We set out to delete that evening — to make the register type itself once, the receipt and the ledger be the same object rather than two objects that have to be reconciled, and the mark sheet arrive already added up. Everything else on this site is downstream of that one decision.
We are 2 people, and we are both still students. We mention that not as a disclaimer but because it explains the shape of the product: nobody here has ever sold enterprise software, so there was no incentive to build the demo well and the workflow badly. The parts a school touches every single day got the attention, and the parts that photograph nicely did not.
We wrote the modules and we wrote the AI layer, which are usually two different teams with a contract between them and a seam you can feel. Here the assistant reads the same documents the fee desk writes, inside the same permissions as the person signed in, because the same two people built both sides and never had a reason to put a boundary there.
What we are not going to do is dress that up. There is no heritage here, no head office and no partner network — the roster below is the entire company, and the rest of this page is the plainest account of it we can write.
Two People, And This Is What It Adds Up To
These are not marketing figures. They are counts of rows in the feature index this site is built from, and each row in it names the file and line it was checked against — so every number below is one you can go and verify rather than one you have to take from us.
The same index holds 15 further entries that no page on this site prints. They are things the code appears to do that we have not finished checking well enough to sell, and they stay recorded so the gap is visible to us and re-checkable by anyone else. Four of them are modules our own plan list is willing to sell, which is the sort of thing an index like this exists to catch. The published list is on the features page, marked line by line for which of the two states each capability is in.
Two People, Both Named
There is no sales team, no support rota and no partner network. Elevate ERP is written by the 2 people listed here, working from Patna, Bihar. Omniflux Team is the operator of record — the named human on the grievance channel and the data-protection contact — and answers within 48 hours. Both are students, which is the least conventional thing about this product and the fact we are least willing to hide.
There is no incorporated company behind it either: Omniflux. We state that here rather than let a school discover it during procurement.
- AyushmanCo-founder — product, platform & AI
- Architecture, the AI layer, the data model and everything a school actually touches.
- ShivamanandCo-founder — engineering & AI
- Module engineering, the examination and academics stack, and AI systems.
You will not find a customer list, school logos, star ratings or a partner directory on this site, because there is no verified customer base to publish yet. When a school agrees to be named it will appear on Customers under its own name, and not before.
Omniflux Is The Workshop. Elevate ERP Is What Left It First.
Omniflux is the name the two of us build under, and Elevate ERP is the first thing that has left it. It is deliberately not the only thing we intend to build. The reason a parent brand exists at all is that the problem we started on — a school retyping the same register into a second system — is one instance of a much more common one, and the tools we had to write to solve it here are not specific to schools.
We are not going to name the next one, put a date on it, or list features for something you cannot open today. A roadmap you cannot hold us to is worth less than this sentence: everything described anywhere on this site is software that exists, and when the second product is real it will be announced the same way — after it works, under its own name, with the same note about what it does not do yet. Until then, Elevate ERP has our whole attention.
Set your institution up on Elevate ERP
Start on the free plan for up to 250 students. Paid plans begin at ₹1499 per month, billed to the institution.
A walkthrough is 30 minutes with Ayushman or Shivamanand — the people who wrote the software. There is no sales team to hand you on to.