Multi-Tenant Graph RAG
Model tenant boundaries, graph overlays, and bucket-routed writes for B2B Graph RAG.
Use Tenant IDs as Graph Boundaries
tenantId is the hard namespace and graph boundary. Use separate tenant IDs when two customers must have separate graphs. Cloud organization/API-key auth resolves the account and schema, but the application tenant remains customer-supplied.
Write Documents Through Buckets
Buckets choose the write graph. Use public for externally visible knowledge and an internal bucket/graph for customer activity, transcripts, and support notes.
Ingest Events With Participants
Events are business occurrences. Participants are provenance and graph context, not access grants. They let broad B2B questions traverse customers, issues, contacts, and product areas inside the selected graph.
Search Within Tenant and Graph
The Acme and Globex clients cannot cross tenant graphs. Within Acme, graph: "internal" reads internal records plus public ancestors. explain shows active resources, weights, graph closure, and skipped resources while debugging.