The operating system for educational institutions
Twenty-one modules on one family and staff database — enter a student once, and admissions, attendance, fees, the library and the gate all know them. Not a teaching tool. The everything-else.
The gate opens.
A walk-in visitor gets a numbered QR pass, printed at the desk. A refused entry does not need anyone to remember it — it opens a security incident on its own.
Every module reads the same family and staff database. There is no second roster to maintain — the library’s borrowers, the gate’s dispersal list, the fee books and the task boards are all the same people.
Pick a role. Filled screens are what that role can open — everything else returns a refusal, not a blank page.
Live means in the product today. Launching means built, switching on with the 1 October release. Planned carries no date — and we will not promise one. No roadmap theatre.
QR passes, parcel custody, dispersal to the right adult — and a campus-wide lockdown broadcast enforced server-side.
Catalogue with MARC import, circulation, holds and fines, RFID kiosk, reading programs and badges, comprehension quizzes. Most schools pay for this separately.
An enquiry pipeline with stages, entrance tests and document collection, principal approval, and admission payments — one flow.
Daily roll call, an absence follow-up queue, bus boarding — and gate-vs-classroom reconciliation that catches a child marked present who never entered.
Fee books and invoicing, a cashier dashboard, a scholarship and concession engine, bank accounts — with GST-aware documents launching.
Multi-stage processes with amount bands, escalation on stall, and 40+ gated actions — purchases, positions, devices, even settings changes.
Built for
Gate & dispersal, attendance with parent alerts, the library, fees — the whole K-12 day this page walks through.
Admissions pipelines, approvals and purchases, HR & recruitment, calendar and resource booking across departments and campuses.
Enquiry-to-enrolment, fee books with reminders, attendance, and one people database across every branch.
How to read our statuses. “Live” is in the product today, verified against the current build — safe to see in a demo. “Launching” exists in code and switches on with the 1 October release. “Planned” is direction, not a promise: anything dependent on a reader, a camera or a barrier, or still being designed, carries no date, because we will not commit to a date we do not control.
Six capabilities ship inside the modules — three live today, every call metered per school. The sensitive one never leaves your campus. How each one works →
Every support ticket gets an instant first response drafted from the product’s own context. Humans take over on escalation.
Quiz question drafts for any book — the librarian reviews before publishing — and written answers graded against a rubric, not just multiple choice.
Every recruitment call transcribed and analysed for sentiment and quality — processed on-premise, so audio never leaves the school’s control.
A central queue where an AI check confirms each day’s sessions and flags gate-vs-classroom disagreements.
Dashboards described as a spec and rendered live — the groundwork for asking for any report in plain language.
AI agents taking on routine admin across the assistant and integration seams — read-mostly at first.
A dedicated team for the development period, billed monthly. The whole table is here — there is nothing behind a sales call.
| Item | Basis | USD / month |
|---|---|---|
| Developer and CTO | Dedicated to your implementation | 1,200 |
| Quality assurance tester | Dedicated | 800 |
| Server hosting | Managed cloud, backups included | 250 |
| Committed monthly | the whole engagement | 2,250 |
| WhatsApp, SMS, email & AI | Billed as used, directly to you, at provider rates | as used |
The team costs the same at 400 students or 4,000.
Figures are arithmetic on the published USD ledger, shown in INR at indicative rates.
Committed monthly ≈ ₹1,98,000 — Prices exclude GST. Contracts are in USD; conversions are indicative. Compare the engagement to your current stack plus the hours spent stitching it, not to a licence alone.
of refused entries logged — the incident opens itself.
By construction · Gate →1database for family, staff, fees, library and the gate. No second rosters.
By construction · Family Database →40+actions gated through Approvals — nothing decided off the record.
By construction · Approvals →“The gate stopped being a register nobody read. A refused entry opens an incident on its own, and dispersal is checked against the collector list — not against memory.”
A demo configured with your roles and your loan rules — not a slideshow.