Hijri-native — not a bolt-on display layer
OS-level Hijri calendar primitives: term boundaries, Ramadan/Eid/Jummah modes, bilingual decision letters — not retrofittable.
What this primitive provides.
Hijri term boundaries
Term starts and ends defined in Hijri dates. Gregorian dual-display where helpful, but Hijri is canonical.
Ramadan mode
Shortened school day schedules, Jummah half-days, Iftar-aware events — all calendar-aware, not text labels.
Eid breaks
Eid al-Fitr and Eid al-Adha breaks scheduled on Hijri dates. Auto-adjusts as moon-sighting confirms.
Bilingual decision letters
Acceptance letters, financial aid offers, and report cards generated in English + Arabic from the same record.
Jummah-aware scheduling
Friday Jummah prayer integrated into the school day schedule. Early dismissal logic for boarding students.
Madares + TETCO data feed (Saudi)
Roadmap support for required Madares + TETCO regulatory data feeds. We feed Madares; we don't replace it.
One family record on one OS — this app reads + writes alongside:
Falcon Academy on this app.
Falcon Academy: Hijri-aware report cards + Ramadan-mode scheduling natively supported.
What schools ask about this app first.
Hijri-native vs Hijri-display?
Term boundaries, Ramadan / Eid / Jummah modes, and bilingual letters use Hijri as a first-class data type. Not a translation layer over Gregorian. Other vendors retrofit; we don't.
Moon-sighting confirmation for Eid?
Eid breaks auto-adjust when moon-sighting confirms. No manual reschedule each year.
Ramadan mode?
Shortened school day, Jummah half-days, Iftar-aware events — calendar primitives, not text labels.
Madares + TETCO data feed?
Required Madares + TETCO regulatory data feeds on the roadmap. We feed Madares; we don't replace it.
Run the TCO math against your current vendor.
Where this app matters most.
See Hijri Engine in action
30-minute walkthrough — focused on this app if you’d like, or the whole OS.
Get a demo →