Configured around the operation
Centre settings, working preferences, records and practical workflows reflect how each nursery operates.
See why Masar combines role-based experiences, connected records, adaptable operating settings and an early-years-first product design.

Masar’s difference is not one feature. It is the way the whole platform is designed around nursery work.
Centre settings, working preferences, records and practical workflows reflect how each nursery operates.
Both languages and right-to-left behaviour are part of supported portal, mobile, notification, report and document experiences.
Care routines, observations, family handovers and pickup sit beside a wider education-ready foundation.
Child records, classroom activity, communication, finance and reporting contribute to the same operational journey.
Managers receive oversight, teachers receive classroom tools and parents receive a child-scoped experience.
Masar is designed so each person works inside the scope they are responsible for. The access model sits underneath the interface, not only in the menu.
It appears in language direction, working preferences, the centre’s timezone, financial records and the payroll details teams actually need.
Right-to-left behaviour is treated as part of the experience, not only translated copy.
Operational dates follow the centre’s own timezone rather than a browser or remote server guess.
Fees, receipts, salary records and applicable payroll exports belong to the same nursery context.
The Masar editorial team writes from recurring nursery workflows and the product questions teams bring to demonstrations. We review each guide for clarity in English and Arabic, label preview or planned capabilities where relevant and update material when availability changes.
We will focus on the people, handovers and priorities that matter to your team—not a generic feature tour.