Why Masar

Built around the nursery day. Designed to grow with you.

See why Masar combines role-based experiences, connected records, adaptable operating settings and an early-years-first product design.

Masar Arabic sign-in experience
EnglishOne day.
One clear view.
العربيةيوم واحد.
صورة واضحة.
Five decisions that shape the product

Specific enough to fit. Connected enough to grow.

Masar’s difference is not one feature. It is the way the whole platform is designed around nursery work.

01

Configured around the operation

Centre settings, working preferences, records and practical workflows reflect how each nursery operates.

02

Arabic and English, properly supported

Both languages and right-to-left behaviour are part of supported portal, mobile, notification, report and document experiences.

03

Nursery-first

Care routines, observations, family handovers and pickup sit beside a wider education-ready foundation.

04

One connected ecosystem

Child records, classroom activity, communication, finance and reporting contribute to the same operational journey.

05

Human-centred by role

Managers receive oversight, teachers receive classroom tools and parents receive a child-scoped experience.

Trust is architectural

Access follows responsibility.

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.

  • Tenant data boundaries enforced at the database
  • Class scope available for teachers
  • Child scope for linked parents
  • Role and permission controls for sensitive areas
  • Audit records for consequential actions
These are product design controls, not a claim of external certification or legal compliance.
Designed for operational reality

Fit comes from practical choices, not a location label.

It appears in language direction, working preferences, the centre’s timezone, financial records and the payroll details teams actually need.

Arabic that changes the layout

Right-to-left behaviour is treated as part of the experience, not only translated copy.

The centre defines today

Operational dates follow the centre’s own timezone rather than a browser or remote server guess.

Practical finance context

Fees, receipts, salary records and applicable payroll exports belong to the same nursery context.

How our guides are prepared

Useful guidance, with a clear line between advice and product claims.

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.

  • Operational guidance is separated from claims about what Masar currently provides.
  • Product statements are checked against the documented capability and rollout context.
  • Local references are linked to their source; guides do not replace legal or regulatory advice.
Explore the guide library
A demo built around you

See Masar through your nursery’s real workflow.

We will focus on the people, handovers and priorities that matter to your team—not a generic feature tour.