We build software for the people who actually run an institution
Not for the person who signs the purchase order and never opens it again. For the counsellor working a queue at a fair, the teacher marking a register at the front of a room, and the registrar who has to produce four years of evidence in a fortnight.
What we build
One student record, and software that does something with it
Ivake is an education ERP for schools, colleges and universities. Admissions, academics, fees, placements, alumni and accreditation sit on a single student record that runs from a first enquiry to a graduate being asked for a referral.
Most institutions did not choose a disconnected setup. They bought admissions software one year, campus software another, and kept placements in a spreadsheet because nothing joined the two. Every seam between those systems is paid for in re-typing, and in the follow-up that never happened because it belonged to nobody.
The part we care most about is what the software does on its own. Storing a fee schedule is not difficult. Chasing the instalment, answering the enquiry at eleven at night, and checking whether the marksheet is genuine — that is the work an institution actually spends its day on, and it is the work we build for.
iVake Technologies Private Limited
4th Floor, Kailash Building, KG Marg
Connaught Place, New Delhi – 110001
India
Registered office. Written enquiries to hello@ivake.com.
Where we work
India, the Gulf, Southeast Asia and Africa. An institution’s records are held in its own region rather than pooled somewhere central, so residency follows the institution instead of the vendor.
Deep on Indian compliance
DigiLocker, APAAR and the Academic Bank of Credits, NAAC and NBA, AISHE returns, UPI — supported properly, not bolted on. Institutions outside India run the same platform without them.
What we believe
Four decisions that shaped the product
These are not values on a wall. Each one is visible in how the software behaves, and each one cost us something to hold to.
Software should do the work, not report on it
A dashboard telling a registrar that forty fee instalments are overdue has moved the problem, not solved it. Ivake chases them, and stops the moment one is paid. Every automated action is written to the audit trail with the actor named — including when the actor was Ivake.
A record is worth more than a module
We could sell more modules faster by shipping them as separate products. We do not, because the moment two systems hold their own copy of a student, somebody has to reconcile them — and that somebody is always the institution.
The people using it did not ask for it
Teachers and clerks inherit software chosen by somebody else. If marking a register takes longer than the paper one did, it will be filled in at the end of the week from memory, and the data will be fiction. Speed at the point of entry is a data-quality decision.
Say what it does, not what it might
Our own writing rule: name the verb and the object. “Checks documents against DigiLocker” is a claim you can hold us to. “AI-powered insights” is not one we would know how to keep.
What we publish
Writing that is useful even if you never buy anything
NEP, the Holistic Progress Card, APAAR and credits, binary NAAC accreditation, two board exams a year, and what the DPDP Act means for a school holding children’s records.
These are the changes institutions are being asked to absorb, usually with little explanation and no lead time. We write them up because we have to understand them to build for them, and a guide costs us nothing to share.
Where your data sits
In the region your institution is in, with access set by campus, department and role, and every read and change attributable. A hostel warden sees residents, not marks. Medical and financial records are restricted separately.
Consent is captured where the data is collected, with the purpose recorded alongside it — which is what the DPDP Act asks of a Data Fiduciary, and what we would want to see from any vendor holding records about our own children.
- Data resident in your own region
- Role-based access, audited on every change
- No advertising, no behavioural profiling of students
Book a demo
See Ivake running on your own data
Send us a sample before the call: a term of enquiries, a fee structure, or a class list. We load it and set up your programmes, so you see your own institution on screen rather than a demo account.
- 45 minutes, your data. Not a generic tour of features.
- Migration mapped on the call. We show exactly where your current records land.
- A written rollout plan within two working days, with phases, owners and dates.
- No pressure to switch everything at once. Most schools and colleges start with one department or one intake.