In a multi-tenant LMS, a single deployment serves many institutions ("tenants"). Each tenant gets its own users, courses, branding, billing, and analytics — but the platform code, database (with tenant-scoped row-level isolation), and infrastructure are shared. This pattern lowers per-tenant cost dramatically vs single-tenant hosting, while keeping data logically separated.
Tenant isolation strategies
- Shared DB, shared schema, tenant-id column — cheapest, common in SaaS LMSs.
- Shared DB, per-tenant schema — stronger isolation, simpler backups per-tenant.
- Per-tenant database — strongest isolation, used for regulated industries or sovereign hosting.
Universities running a single tenant for the entire institution typically choose option 1 with proper indexing. Multi-campus universities or training networks managing several brands choose option 2 or 3.