Mosque OS

A mosque holds a community's worship, its children's education, and their Qur'an. This is the operating system built to serve all three responsibly — in Arabic, German, and English.

GDPR by design
Every change on the record
العربية · Deutsch · English

One system

Everything the mosque already does, in one place

Arabic school and Hifz first, with the mosque operations that keep them running. Each area is a working part of this deployment, not a roadmap item.

Arabic school
Academic years, classes, attendance, homework, assessments and report cards.
Quran & Hifz
Circles, session logs, page-by-page progress, revision cycles and milestones.
Households & guardians
Families, children, guardianship, emergency and pickup contacts.
Fees & billing
Fee plans, invoices, payments and reconciliation — to the cent, never a rounded float.
Donations
Funds, donations and German tax receipts (Zuwendungsbestätigung).
Membership & staff
Members and dues, contracts, teaching assignments and background checks.

Arabic, German and English — all three, all the way down

Not a translated shell over an English product. Layout mirrors for Arabic, names carry both scripts, and every screen was built right-to-left first.

Arabic
المدرسة العربية وحلقات التحفيظ
German
Arabischschule und Quran-Unterricht
English
Arabic school and Quran circles

Trust

Children's data and money, treated as such

Privacy and auditability are product features here, not a policy page. Four of them are worth naming.

The mosque owns its data
One deployment, one database, one mosque. The mosque is the controller; nobody's records are pooled with another community's, and none of it is used to train anything.
Every sensitive change is on the record
Mutations write an audit entry in the same transaction as the change itself, so the log cannot disagree with what happened. Reads of safeguarding notes are recorded too.
You see your own rows, not the database
A teacher reaches the classes they are assigned to; a guardian reaches their own children. That boundary is enforced on the server for every request, not hidden in the interface.
Built around consent and erasure
Consent records, retention policies, data-subject requests and export or erasure are part of the system — not something bolted on when a family asks.

Built with the same care a mosque asks of everyone it serves

Every record here belongs to a family that trusted the mosque with it. Mosque OS is designed around that trust — audited, private by default, and built for the community it serves, not the other way around.