BuildWithHQ
Canonical knowledge unit · builder

Wholesale resource pools and per-app allocation

Builder accounts manage separate shared capacity pools for primary DB, log DB, AI DB, and container storage and allocate those resources across their SaaS portfolio.

ID: BWHQ-BUILDER-002Status: currentAuthority: highresourcesstoragequotaportfolio

Wholesale resource pools and per-app allocation

Resources are separate

Primary database, logging database, AI/vector database, and container storage are distinct resource types. Do not collapse them into one ambiguous “storage” number.

Allocation model

The account owns plan capacity plus purchased add-ons. It assigns capacity to individual SaaS apps. Allocation changes must respect shared-pool headroom and concurrency rules so simultaneous requests cannot overdraw the pool.

Operational thresholds

The portal specification calls for visible warning thresholds as utilization approaches capacity.

Commercial effect

Portfolio-level resource pooling fits agencies/MSPs better than forcing each small SaaS app into a separate retail infrastructure subscription. Usage growth can drive automated capacity expansion.

Related knowledge

Builder account control planeThe builder portal manages the BuildWithHQ customer account, team, platform billing, portfolio, resource allocation, domains, API clients, backups, integrations, sessions, and audit—not the SaaS end-customer data plane.
Machine-readable source: canonical Markdown. This HTML companion exists for human reading, search indexing, and AI retrieval.