LanceDB vs pgvector
LanceDB vs pgvector: side-by-side comparison of two vector-database infrastructure systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Cost & capability
| LanceDB | pgvector | |
|---|---|---|
| Cost tier | free | free |
| $/Mtok input | 0 | 0 |
| $/Mtok output | 0 | 0 |
Where they differ (15)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| LanceDB | pgvector | |
|---|---|---|
| Type | Embedded Arrow-columnar vector DB | PostgreSQL vector extension |
| Created | 2023-02 | 2021-04 |
| Latest release | python-v0.31.0-… 2026-04-29 | no releases |
| License | Apache-2.0 | Custom |
| GitHub | 10.2k★ +200/mo HTML | 21.1k★ +123/mo C |
| Pricing | Free + paid | Free (PostgreSQL License open source) |
| Funding | $38M total Series A · 2025-06 | No external funding — open-source project by independent developer |
| Backend storage | custom (Lance columnar format on object storage) | Postgres |
| Deployment | Both | Self-hosted only (PostgreSQL extension; managed via Supabase/AWS RDS/etc.) |
| API surface | REST (cloud), SDK: Python, JS/TS, Rust | SQL via Postgres protocol |
| Embedding | multiple supported | BYO |
| Multi-tenancy | Logical namespace per dataset; embedded library or LanceDB Cloud (single-tenant available) | Logical isolation via Postgres schemas/databases; managed providers (Supabase, Neon, RDS) add tenant-level controls |
| MCP | no first-party MCP adapter published as of 2026-05; community connectors may exist. | via Postgres MCP servers (community) |
| A2A | no Google A2A (Agent2Agent) integration documented as of 2026-05. | not supported |
| OpenTelemetry | no first-party OpenTelemetry exporter documented; standard logs/metrics typically available. | via Postgres OTel |
At a glance
| LanceDB | pgvector | |
|---|---|---|
| Section | Vector-database infrastructure | Vector-database infrastructure |
| Tier | T1 | T1 |
| Type | Embedded Arrow-columnar vector DB | PostgreSQL vector extension |
| Created | 2023-02 | 2021-04 |
| Latest release | python-v0.31.0-… 2026-04-29 | no releases |
| License | Apache-2.0 | Custom |
| GitHub | 10.2k★ +200/mo HTML | 21.1k★ +123/mo C |
| Pricing | Free + paid | Free (PostgreSQL License open source) |
| Funding | $38M total Series A · 2025-06 | No external funding — open-source project by independent developer |
| Backend storage | custom (Lance columnar format on object storage) | Postgres |
| Deployment | Both | Self-hosted only (PostgreSQL extension; managed via Supabase/AWS RDS/etc.) |
| API surface | REST (cloud), SDK: Python, JS/TS, Rust | SQL via Postgres protocol |
| Embedding | multiple supported | BYO |
| Multi-tenancy | Logical namespace per dataset; embedded library or LanceDB Cloud (single-tenant available) | Logical isolation via Postgres schemas/databases; managed providers (Supabase, Neon, RDS) add tenant-level controls |
| MCP | no first-party MCP adapter published as of 2026-05; community connectors may exist. | via Postgres MCP servers (community) |
| A2A | no Google A2A (Agent2Agent) integration documented as of 2026-05. | not supported |
| OpenTelemetry | no first-party OpenTelemetry exporter documented; standard logs/metrics typically available. | via Postgres OTel |
| Optimised for | low-latency similarity search + scale | low-latency similarity search + scale |
| Anti-fit | not for relational / graph-heavy queries (vector-first by design) | not for relational / graph-heavy queries (vector-first by design) |
Taxonomy
| Axis | LanceDB | pgvector |
|---|---|---|
| storage | vector | vector |
| retrieval | similarity | similarity |
| persistence | long-term | long-term |
| update | overwrite | overwrite |
| unit | chunk | chunk |
| governance | inspectable | inspectable |
| conflict | overwrite | overwrite |
Pros & cons
LanceDB
Pros: Built on Lance columnar format — gives you vector search + analytical SQL on the same data without ETL between systems.
Cons: Newer ecosystem; fewer integrations than Pinecone / Weaviate; Lance format is non-standard so portability requires conversion.
pgvector
Pros: Postgres extension — keeps vector data alongside transactional data with full ACID; minimal ops for shops already running Postgres.
Cons: Performance plateau at very large vector counts; limited filter pushdown vs purpose-built engines.