Skip to content

The platform

Everything a maktab runs on.

Four portals, one ledger. Staff teach, guardians watch, students see their own progress, and anyone can verify a certificate — without an account, and without a single recitation leaving your mosque's control.

The whole mushaf, one grid.

Every one of the 114 surahs and 6,236 ayahs is catalogued and mapped to its juz, so a teacher marks memorisation, revision, and tajwīd review against the text itself rather than against a row in a spreadsheet. The class view is the same grid at a distance: one colour per state, thirty juz across the bottom.

  • Ayah-level status, not surah-level guesswork
  • A 30-juz heatmap for the whole class
  • Hifdh session logs kept against each student

Progress · Surah al-Baqarah

30 ajzāʾ

Ayah-level memory, not a spreadsheet.

And the parts nobody demos, that decide whether it is used.

Milestones and verified certificates

Juz and surah completions become printable certificates carrying an opaque code. Anyone can verify one; a revoked certificate reports as revoked rather than vanishing.

Smart scheduling with conflict detection

Recurring sessions, suggested times, and a warning when two classes want the same teacher — before the message goes out to parents.

At-risk analytics and learning paths

Attendance and progress signals surface the students drifting quietly, with a suggested next surah rather than only a red flag.

Roles, forum, and an audit log

Administrators, teachers, and teaching assistants scoped to their own students — with a record of who changed what.

Where it runs.

WebAny modern browser
DesktopmacOS today, Windows soon
MobileAndroid and iOS apps in preparation

All three keep working when the mosque WiFi does not: the local database is encrypted, edits queue, and sync resolves conflicts when the connection returns.

Begin your hifdh ledger.

Set up your mosque in an afternoon. Your first class can be on Mudrus by Maghrib.