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 demand SOC 2-grade controls and data residency. 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.
Where This Is Used
Recent updates
Full changelog- Jul 6, 2026Create namespaces and collections by picking features, not extractorsYou can now declare what you want to search by (a features list) when creating a namespace or collection, and the server resolves the right extraction pipeline for you. Studio's collection wizard gained a modality-grouped feature picker, and features-first creates preserve your metadata fields by default. Extractor names become an advanced detail instead of a required decision.
- Jul 1, 2026Live cluster resources & capacity for namespacesThe namespace view now shows a real cluster resources and capacity panel — actual serving resources and headroom — replacing the old "coming soon" placeholder. The Total Documents card also no longer flashes a misleading 0 on a cold cache.
- May 22, 2026MVS standalone namespaces — bring your own vectorsRun Mixpeek Vector Store in standalone mode: create a namespace, push your own embeddings, and get agent-native dense + sparse + BM25 hybrid search on object storage — no extraction pipeline required. Add Managed extraction later without re-indexing.