BusinessOS Docs

What this platform is

BusinessOS is a multi-tenant platform where builders (project owners) assemble and operate business products using modules.

There are four core concepts:

• Tenant: the builder’s workspace (billing, team, enabled modules).
• Project: an individual “site/product” owned by a tenant. Projects are what end-users interact with.
• Module: an installable unit of capability that has two layers:
  • Project-owner backoffice (admin inside a project)
  • End-user/public experience (project site pages and end-user APIs)
• End-user: a user that belongs to a project (authenticated via project_session).

Two-layer module rule

Every module must be designed with a strict separation:

• Project-owner backoffice
  • Routes under /p/:slug/modules/:moduleId/...
  • Uses project-owner auth session (builder login)
  • Controls configuration, publishing, pricing, access rules, analytics
• End-user/public
  • Routes under the project host and internally rewritten to /site/...
  • Uses end-user session (project_session)
  • Consumes what the builder published

Core module

Each project has exactly one core module (stored in project_module_installations.config.isCoreModule = true).

Core module drives:

• Landing template selection (/)
• Default end-user navigation expectations
• Template-specific authenticated experience (for example /portal, /courses, /products)

Payments

All monetization must go through Payments Core:

• Checkout/session creation
• Webhooks
• Entitlements (grant/revoke)

Feature modules never integrate Stripe directly.