Namespaces
Isolated multi-tenant environments with dedicated vector storage, access controls, and complete data separation
Why do anything?
Multi-tenant applications need complete data isolation. Without namespaces, customer data can leak across boundaries, creating security and compliance risks.
Why now?
Enterprise AI applications require SOC 2 compliance and data residency controls. Manual tenant isolation is error-prone and doesn't scale.
Why this feature?
Each namespace maps to a dedicated Qdrant collection with 12 protected payload indexes. Full cascade deletion ensures no orphaned data. Supports cross-namespace migration for tenant onboarding.
How It Works
Namespaces provide tenant isolation by mapping each namespace to a dedicated Qdrant collection. All documents within a namespace share the same vector storage while maintaining complete separation from other namespaces.
Namespace Creation
Generate namespace_id, create Qdrant collection with same name
Index Configuration
Set up 12 protected payload indexes for _internal fields
Access Control Setup
Configure namespace-scoped API keys and permissions
Cascade Deletion
12-step process: webhooks → alerts → taxonomies → clusters → retrievers → collections → batches → documents → buckets → secrets → namespace
Why This Approach
Namespace-per-Qdrant-collection ensures complete vector isolation. Protected indexes guarantee system field queryability. Cascade deletion prevents orphaned resources.