Problem
There is currently no native driver support for Weaviate (https://weaviate.io/), an open-source AI-native vector database. Teams building semantic search, RAG, and other AI/ML workloads rely on Weaviate for vector storage and similarity search, but cannot connect it through TablePro today. This forces us to manage Weaviate separately from the other databases we already access through TablePro, which is slow and fragmented.
Proposed solution
Add native driver support for Weaviate (https://weaviate.io/) so it can be added and accessed alongside the other 18+ supported databases. Ideally this would include connecting via Weaviate's REST/gRPC endpoints (or its client APIs), browsing collections/classes, and running vector and hybrid search queries from within TablePro.
Alternatives considered
Considered managing Weaviate separately through its own console/clients (e.g., the Weaviate Python/JS clients or REST API directly), but this means context-switching out of TablePro and losing a unified workflow. Also considered using a generic HTTP/REST tool, but it lacks first-class schema browsing and query support for Weaviate collections.
Related database type
N/A / General
Problem
There is currently no native driver support for Weaviate (https://weaviate.io/), an open-source AI-native vector database. Teams building semantic search, RAG, and other AI/ML workloads rely on Weaviate for vector storage and similarity search, but cannot connect it through TablePro today. This forces us to manage Weaviate separately from the other databases we already access through TablePro, which is slow and fragmented.
Proposed solution
Add native driver support for Weaviate (https://weaviate.io/) so it can be added and accessed alongside the other 18+ supported databases. Ideally this would include connecting via Weaviate's REST/gRPC endpoints (or its client APIs), browsing collections/classes, and running vector and hybrid search queries from within TablePro.
Alternatives considered
Considered managing Weaviate separately through its own console/clients (e.g., the Weaviate Python/JS clients or REST API directly), but this means context-switching out of TablePro and losing a unified workflow. Also considered using a generic HTTP/REST tool, but it lacks first-class schema browsing and query support for Weaviate collections.
Related database type
N/A / General