Vector Storage
Vector storage controls where Cognipeer keeps the searchable representation of datasource content. It affects semantic search quality, scale, cost, data location, and administration.
What this is
When a datasource is indexed, Cognipeer prepares the content so Peers can search it by meaning, not only by exact words. Vector storage is the place where that searchable representation is kept.
Most teams can start with the system default. Workspace admins may choose an external provider when they need more control over scale, data location, or operational requirements.
For provider setup commands, API configuration, schemas, or programmatic management, use the Developer Hub.
When the default provider is enough
Use the system default when:
- You are getting started with datasources.
- Your team wants minimal setup.
- Search volume is moderate.
- You do not have a strict requirement to manage vector storage outside Cognipeer.
- You want Cognipeer to handle routine storage operations.
The default provider is usually the best first choice for pilots, small teams, and standard knowledge-base use cases.
When to choose an external provider
Consider an external provider when:
- Your datasource volume is large or growing quickly.
- Your organization requires a specific data location or vendor.
- You need dedicated operational controls.
- You already manage a vector database for other systems.
- Your security, compliance, or procurement process requires direct provider ownership.
- You need to coordinate vector storage with an on-premise or private deployment.
External providers usually require credentials, provider-side setup, monitoring, and an owner who understands the service.
Provider comparison for admins
| Provider type | Best for | Admin considerations |
|---|---|---|
| System default | Standard teams, pilots, and simple setup | Least operational overhead. Review plan quotas and search quality after indexing. |
| Managed vector database | Larger production workloads | Requires account ownership, access credentials, cost monitoring, and provider health checks. |
| Self-hosted vector database | Private, on-premise, or compliance-driven deployments | Requires infrastructure ownership, backups, scaling, and operational support. |
| Hybrid search setup | Teams that need semantic and keyword matching together | Requires search-quality testing and clear expectations for ranking behavior. |
Before changing providers
Prepare the following before making changes:
- The business reason for changing storage.
- The datasources affected.
- Provider credentials or access details.
- Expected data volume and search volume.
- A test plan for search quality.
- A rollback plan if the new setup does not meet expectations.
- A communication plan for users who depend on the affected Peers.
Changing vector storage can require re-indexing datasource content. Plan the change during a low-impact window when possible.
Configure a provider in Datasource settings
- Open Datasources in Studio.
- Choose the datasource or workspace setting that controls vector storage.
- Select the provider type.
- Enter the required provider details.
- Save the configuration.
- Run the connection test if available.
- Re-index or refresh the datasource if Studio prompts you to do so.
- Test the Peers that rely on the datasource.
Only admins who understand the provider ownership and data requirements should change these settings.
Test search quality after migration
After changing providers, test:
- Common user questions.
- Rare but important questions.
- Questions that require exact terms.
- Questions that require semantic matching.
- Datasource content with long documents, tables, or attachments.
- Peers that combine multiple datasources.
Compare results against the previous provider before declaring the migration complete.
Operational guidance
- Monitor provider usage and cost.
- Keep provider credentials limited to the right admins.
- Re-test search after major datasource changes.
- Document which team owns the external provider.
- Keep a rollback plan for critical Peers.
- Review search behavior after changing embedding or retrieval settings.
Troubleshooting
Search results are missing expected content
Confirm the datasource has finished indexing, then test the same question in the datasource playground.
Results are less relevant after a provider change
Review search settings, re-index the datasource, and compare test questions with the previous provider.
The provider connection fails
Check credentials, provider availability, network access, and workspace permissions. Use your provider administrator for service-specific checks.
For technical implementation
Use the Developer Hub for provider-specific setup, API configuration, Docker or infrastructure commands, migration scripts, endpoint details, and programmatic provider management.