Skip to main content

Tenancy and Routing

Tenancy in this starter is not an add-on. It is part of the product model.

Core Model

  • the organization is the tenant boundary
  • portal users access tenant-facing experiences on tenant hosts
  • org staff and platform operators stay on their own product surfaces

Routing Summary

  1. Middleware inspects the incoming hostname.
  2. The hostname is resolved to tenant context.
  3. Verified tenant headers are set server-side.
  4. Server components and backend handlers use that verified context.

Why Buyers Should Care

If your product needs real tenant-host routing, this starter already treats that as a first-class concern.

That means the app structure, local setup, and backend enforcement model already assume tenancy is real instead of pretending everything can stay path-based forever.

Isolation Rule

Tenant data stays isolated by organization boundary, and backend checks remain the security boundary.