-
Their children, and nobody else’sOne login covers every child in the family. Attendance, homework, results, fees and certificates in one place.
-
Their own timetable and marksTimetable, assignments, internal assessment, hall ticket and certificates. Nothing about anyone else.
-
Their classes, not the whole schoolAttendance, marks entry, their own timetable and today’s substitutions. Fee status is none of their business, so they cannot see it.
-
Money, across everyoneCollections, ageing, concessions and reconciliation. Access to financial detail is restricted and logged separately.
-
The whole institution, liveThe same records the staff are working in, with no export and no overnight job. The board pack stops needing two weeks of reconciliation.
-
Who did what, and whenSingle sign-on, role-based access and a full audit trail. One supplier to manage instead of six integrations.
One student record. Four modules. Nine stages of institutional work
Ivake is not a CRM bolted onto an ERP. It is one system. The enquiry, the application, the enrolment, the attendance mark, the fee receipt and the placement offer are all facts about the same person. Written once, read everywhere.
How it is built
The difference is the data model, not the feature list
Most institutional software falls apart because each product keeps its own copy of the student. Ivake has one identity instead. It moves through the lifecycle, picking up context at each stage, and is never created twice.
Every department works from the same record. Nothing is exported, and no department keeps its own copy.
One identity, many roles
A person is a lead, then an applicant, then a student, then an alumnus. It is the same record all the way through. Nothing is lost when they move from one stage to the next, and duplicates are merged rather than multiplied.
Institution structure as configuration
Campuses, schools, departments, programmes, batches, sections, electives, sessions and fee structures are all settings, not custom code. A group with eleven campuses runs one system with eleven contexts.
Permissions that match the org chart
A counsellor sees their own list. A head of department sees their department. A principal sees the campus, and trustees see the group. Every read and write is limited by role, and logged with a time and a name.
Automation as a first-class object
Your administrators set up the assignment rules, response timers, reminder schedules, eligibility checks and approval chains. Each one is versioned and visible, not buried in a developer's script.
Open at the edges
There is a REST API, webhooks and scheduled exports for everything Ivake stores. Your reporting tool, your website, your dialer and your accounting system all read and write through documented endpoints.
Reporting off live records
Every dashboard, accreditation report and management pack reads the same records your staff are working in. There is no overnight job that can be out of date by morning.
The lifecycle
Pick a stage and see what it creates
Nine stages, grouped into four modules, on one record. Every handover is a status change rather than an export, so nothing is typed twice and nothing is lost between departments.
Who sees what
One record. Six people. Six different views
Everybody works from the same student file, and nobody sees more than their job needs.
Security & data
Institutional data, handled the way an audit expects
You are holding children's records, money and academic credentials. Ivake is built for that responsibility, and for the questions your IT committee will ask.
Data residency in India
Production data and backups are hosted in Indian regions. Where a group requires a dedicated database or a private deployment, that is available.
Role-based access control
Permissions are set by campus, department, programme and role. Access to a student's financial or health information is restricted, and logged separately.
Full audit trail
Every create, update, approval, export and AI action is recorded with actor, timestamp and previous value. Marks and fee entries keep a complete revision history.
Encryption in transit and at rest
TLS on every connection, encrypted storage for documents and backups, and signed URLs with expiry for certificate and marksheet downloads.
Single sign-on
Google Workspace, Microsoft Entra ID and SAML. Staff accounts are provisioned and de-provisioned from your directory, so departures close access immediately.
Your data stays yours
Ask, and you get every record and document exported in open formats. That holds at any point, including after the contract ends. We do not hold data to keep customers.
Hosting regions, the DPDP Act position, our limits on AI access and what happens to your data if you leave are all set out in full. Read the security page
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.