Ecoleby JalsaX AI

The school office, in three logins.

Ecole is the school ERP we built and now run for a school in Hyderabad. A principal console that reports, an accounts console that issues numbered receipts, and a class teacher console that takes the register in one screen. Attendance, marks and fees sit in one ledger, and the rules are held by the database rather than by trust.

Book a demo Work out your price

Priced from ₹3,000 a month · one price for every console and every teacher

Three consoles: Principal, accounts, and a class teacher login for every class.
One ledger: Attendance, marks, fees and receipts against the same student record.
Built for India: Dates and cut-offs in Indian time, money and receipts in rupees.
From ₹3,000 a month: Priced on roll strength, not per login. GST at 18% on top.

Three people, three consoles

Nobody is handed a screen full of things that are not their job. What each role can do is set once, in the data, and every console follows from it.

Principal console

Sees everything. Writes nothing.

The whole school on one screen, and a way down into any class or any student without asking anyone to pull a report.

Active students, attendance marked today, fee collection this year and the recorded academic average, on one overview
Any class opened up: attendance trend, subject averages and where its fees stand
Any student found by part of a name or a student code, then their attendance, marks, fee ledger and contacts
A fee attention list that links straight to the student it names
Numbers that move on their own when a teacher marks a register or accounts takes a payment

Cannot: Change a single record. The read-only limit is set in the database, not in the screen.

Accounts console

Records money. Never edits it.

Fee collection with a receipt trail that survives an audit, because correcting a mistake leaves more behind than making one.

A student found by name or code, with class and section shown when two names match
This year's fee, what has been paid, what is outstanding and every receipt so far
A payment recorded as one transaction, with the receipt number generated by the server
A receipt printed or saved as PDF straight from the browser
A defaulters report, sortable, exported as CSV

Cannot: Delete or edit a payment. A wrong receipt is voided with a reason, and the void is itself a record.

Class teacher console

Opens on the roster, already present.

The console the school actually lives in every morning, built so the common case takes seconds and the rare case is still possible.

The full roster for the day, loaded with every student already marked present
One tap per absentee, and the whole register saved in a single submit
A saved date reopened and corrected, not started again
Marks entered only for exams that match this teacher's class and subject
Every score checked against the exam maximum before it is accepted

Cannot: Mark a class they do not teach, or date a register in the future or outside the school year.

What it looks like in use

Captures of the running consoles. The students, guardians and numbers in them are generated for demonstration, not a real child’s record.

The principal console's school overview. Across the top: active students, today's attendance, fees collected this year and the recorded academic average. Below, the annual fee collection register showing collected against outstanding, and the most recent examination with its average. — Principal console: the whole school on one screen.

One class opened in the principal console, showing students enrolled, attendance across all marked days, fees collected and the amount outstanding, with a daily attendance trend chart and the average by subject. — Any class, opened up.

One student, end to end.

A student's fee account in the accounts console, with controls to record a payment or correct a receipt, the annual fee, amount paid and balance due, and a fee ledger listing each receipt number, amount, payment mode, who recorded it and whether it is valid or voided. — Accounts: the ledger, with the voids kept.

The accounts console student search, listing student ID, name, class and section, roll number and guardian for each record, with a button to open the fee account. — Find a student by name or admission ID.

What Ecole will not let you do

Most school software is a list of what it can do. The part that matters to a school is the opposite list, because that is the one that decides what a bad afternoon looks like. These are enforced in the data itself, so they hold whichever screen is open.

01
A receipt cannot exist without its ledger row.
Recording a payment writes the receipt number, the ledger entry and the audit record together, or writes none of them. A failed or duplicated request cannot leave half a receipt behind.
02
A payment cannot be deleted or edited.
The ledger only ever grows. Corrections are made by voiding a receipt with a stated reason and issuing a new one, so the mistake and the fix are both still there a year later.
03
A teacher cannot mark a class they do not teach.
Attendance requires the class-teacher assignment. Marks require an exam that matches the teacher's own class and subject. Neither check can be skipped by opening a different page.
04
The principal cannot quietly change a number.
Read access only, granted at the database. A report can be looked at from the top of the school down to one student, and none of it can be edited on the way back up.
05
A signed-out visitor gets nothing at all.
No tables, no functions, no data. Access is resolved from the signed-in role every time, not from what the browser was last told.

How it goes live

You send the lists

Students with their classes and sections, the teacher for each class, and this year's fee structure. However you keep them today, including a stack of spreadsheets.

We set it up

Your own database, the year and its classes, every student loaded, and logins created for the principal, the accounts staff and each class teacher with their class attached.

Registers first, fees next

Teachers start with attendance, because it is the shortest habit to change. Fees move across at a term or month boundary, so the ledger opens on a balance everyone agrees with.

What is not in it yet

Staff accounts are created by us rather than by you, so a new class teacher in March is a message to us and not a screen you drive. There is no transport, library, hostel or parent-facing module. We would rather you read that here than find it out in month two.

Priced by how many students you have.

₹3,000 a month covers the first 500 students. Every further 500, or part of 500, adds ₹1,000 a month.

Students on your rolls

1,000

1005,000

Your monthly price

₹4,000/month

GST at 18%: ₹720
Payable each month: ₹4,720
Per student, per month: ₹4

One price for all three consoles and every teacher who needs one. We do not charge per login, and we take no share of the fees you collect.

Book a demo

Questions schools ask us

What will it cost for our school?

₹3,000 a month covers up to 500 students. Every further 500 students, or part of 500, adds ₹1,000 a month. A school of 1,000 pays ₹4,000 a month, a school of 1,500 pays ₹5,000. GST at 18% is charged on top.

Where does our school's data live?

In a database we set up for your school and nobody else. Demonstration data and real student records never share a project, which is the only arrangement we consider safe for a school.

Can one teacher see another class?

No. A teacher sees the students, registers, exams and marks inside their own assignments and nothing else. The limit is enforced in the database, so it holds no matter which page is open.

What happens when a receipt is issued wrongly?

It is voided with a reason and a correct one is issued. The original receipt, the void and the replacement all stay in the ledger, which is what an auditor is actually looking for.

Who creates the logins for our staff?

We do. There is no self-service staff console yet, so you send us the principal, the accounts staff and the class teacher for each class, and we set up the accounts and the class assignments.

What is not in it yet?

Staff accounts are created by us rather than by you. There is no transport, library, hostel or parent-facing module. We would rather say that now than at the demo.

Do we need to install anything?

No. It runs in a browser and the school signs in with the accounts we create. Receipts print through the browser's own print and save-as-PDF.

Can we see it before we decide?

Yes. Book a demo and we walk all three consoles with you on a call, on data that is generated rather than borrowed from another school.

Ecoleby JalsaX AI

Your office already runs on registers. Move it, one console at a time.

Send us your roll strength and we come back with your exact price and a time to walk all three consoles.

Book a demo

20 minutes · no obligation · on WhatsApp if you prefer

Book a demo of Ecole.

Tell us your roll strength and we come back with your exact price and a time to walk all three consoles. Or email info@jalsax.com.

We walk the principal, accounts and teacher consoles, in that order
On generated data, never on another school's records
Reply within 24 hours, on WhatsApp