Namespaces
Namespaces are logical isolators of vector indices within a single cluster. Each project, environment, or context runs in its own namespace, preventing results contamination.
A namespace is like a “virtual database” within the system. Searches in one namespace NEVER return chunks from another namespace.
The Problem
Without namespaces:
- Searching for “login” returns chunks from 50 different projects
- Easy to “leak” context between teams
- Impossible to manage indices by project or environment
With namespaces:
- Search is isolated: “login” returns ONLY from project X
- Multiple teams can share an instance without contamination
- Scalability: adding a new project = new namespace
Naming & Conventions
Standardizing namespace names is essential for organization and automation in multi-tenant clusters.
Recommended Pattern
<org>-<project>-<environment>Examples:
kaffyn-vectora-prod # Org-Project-Env
kaffyn-vectora-dev # Same project, different environment
acme-backend-staging # Another projectValidation
Namespaces must:
- Have 3-63 characters
- Use only
[a-z0-9-](lowercase, numbers, hyphens) - Start with a letter
- NOT include underscores or spaces
Lifecycle
Namespace management covers everything from technical initialization to secure disposal of indexed data.
Creation
# Via CLI
vectora namespace create --name kaffyn-vectora-prod
# Via config
vectora.config.yaml:
project:
namespace: kaffyn-vectora-prodIndexing
Once created, the namespace accepts chunks:
# indexing.yaml
namespace: kaffyn-vectora-prodSearch
Every search specifies a namespace:
// Search is filtered by namespace
const results = await vectoraClient.search({
query: "How to validate tokens?",
namespace: "kaffyn-vectora-prod",
top_k: 10,
});Multi-Tenancy Patterns
Using namespaces allows for the implementation of different isolation patterns depending on the needs of the project or organization.
Pattern 1: One Namespace per Project
# Team A
namespace: acme-backend-prod
# Team B
namespace: acme-frontend-prodUse when: Completely separate teams, rigorous compliance/security.
Part of the Vectora ecosystem · Open Source (MIT) · Contributors