Skip to main content

System Architecture

This is the buyer-facing architecture summary for the starter.

It is meant to answer the question: what are the major pieces, and why were they separated this way?

Major Pieces​

  • apps/app The main authenticated product app for org, portal, and platform surfaces.
  • apps/marketing The separate public marketing site.
  • apps/docs The published docs site.
  • packages/backend The authored Convex backend.
  • packages/* Shared contracts, configuration, permissions, capabilities, and infrastructure.

Why This Shape Exists​

The starter is designed to keep product surfaces explicit instead of collapsing everything into one undifferentiated frontend and one pile of backend logic.

That separation matters when a product needs:

  • different experiences for staff, portal users, and platform operators
  • backend enforcement around tenant isolation and access control
  • shared infrastructure without turning every shared concern into app-local duplication

Buyer Takeaway​

You are not just buying screens. You are buying a repo shape that already separates product surfaces, backend ownership, and shared contracts in a way that can keep scaling.