Company
Infoleen exists because schools deserve one system that works, in their language, at a price they were told up front.
Infoleen started from a pattern we kept seeing in schools across India, the Gulf and beyond: enormous effort spent operating software rather than running a school. A head of department exporting marks from one system to paste into another. An office administrator retyping the same enrolment list into four tools every July. A parent with three logins and no clear answer about their own child.
The tools weren't bad. They were separate — each one solving a real problem while creating a seam. And seams are where school data goes to die.
So we built a single platform where the student record is genuinely one record. Attendance, marks, assignments, report cards, library loans, canteen orders and safeguarding reports all attach to the same person, in the same database, under the same permission model. Not integrated. The same.
If your staff have to know which system a piece of information lives in, the software has already failed.
"Contact us for pricing" means the price depends on what the vendor thinks you can afford. Ours is on the website. A school board should be able to budget without a sales call.
Export it whenever you like, in open formats, with no ticket and no fee. Software that keeps customers by holding their history hostage isn't good enough to keep them any other way.
Right-to-left is a layout mode, not a stylesheet flip. If Arabic breaks when the report card renders, the feature was never finished.
Hiding a menu item is decoration. Every role and school boundary in Infoleen is enforced server-side, where a browser console can't reach it.
Our comparison page names the competitors who beat us and the features we don't have yet. You'd find out in month two anyway — better you hear it from us in week one.
We'd rather have twenty-one modules that work than forty that demo well. Anything still on the roadmap is labelled as roadmap, on every page of this site.
Security & data
You are trusting us with records about minors. We treat that as the highest-stakes part of the product, not a compliance checkbox at the end.
Every read and write is checked against role and school membership in server-side security rules, independently of what the interface allows. The UI is a convenience, never the control.
Users can only reach data for schools they're a member of. In a multi-school group, a campus administrator cannot read a sibling campus unless you grant it.
High-sensitivity modules such as the warehouse are gated in three independent layers, so a mistake in any one of them doesn't expose data.
Self-service edits are restricted to a short allow-list of a user's own fields. Nobody escalates their own role by editing their profile.
All traffic over TLS; data encrypted at rest by the underlying cloud platform, with managed backups.
You can export your school's data at any time and request full deletion when you leave. We don't retain your records to train anything.
About four weeks for a single campus: discovery, migration, training, then a parallel run through one assessment cycle before cutover. Multi-campus groups take longer, and we'll give you a dated plan rather than a range.
Yes. Students, staff, guardians, classes and historic results migrate from your current system's export, and it's covered by the onboarding fee. Send us a sample export before you commit and we'll tell you honestly what will and won't carry across.
Both. It's designed so a teacher can find their classes without a manual, but we still run role-based sessions — teachers, office staff, admins — and record them in your language, so next year's new joiners aren't dependent on somebody remembering.
Yes. Every role's interface is built mobile-first, because in most schools guardians and a good number of teachers never open a laptop. The app is built to tolerate intermittent connectivity rather than assume campus-wide wifi.
The curriculum structure is configurable rather than hard-coded, so CBSE, ICSE, state boards, Cambridge, IB and Saudi national curricula are all modelled the same way. School- scoped curriculum lists mean each campus only sees its own.
Yes — that's a first-class case, not a workaround. One account, multiple roles, multiple schools, switched from a dropdown, with permissions re-applied on every switch.
It's yours. Export it. We consider the bank a school asset that we happen to host, which is also why AI Studio drafts from your bank rather than replacing it.
A named contact, not a shared queue — during onboarding for every plan, and ongoing on Premium. Support is available in English and Arabic.
Yes. Registration details, tax documentation and references from existing schools are provided on request during procurement — just ask.
Bring your hardest requirement, your messiest data and your most sceptical head of department. That's a better demo than anything we'd script.