School Management System in Morocco

We support the workflow, not yet a live API. Every student record carries the Code Massar (CNE), and our class-list exports use the column structure that schools upload to Massar. A direct API sync is on the public roadmap and depends on Ministere AREF authorisation, which is not granted to every vendor. We would rather be honest about that than over-promise: today, you import and export, you do not push live.

Both are production-grade. The French UI has been used by francophone schools for over a decade, and the Arabic UI runs right-to-left across forms, bulletins, and parent emails. Where translation gaps exist, they tend to be in niche admin labels rather than parent- or teacher-facing screens; schools can override any label themselves. Tamazight is not a full UI language yet, although you can store Tamazight school names and addresses.

Yes. You can run a French calendrier scolaire (September to July with the standard vacation cuts), evaluation par competences for cycle 3, and bulletins in the French format, while keeping a parallel Moroccan reporting view for the local authorities. Schools in the AEFE network typically run two reporting layers; OpenEduCat handles both from a single tenant.

Three options. Self-host on a Moroccan provider (for example a Casablanca or Tangier datacentre) for full data sovereignty. Self-host on a European cloud region (Paris or Frankfurt) for AEFE schools that prefer EU GDPR alignment. Or use OpenEduCat managed cloud with an EU region. We do not force a single region and we do not move data without written consent.

Community Edition is free to self-host; budget for a small Moroccan VPS (around 3,000-6,000 MAD per year) and a part-time IT contact. Enterprise plans for 500 students typically land in the 25,000-60,000 MAD per year range depending on modules and support level, before any one-time migration help. We will quote the exact figure after a discovery call; what you see above is honest market range, not a teaser.