Product code, not customer code
Nothing in the codebase names a customer. Everything that differs between websites is configuration data on a deployment.
Internal platform
Former Factory
The factory that builds and runs Former customer websites. One reusable product codebase, many tenants, zero customer-specific forks.
Headless is the primitive
Every module exposes its capability as an API first. Hosted pages and embeddable widgets are transports in front of the same core.
Three levels of customization
Theme tokens, then layout variants, then fully custom front-ends on the API — a premium site never needs a code fork.
Isolation by construction
Tenant scoping lives in database policies and server-side authorization, never in UI logic or client filters.
Architecture layers
- PresentationHosted UI · Embedded widget · Headless API
- Module registryDefinitions, capabilities, config schemas, lifecycle
- Platform coreTenants, deployments, keys, theming, audit, rate limits
- DataPostgres with row-level tenant isolation