Multi-tenant SaaS
Four portals. One backend.
Distinct user groups often need different views of the same data and different permissions over it. Four applications would mean four codebases, four deployment pipelines, and the same business rules written four times over. Versions drift within a year.
We build one backend with role-based portals on top. Shared domain logic, separate access boundaries, a single deployment. Permissions resolve at the data layer rather than in each interface, so a rule written once applies everywhere it should. Adding another role becomes a configuration change instead of a new application.
Django's permission framework and row-level scoping make this the natural shape for Python SaaS — the same access-control discipline we apply when the product has more than one user type.
