Sheet W-01 · Multi-tenant SaaS in production · Sport and recreation
LiveOne codebase serving several fully branded tenants with isolated data and role-based access, running in production.
- Goes in
- One codebase, one deployment, one owner console
- What we built
- The host decides which tenant you are, and every query is scoped to it
- Comes out
- Four branded sites, each with its own content, roles and members
- The line it does not cross
- No tenant can read another tenant’s data
Note 1 · The constraint
An operator running more than one site, brand or franchise usually ends up with a separate installation per customer. Every change then has to be made several times, and the copies drift apart within a year.
Note 2 · What transfers
This is the engineering that lets one system serve many customers, branches or franchisees without forking it per customer. A vendor portal, a dealer network or a multi-site operations tool is the same problem wearing different clothes.
- Tenants live
- Four
- Automated tests
- ~1,290
- Hosting
- Oracle Cloud, Hyderabad
- Tenant isolation
- Per-tenant data scoping