A bilingual platform covering admissions, academics, finance, HR, transport and governance, which a single school can run on its own and a group can run across every branch from one place.
The same product at both ends of the market: one school switches on what it needs, a group adds branches without cloning anything, and five curricula run side by side in either.
A group adds branches without cloning anything, and decides who owns each setting.
It is usually built for one school and stretched to fit a group, or built for a group and far too heavy for a single site. Four things decide whether it fits both, and each one has to be designed in from the start.
The moment an operator runs several branches, everything that was a single value, the fee policy, the curriculum, the grading scale, becomes a decision about who owns it. Build that in late and it never fits.
British for the younger grades and IB for the older ones is an ordinary arrangement, and which curricula a branch offers varies branch to branch. Treat curriculum as a property of the school and that is impossible to express.
Layout direction, date handling and even a plain time range behave differently. A product that treats RTL as a stylesheet toggle breaks in ways nobody catches until a real user reports it.
Fee waivers and policy exceptions need board members, group directors and per-school committees: people who are not employees and appear in no staff hierarchy.
Every row carries its tenant, and Postgres row-level security enforces it in the database rather than relying on every query being written correctly. A missed filter returns nothing instead of another school's data.
select * from invoices -- tenant filter forgotten
Sample rows. Try “Every query” with the filter missed, then switch back to the database.
A generic lock-or-delegate framework lets a group either fix a setting for every branch or hand it down, while a single school simply owns all of them, with no group layer in the way.
Fee policy was the first consumer: fixed or percentage late fees, grace periods and an arrears ladder, owned at group level with an optional branch lock. Grading scales and approval chains now run on the same mechanism, and the framework has been proven live on both paths.
Lock a setting, then try changing it at a branch. Delegate it, and each branch sets its own.
A branch declares the curricula it offers, grade levels are created per curriculum, and sections inherit from their grade with a per-section override. Exams, grading scales and report cards resolve from the section, so a British section and an IB section in the same building are graded on their own terms.
Pick a section, add or drop a curriculum, or override one section. Grade and section names are samples.
English and Arabic dictionaries ship in code with a database-backed override table, so any string, or a whole new language, changes without a redeploy.
Right-to-left is handled as layout, not translation: logical CSS properties throughout rather than left and right, and numeric ranges isolated by direction so a time range does not reverse itself in Arabic.
Switch to right to left. Both ranges are real text, laid out by your browser.
A generic approvals engine handles any request type, with either N-of-M voting or a strict sequential chain, accountant to principal to committee president to chairman, where each step unlocks only once the previous one signs and a rejection vetoes immediately.
Request created. Voters notified.
Sign in order, or reject at any step. The 2-of-3 vote is a sample configuration.
Four audiences, four products. Each sees only what belongs to them, checked on the server rather than hidden in the interface.
Lands on my classes, with attendance, exams and lesson plans pre-filtered to the sections they are actually assigned to.
One card per linked child, then enrolment, attendance, report cards and invoices, with an ownership check on every endpoint, verified with live negative tests.
Timetable, homework, results and library access, on the web and in the mobile app.
Admins see the school; the operator sees the group, with consolidated dashboards across every campus.
Around them: parent, teacher and admin messaging with admin oversight for safeguarding, announcements targeted by role, a month calendar with multi-day events, and teacher availability slots for in-person or virtual meetings.
The full scope, grouped by the part of the school it serves. Each school switches on only the modules its package includes.
A no-login application flow with an opaque per-application token, a manually built tenant context and rate limiting. Entrance-test slots are row-locked, verified under a genuine two-request race for the last seat.
Generated without a headless-browser dependency to carry in production.
Per-branch timezones, so “today” resolves to the branch's calendar day and a school ahead of UTC never loses its own attendance.
A weekly grid on the GCC school week. Teacher, room and section conflicts are each prevented independently, with an accurate error per axis rather than a parsed database error. Substitutions are date-specific and leave the recurring pattern intact.
Plan changes append to a per-school history, so proration splits an invoice period across however many price changes fell inside it. Confirmed prices are frozen at contract time: a later rate-card edit never reprices an existing school.
Invoices generated per structure and cycle, many-to-one allocation so one payment settles several overdue invoices, and late fees computed automatically.
Uploaded browser-to-CDN, so files never touch the application servers, then reconciled by webhook-verified background jobs.
Server-side ownership checks on every parent-facing endpoint, verified with live negative tests rather than hidden in the interface. Library content a teacher creates is limited to the sections they teach.
A monorepo sharing types and validation across an API, a web app and a mobile client, with tenancy enforced in the database and long-running work pushed to a queue.
Services: Web Application Development · Mobile Application Development · Business Process Automation · ERP Services & Automation
A single school runs on it with no multi-branch overhead, and a group adds branches without cloning anything
British and IB grades coexist in the same branch, graded on their own scales
Fee policy is owned where the group wants it owned — locked centrally or delegated
Board and committee sign-off happens inside the product, with an audit trail per record
Arabic is a first-class interface, not a translated afterthought
Task, project and deadline management for delivery teams
Assignment, progress tracking and collaboration in one place, so teams know who owns what.
Security assessments that end in proof, not a PDF
A security assessment and remediation platform: nine frameworks, every gap routed to an owner, evidence checked and read by AI, and an auditor-ready closure record — in English and Arabic.
Fifteen HR services, answered on WhatsApp, written back to Oracle EBS
A bilingual AI assistant that turns Oracle EBS HRMS into a conversation — leave, certificates, attendance, approvals — for around 10,000 employees, hosted inside the Kingdom.