Tenant isolation is a product concern
Isolation is not delegated to a landing page. The product model is built around tenant-scoped data, entitlements, retention, and operator boundaries.
BrainCaps public product surface
Memory for sensitive teams that need proof, not prompt theatre.
BrainCaps is the business product surface for structured memory, controlled ingestion, provenance, and customer-facing clarity. PortalHQ remains the shared SaaS shell. BrainCaps App remains the customer workspace.
What this public surface does
Explain where the product starts and where the shared shell stops.
Make creation, ingestion, evidence, and trust paths legible before sign-in.
Boundary rule
Public host: https://braincaps.io
Customer app: https://app.braincaps.io
Shared shell: PortalHQ
Product shape
What BrainCaps sells, and what it refuses to become.
BrainCaps is not a generic AI shell, not a portal clone, and not a chat façade for unstructured storage. It is a product surface for living memory, controlled ingestion, and evidence-backed retrieval.
Public copy should describe the real execution model, not hide it.
Product promise
Create customer-specific memory boundaries.
Ingest controlled source material with provenance.
Expose usage, limits, and health without leaking operator concerns.
Sensitive clients do not land on a shared admin plane
The customer workspace stays separate from the operator console. BrainCaps360 remains private and out of the public route map.
PortalHQ stays the shell, not the business UI
Access and billing stay transversal. The BrainCaps business experience lives in the product app where memory logic and product context are actually applied.
Stack logic
Where each responsibility lives.
The point of the stack is not aesthetics. It prevents product drift, mixed boundaries, and false assumptions about where billing, identity, customer data, and operator power should live.
Strate 1
Public entry
The public host explains the product, the trust posture, and the path into the SaaS journey. It does not host account logic.
braincaps-web
Strate 2
Shared shell
PortalHQ handles identity, organizations, billing, access, and the shared launch layer across products.
PortalHQ
Strate 3
Customer workspace
BrainCaps App takes over after launch and shows the product experience: memory, ingestion status, usage, and settings.
braincaps-app
Strate 4
Business services
BrainCaps API, orchestration, parsing, storage, and private operator tooling stay behind the product boundary.
braincaps-api + braincaps360
Creation model
How a BrainCaps becomes real.
The customer does not buy a page. They buy a controlled memory perimeter with ingestion rules, retrieval logic, and visible operating guardrails.
Step 1
Create the workspace boundary
A customer workspace resolves to a product-scoped BrainCaps perimeter, not to a generic assistant session.
Step 2
Ingest controlled source material
Documents, connectors, and evidence enter through explicit ingestion paths with provenance and retention intent.
Step 3
Turn raw content into memory objects
The product builds structured memory, links, decisions, and evidence layers instead of flattening everything into a chat history.
Step 4
Operate with proof and guardrails
Usage, entitlements, health, and operator boundaries remain visible so the customer sees product state without reading infra logs.
Non-negotiables
What stays outside the public surface.
The public site should make the operating model easier to understand, not smuggle shell logic or private administration back into the product.
Boundary checklist
No duplicate login or billing shell in BrainCaps public.
No operator administration mixed into the customer path.
No fake compliance language detached from the real product boundary.
No customer-sensitive rollout until the customer surface and P0 evidence are closed.
Next public conversation
The next useful layer is not more shell chrome. It is a sharper explanation of ingestion modalities, customer-specific BrainCaps creation, and the trust model customers need before they put sensitive material into the system.