One platform for your whole institution

Admissions, fees, attendance, examinations, payroll and parent communication in a single system, sharing one record of every student, staff member and payment.

Book a demo
Modules
20+
Modules
Features
150+
Features
Role portals
4
Role portals
Shared record
1
Shared record

A long module list is not the point. Sharing one record is.

Most institutions already own software for fees, another for attendance, a third for examinations, and a spreadsheet holding the parts none of them cover. Each one works. The cost is the space between them.

When a student is admitted at the front desk here, the fee ledger, the attendance register, the examination roll and the family portal all know about it immediately. Nobody exports a file. Nobody re-keys a name. Nobody reconciles two systems that disagree about who is enrolled.

That is what makes a term-end report take an afternoon instead of a fortnight, and it is the difference a module count on a brochure cannot convey.

Everything an institution runs on

Grouped by the part of the institution they serve. Each module works on its own and reads from the same underlying records.

Student information

Admissions, withdrawals, documents, ID cards and a complete academic history for every student.

Learn more

Fees and collection

Fee terms, heads, concessions, scholarships, family collection and automated defaulter reminders.

Learn more

Attendance

Student and staff attendance, biometric device support, leave management and absence notifications.

Learn more

Examinations

Exam setup, datesheets, grading schemes, remarks and result cards for any board.

Learn more

Staff and HR

Org chart, appraisals, recruitment, training records and compliance documents.

Learn more

Learning management

Live classes through Zoom or Meet, assignments, quizzes and course material.

Learn more

Payroll

Salary structures, allowances and deductions, generated from the attendance already recorded.

Accounting

Chart of accounts, vouchers, ledgers and period close built for institutional finance.

Transport

Routes, stops, vehicle and driver records, with route-linked fees that follow the student.

Hostel and inventory

Room allocation, hostel fees, mess management, stock control and asset registers.

Library

Cataloguing, issue and return, fines and reservations against the same student record.

Communication

Notices, circulars and direct messages to staff and families, with SMS and WhatsApp alerts.

And the rest of the platform

Appraisals, batches, curriculum planning, datesheets, downloads, front office and visitor logs, online classes, payment gateways, point of sale, professions, semesters, staff compliance, support desk, tags, timetable, to-do lists, trainings and multi-campus wings.

All included in the platform rather than sold as add-ons, and all reading the same records as the modules above.

Four portals, one record

Most school software gives you an admin panel and calls the parent experience a mobile app. Administrators, staff, students and families each get an interface built for what they actually do, all reading and writing the same underlying data.

  • Staff: attendance, curriculum, diary, live classes, leaves and their own payslip
  • Students: assignments, quizzes, results, timetable, library and transport
  • Families: everything the student sees, plus fee payment and multi-child switching
  • Administration: the full institution, with permissions deciding who sees what
See each portal in detail
Screenshot placeholder

Built for institutions that ask hard questions

What an evaluation team usually wants to confirm before a rollout.

Layered permissions

Permission to open something is checked on several independent levels rather than once, so a single misconfiguration does not expose data.

Sensitive fields stay hidden

Identity documents, personal contact numbers and bank details can be withheld from roles that do not need them, even on records those roles are allowed to open.

Reversible deletion

Records are retired rather than destroyed, so a mistaken deletion during a busy admissions week is recoverable.

Full audit trail

Every record carries who created it, who last changed it and when, so a disputed fee or mark has a history to check.

Multi-campus structure

Each campus runs its own admissions, staff and fees while the group sees consolidated reporting without anyone assembling a spreadsheet.

Mobile applications

Staff, student and family apps for the things people do away from a desk: attendance, notices, results and fee payment.

How institutions move across

Adoption is a project, not a download. This is what it actually involves.

  1. Structure first

    We set up your campuses, classes, sections, fee heads and grading schemes to match how the institution already works, rather than asking you to adapt to a default.

  2. Import and verify

    Student, staff and fee records come across from spreadsheets or your current system. We check the import with you before go live, because a silent mismatch in opening balances is expensive to unpick later.

  3. Train each role

    Administrators, teachers and office staff are trained on their own portal. Adoption fails when people are handed a system built for somebody else's job.

  4. Go live with support

    Most institutions start with the core modules and switch on transport, hostel, library or payroll once the routine has settled. Adding one later is a settings change, not a project.

Questions about the platform

How long does it take to get running?
Most institutions are operational within a few weeks. The work is mainly getting your existing records in and agreeing how fee structures, classes and permissions should be set up. We do that with you rather than handing over a login and a manual.
What happens to the data we already have?
Student, staff and fee records are imported from spreadsheets or your current system during setup, and we check the import with you before go live. A silent mismatch in opening balances is far more expensive to unpick in month three than to catch in week one.
Do we have to take every module?
No. Institutions typically start with the core - students, fees, attendance and examinations - and switch on transport, hostel, library or payroll when they are ready. The modules are already integrated, so adding one later is a settings change rather than a new project.
Will teachers and parents actually use it?
That is the reason for separate portals rather than one interface with everything hidden behind permissions. Staff see the teaching tasks they need, families see their own children. Adoption fails when people are asked to learn a system that was not built for their job.
How is access controlled?
Permissions are layered: what a role can open, what their plan includes, and what an individual is allowed to do within it. Sensitive fields such as identity documents and bank details can be masked from lower roles even on records they can otherwise see. Every record carries who created and last changed it, and deletions are reversible rather than destructive.
We run several campuses. Does that work?
Yes, and it is one of the reasons groups move here. Each campus runs its own admissions, staff and fees, while the group sees consolidated reporting across all of them without anyone assembling a spreadsheet.
What does it cost?
Pricing scales with the size of your institution, so a 200-student school is not paying what a multi-campus group pays. Published pricing is on the pricing page, and a demo includes a figure for your actual numbers.
Is the software available in other languages?
The interface is English today. Institutions across several countries run on it, but if your staff need to work in another language day to day, that is a genuine consideration rather than a preference we can configure away.

See it with your own data

A guided walkthrough using your classes, fee structure and staff setup, and a real price for your numbers.

Book a demo