Overview
Ilmora is my current venture: AI-first school management software built for Pakistan. The problem in most schools is never one module — it's the gaps between them. A fee collected at the desk gets typed into a register, then a spreadsheet, then the accounts; every hop is a chance to be wrong, and by month end nobody knows which copy is right. Ilmora is one platform where that fee reaches the ledger without anybody re-typing it.
It's live at ilmora.cloud.
What it does
- Twenty modules, one set of books — admissions, student 360, attendance, fees and challans, real double-entry finance, payroll and HR, exams with hall/seat allocation and admit cards, generated clash-free timetables, transport with live GPS, hostel, library, discipline, communication, visitor management, NFC credentials, inspections, and multi-campus consolidation.
- AI that actually does something — "Ask Ilmora" answers how-to questions in place of a manual; a report analyst makes 200+ reports reachable in plain language ("Who hasn't paid this month?"); agentic actions fill the forms from a described outcome ("Generate October challans for the senior wing"); and automated alerts flag consecutive absences or collection falling behind before somebody has to notice.
- Permission-aware AI — the assistant inherits each user's permissions exactly; it cannot surface a record to somebody who couldn't open it themselves.
- A surface for every role — separate portals for owners, principals, teachers, accountants, and parents, plus native Android apps for the roles that don't work at a desk: teachers, parents, students, drivers, wardens.
- Built for how Pakistani schools actually run — offline-markable classroom registers reconciled against gate scans, NFC/biometric/QR attendance, a chart of accounts with fiscal-year close, and correction requests with approval trails instead of silent edits.
The stack
A Laravel API with dedicated queue workers, a scheduler, and Laravel Reverb for real-time WebSocket updates — all containerised with Docker alongside PostgreSQL and Redis. The frontend is Next.js. The architecture is built for the operational reality of a platform schools run their whole business on: background jobs that can't silently fail, real-time state, and accounting math that has to be right.
My role
Founder and engineer. I designed the domain model, built the API and frontend, and run the infrastructure. Building a real double-entry accounting engine inside a school platform teaches you that the product is 20% code and 80% understanding how the customer actually works — a fee voucher is easy; a fiscal-year close with opening balances adopted mid-year is the product.
Why it matters for your project
If you're building vertical SaaS — billing, multi-role permissions, real-time features, background processing, AI features that respect authorization — I'm doing all of it right now, in production, with my own money on the line.