Multi-Tenant SaaS Architecture: Lessons from Building a School ERP

STUCARE had to serve many schools from one codebase, with each school's data fully isolated from every other's, while still sharing a single set of features and a single deploy pipeline.

We used a shared-database, tenant-scoped approach: every table that holds tenant data carries a tenant identifier, and every query passes through a layer that automatically scopes to the current tenant. The rule that made this safe was strict — no query bypasses that layer, ever, including internal admin tools.

Role-based access control had to work on two levels at once: within a tenant (admin, teacher, accountant, parent) and across the platform (our own support and billing roles). Keeping these as separate permission systems, rather than merging them, kept the logic readable as the school count grew.

Workflow automation — fee reminders, attendance alerts, exam scheduling — is where a lot of the real value showed up for schools day to day. The technical architecture matters, but it only matters because it's what let those automations run reliably for every tenant without special-casing any one school.