Building an educational platform for Saudi Arabia — Madrasati, NOOR system, and Arabic LMS requirements explained

Working on an EdTech project targeting Saudi schools and the regulatory and technical landscape is more complex than most founders realise going in.

Madrasati is the baseline, not the competition: Madrasati is the MOE's official platform with 6+ million students. You cannot position a new platform as a Madrasati replacement for public schools. What you can do is complement it, or build for the private school segment where flexibility exists.

NOOR system integration: Noor (نور) is Saudi Arabia's central education management system — it handles school registration, student grades, academic records, and certificates. Saudi parents already expect academic visibility through NOOR-connected workflows. For private schools, NOOR compatibility is increasingly a procurement requirement. Your platform should either integrate with NOOR or mirror its data structure and visibility standards.

PDPL student data requirements: All student personal data must be handled under PDPL compliance. Practically this means KSA-based hosting, explicit parental consent workflows, and auditable data access logs. Not optional for any platform touching minors' academic records.

Arabic-first is not a translation job: Tashkeel (Arabic vowel diacritics) matters for younger learners. Right-to-left form logic, Arabic numeral options, and Arabic keyboard input need to be native — not overlaid on a left-to-right base.

Saudi AI curriculum is now relevant: SDAIA and MOE have been pushing AI literacy into curriculum. Platforms without MOE-aligned AI modules are already appearing outdated in procurement discussions.

Found this guide extremely useful when scoping the project: https://logiolegion.com/blogs/edtech-platform-development-saudi-arabia-moe-arabic-lms-guide-2026

Anyone else navigating the private school procurement cycle in KSA? The decision-making timeline feels very different from what I expected.