Feature Description
Add a new Valkey vector store node that enables users to store, index, and search vector embeddings using Valkey's valkey-search module. This would provide Flowise users with an open-source, high-performance alternative to the existing Redis vector store node.
Feature Category
New Node/Component
Problem Statement
The existing Redis vector store node uses @langchain/redis which depends on RediSearch (part of Redis Stack) for vector similarity search commands (FT.CREATE, FT.SEARCH, etc.). While Redis and Valkey are mostly protocol-compatible for core operations, their search modules are not compatible — RediSearch commands do not work with Valkey's valkey-search module. This means the Redis node cannot be used with Valkey deployments.
This is a blocker for teams running Valkey in production — whether self-hosted or through managed cloud services — which has become increasingly common since the Redis license change.
Proposed Solution
Add a new Valkey vector store node in packages/components/nodes/vectorstores/Valkey/ following the same patterns as the existing Redis node.
The node would use valkey-glide (the official Valkey client) with Valkey's native search commands instead of RediSearch.
Value
- Open-source alternative: Valkey is a Linux Foundation project with transparent governance and community-driven development
- Performance: Valkey's valkey-search module delivers single-digit millisecond latency with 99%+ recall for vector search
- Scaling: Linear scaling with cluster mode support
- Cloud support: Managed services from major cloud providers
- Migration path: For teams moving from Redis to Valkey after the license change
Mockups or References
No response
Additional Context
Valkey: https://valkey.io/
Valkey search module: https://valkey.io/topics/search/
Feature Description
Add a new Valkey vector store node that enables users to store, index, and search vector embeddings using Valkey's valkey-search module. This would provide Flowise users with an open-source, high-performance alternative to the existing Redis vector store node.
Feature Category
New Node/Component
Problem Statement
The existing Redis vector store node uses
@langchain/rediswhich depends on RediSearch (part of Redis Stack) for vector similarity search commands (FT.CREATE,FT.SEARCH, etc.). While Redis and Valkey are mostly protocol-compatible for core operations, their search modules are not compatible — RediSearch commands do not work with Valkey's valkey-search module. This means the Redis node cannot be used with Valkey deployments.This is a blocker for teams running Valkey in production — whether self-hosted or through managed cloud services — which has become increasingly common since the Redis license change.
Proposed Solution
Add a new Valkey vector store node in
packages/components/nodes/vectorstores/Valkey/following the same patterns as the existing Redis node.The node would use
valkey-glide(the official Valkey client) with Valkey's native search commands instead of RediSearch.Value
Mockups or References
No response
Additional Context
Valkey: https://valkey.io/
Valkey search module: https://valkey.io/topics/search/