Multi-tenant learning platform — isolation without per-tenant infra
Designed a multi-tenant LMS so operators could onboard organisations with their own branding and reporting, without a database or cluster per customer.
The problem
Operators wanted one product for many organisations, with data isolation, branding, and reporting, without infrastructure cost growing linearly with tenants.
The role and approach
Chose shared-database, tenant-scoped queries, and application-level isolation for early scale. Split billing, content, and analytics so they could change independently. Put an operator analytics view in the first release so value was visible to non-technical buyers.
The outcome
New organisations went from request to a live workspace in hours rather than a multi-day install. Reporting stayed inside the product instead of in side spreadsheets.
Hard decisions
- 01Shared database and tenant-scoped queries over schema-per-tenant, because early tenant count did not justify the operational cost.
- 02Service boundaries between billing, content, and analytics so a change in one did not force a rewrite of the others.
- 03Operator analytics in the first release, so the product could be evaluated by a non-technical buyer.
Lesson for future clients
The isolation model is a pricing and support decision. Choose it deliberately; it is expensive to undo after the first twenty tenants.