Lattice
Skip to content

pgvector alternatives

4 substitutes · 4 in retrieval · 0 adjacent

The short answer

4 tools on this index are recorded as a substitute for pgvector. 4 of these run the same way you already deploy pgvector (self-hosted), and 4 are permissively licensed, so they do not change what you can ship. All of them sit in Retrieval & Vector Stores, so the choice is a real one rather than a category change. There is no overall winner here: which one is right depends on traffic shape, operational budget and how much of pgvector you have already built around.

By Lattice editorial · Comparison reviewed · method

Better than this page

4

Real substitutes

in Retrieval & Vector Stores
  • Qdrantdatabase · Apache-2.0

    Rust vector database with rich filtering payloads.

    Use when Vector-first workloads with heavy metadata filtering at scale.

    Skip when You want no new datastore to operate.

  • Chromadatabase · Apache-2.0

    Embeddings database designed for fast prototyping.

    Use when Getting a prototype working in an afternoon.

    Skip when You need durability, scaling or concurrent writes.

  • Milvusdatabase · Apache-2.0

    Cloud-native vector database supporting billion-scale indexes.

    Use when Billion-scale indexes with a cloud-native deployment.

    Skip when You need a small, comprehensible system.

  • Weaviatedatabase · BSD-3-Clause

    Graph-aware vector database with hybrid and multi-vector search.

    Use when Hybrid or multi-vector search with a graph-shaped data model.

    Skip when Your data is genuinely relational and joins matter more than vectors.

This graph is bidirectional and unsponsored. A tool appears here if pgvector or another entry names it as a substitute, and Qdrant, Chroma, Milvus and Weaviate point at pgvector as well. How this index is compiled — including where it is wrong.