Platform planes and database boundaries
System-level planes
The current architecture is broader than a single two-database design. Central BuildWithHQ responsibilities include control, template/catalog, AI/runtime orchestration, and marketplace/distribution concerns. Per-SaaS application responsibilities are isolated into dedicated runtime/data, AI/vector, logging/compliance, and custom-service execution boundaries.
Per-SaaS application shape
A SaaS app is designed to have:
- a transactional/runtime database for application records and business operations;
- a separate AI/vector database for sources, chunks, embeddings, retrieval state, and telemetry;
- a separate compliance/log database for append-oriented history and evidence;
- an isolated code container/service boundary for custom logic.
Central control-plane boundary
Builder accounts, builder users, platform subscriptions, BuildWithHQ billing, SaaS app registration, routing, resource allocation, domains, API clients, backups, integrations, security metadata, and platform audit belong to the central control plane.
Rule
Do not place a generated SaaS product’s end-customer business data or end-customer subscription billing into the BuildWithHQ builder-account control plane.