TABSAP LMS is a school ERP, not a course platform. The distinction matters: most systems sold as learning management software handle teaching and leave the school running its actual operations on spreadsheets.
This covers the operations — academics, fees, HR, exams, attendance, transport and library — plus a full public-facing school website with a CMS, an admissions flow and multi-theme support. A school gets its administration and its public presence from one system rather than stitching two together.
One codebase deploys to unlimited schools through per-tenant configuration, with each school's data in an isolated database rather than partitioned by a tenant column in shared tables.
That isolation decision is the one that cannot be retrofitted later. It determines whether a mistake in a single query can surface one school's records inside another's — and by the time that question is being asked in production, the answer is already fixed by the schema.
Every release passes an automated pipeline — TypeScript compilation and test verification — before it deploys. A school ERP that breaks during enrollment week is not a bug report, it is an incident. The gate exists because the deployment target is a live school day.
374 API endpoints and 164 data models are specified across the platform, covering the enrollment, scheduling and administrative workflows a school actually runs on.
That documentation is what makes the mobile side possible. The companion React Native app for parents, students and staff runs against the same backend and the same contract, rather than a second API written afterwards to catch up with the first.
Live and in active use by real schools, including Al Hijazi and Shining Star Academy.
The pricing model — monthly, annual, or one-time plus maintenance and hosting — is still under research, so none is published here until that decision is made.