Skip to main content

Surfaces and Host Model

The main product app is split into three product surfaces. That is the core product decision in this starter.

Surfaces​

  • org The staff-facing surface for a subscribing organization.
  • portal The tenant-facing customer surface.
  • platform The operator surface used to manage the whole system.

Why This Matters​

Many B2B2C products fail because they blur staff, customer, and platform concerns into one route tree and one UI system. This starter keeps those concerns explicit from the start.

URL Model​

  • org routes live on the app host without /org in the public URL
  • portal routes live on tenant hosts without /portal in the public URL
  • platform routes stay under /platform

Evaluation Questions​

  • Do you need distinct staff and customer experiences?
  • Do you need tenant-host routing for portal users?
  • Do you want platform operations kept separate from customer-facing product work?