Namespaces provide logical separation for different use cases, applications, or environments while maintaining independent configurations and security controls.

​
Key Concepts

Isolation

Each namespace operates as a completely isolated environment with its own:

  • Resource allocation
  • Access controls
  • Configuration settings

Indexing

Configure vector and payload indexes for:

  • Feature extraction
  • Search capabilities
  • Data organization

​
Vector Indexes

Mixpeek provides managed vector indexes that automatically handle embedding updates and model improvements:

# Available vector indexes
embedding_models = {
    "image": {
        "modalities": ["image", "text"],
        "type": "dense",
        "size": 512
    },
    "multimodal": {
        "modalities": ["image", "video", "text"],
        "type": "dense", 
        "size": 1408
    },
    "text": {
        "modalities": ["text"],
        "type": "dense",
        "size": 1024
    },
    "keyword": {
        "modalities": ["text"],
        "type": "sparse"
    }
}

​
Payload Indexes

​
Best Practices

​
Organization Strategies

1

Environment Separation

Create separate namespaces for development, staging, and production

2

Use Case Separation

Isolate different applications like product search, content discovery, etc.

3

Client Separation

Maintain distinct namespaces for different customers or regions

​
Naming Conventions

Use descriptive, lowercase names
Include environment or purpose
Be consistent across teams
Add relevant prefixes/suffixes

Examples:

prod-ecommerce
dev-content-search
staging-recommendations

Learn more about namespace management in our API Reference.

Was this page helpful?

Suggest editsRaise issue
CollectionsAssets