Students and groups
A student card holds the course, group, room, payments and issued textbooks. Moving a student between groups or branches takes two clicks and keeps the history.
Kyrgyz Republic · schools, lyceums, learning centres
CRM for educational institutions
AuniEdu brings a learning centre into one system: students and groups, branches, payments and cash shifts, textbooks, staff permissions and an audit log. It runs in the browser — nothing to install.
Built, rolled out and supported by Aunimeda, a software company in Bishkek.
Students live in notebooks
Every administrator keeps group lists their own way, and the question “who moved to another group in March” is answered only from memory.
Money lives in spreadsheets
Payments, discounts and refunds sit in several files. Closing the day and finding out who granted a discount, and why, is manual work.
Textbooks live “somewhere”
Books are handed out of a cupboard with no record: stock is known roughly, and who never returned a textbook surfaces a year later.
What is inside
Eight modules — eight desks of a school
Not a general-purpose CRM you have to bend into shape, but a system built for a learning centre: branches, courses, groups, cash shifts and textbook stock are in the data model from the start.
Branches
Several branches in one system, each with its own courses, groups and staff. The director sees all of them; a branch administrator sees only their own.
Payments and cash desk
Taking a payment split across the course and textbooks, printing a receipt (thermal printers included), refunds, and cash shifts with daily totals.
Approved discounts
A manager requests a discount, the director approves or rejects it. No verbal discounts: every one has an author, a reason and a decision.
Textbooks and stock
Stock by category and branch, issuing a textbook to a student, returns, movements between stores. You can see who is holding which book.
Roles and access
Cashier, manager, branch administrator, director — each with their own permissions. New accounts require approval, and sessions can be closed remotely.
Audit log
Who changed an amount, who deleted a student, who approved a discount. The log writes itself and answers the director's first question — who did this.
Reports and exports
Payments and student lists filtered by branch, course, group and period. Any selection exports to a spreadsheet for accounting.
How it works
Three ordinary days at a learning centre
A system is useful not for its feature list but for what happens at the front desk. Here are the three scenarios a working day is made of.
01
A parent pays for a course
- The cashier finds the student by surname and opens the payment form.
- The amount is split between the course and the textbooks automatically — nothing is calculated by hand.
- A receipt is printed, the textbook is written off in stock, and the payment shows up on the student card.
02
A student needs a discount
- The manager submits a discount request with a reason.
- The director sees the request and approves or rejects it.
- The decision and its author stay in the log — “who allowed this” is settled for good.
03
End of the working day
- The cashier closes the shift and the system totals every payment and refund of the day.
- The director opens branch results without calling the administrators.
- The rows that matter are exported to a spreadsheet for accounting.
Separate tenancy
Every institution gets its own address and its own database
crm.edu.kg is a platform, not a shared account. A school gets its own address with a certificate, a separate database and its own users. Institutions never share a table and never see each other's data.
- school.crm.edu.kgown database
- lyceum.crm.edu.kgown branches
- centre.crm.edu.kgown staff
- courses.crm.edu.kgown certificate
Institution data
Security you do not have to think about
The system holds children's personal data and parents' money. Security here is not a clause in a contract but the way sign-in, permissions and the log are built.
A separate database per school
Institutions do not share a table: each has its own address and its own database. One school's data is physically out of reach of another.
HTTPS only
A certificate, modern TLS and strict security headers. A plain HTTP connection is not possible.
The token is out of the page's reach
The session lives in an httpOnly cookie, not in browser memory, so injected scripts cannot read it. Sign-in can be tied to the school's Google account.
Password guessing is throttled
Sign-in attempts are rate-limited at the server level, and a director can terminate an employee's active sessions with one click.
Permissions instead of trust
An employee sees exactly their branch and their set of actions. New accounts do not work until the director approves them.
Everything is recorded
Changes to students, payments and users go into the log: who did what, and when.
Getting started
A rollout in four steps
A school is never left alone with new software: setup, data migration and training are on us, and afterwards we stay on support.
1
We map your processes
We look at how the school works today: branches, courses, who takes the money, how textbooks are tracked. That becomes the list of what we configure.
2
We configure the system
Branches, courses, groups, rooms and staff with permissions. We bring up an address in the form school.crm.edu.kg with a certificate.
3
We migrate your data
Students, groups and textbook stock move over from your spreadsheets. We verify the migration together with the school's administrators.
4
We train and support
We walk each desk through its work — cashier, manager, director. Then we stay available: updates, changes, backups.
Pricing
Quoted for your institution
Standard
Onboarding a school
Branches, courses, groups and roles configured on the existing system, your own address and data migration. A fit when your processes are typical.
Customised
Built around your processes
The same plus changes for your school: custom reports, additional roles, your own payment and instalment scheme.
Support
Support and development
Updates, backups, help for administrators and further development as the institution grows — on a monthly basis.
Three numbers are enough for a quote and a timeline: how many branches, how many students, and which modules you need. Send them over WhatsApp and we will come back with the figures.
FAQ
What directors usually ask
Does it fit a language school or an exam preparation centre?
Yes. The system is built around what every learning centre has: branches, courses, groups, students, payments and study materials. Exam preparation, language courses, children's schools, tutoring centres — the logic is the same.
Does anything have to be installed on the computers?
No. The system opens in a browser at your own address in the form school.crm.edu.kg — on the administrator's computer, the director's laptop, or a phone. Nothing to install or update locally.
Can students be imported from Excel or another program?
Yes, migration is part of the rollout. Send the export in any shape — we map it onto the system's structure and show you the result before go-live.
What if we need a module that does not exist yet?
We wrote the system ourselves rather than reselling a box, so it can be extended to fit the school: a new report, another role, your own payment scheme. Scope and timeline are estimated from your list.
Where is the school's data stored?
On a server operated by Aunimeda: role-based access, HTTPS connections and database backups as part of support. The data belongs to the school and can be exported at any time.
How much does it cost?
The price depends on the number of branches, the number of students and the set of modules. Send us those three numbers and we will come back with a quote and a timeline.
Who trains the staff?
We do. Training follows the desks: the cashier learns payments and shifts, the manager learns students and groups, the director learns reports, permissions and the log.
We will walk the system through your own case
Take your branch and your courses, and we will show how an ordinary day runs inside the system — from taking a payment to closing the shift.