Head to head · Vector search · October 2026 research run

Epsilla Vector Database vs LanceDB

LanceDB scores 66.3 (B) on agent readiness against Epsilla Vector Database's 40.4 (E), and leads in 6 of 7 scored categories. Epsilla Vector Database leads on payments & pricing. Both do vector search.

Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons

Which one, for what

Epsilla Vector Database E

Best for Only for teams already running Epsilla, or buyers of its agent platform who want the bundled vector storage.

Ahead on

  • Payments & pricing, 45 against 30

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No tagged release since 29 November 2025 and no release notes since March 2025

LanceDB B

Best for Agents whose code can import a library and keep retrieval data in object storage, from notebooks to multimodal datasets.

Ahead on

  • Reliability, 75 against 60
  • Schema & documentation, 81 against 36
  • Agent ergonomics, 74 against 55
  • Security & auth, 44 against 27
  • Maintenance & community, 93 against 8
  • Transparency & trust, 75 against 64

Also in its favour

  • No key needed to call it
  • Rated higher by the reviewer agents, 3.0 against 1.5 out of 5
  • No incidents deducted, where Epsilla Vector Database loses 3 points for them

Watch for

No self-serve hosted API. Enterprise is sold through a contact form

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community LanceDB +85

Epsilla Vector Database 8

The last tag anywhere is cc-0.3.36 on the cc branch on 29 November 2025, and the last tag on main is v0.3.17 on 8 October 2025, both more than 180 days ago (0). The only commit since is an untagged feat/batch-search branch commit of 29 September 2026, not a release (0). Release notes stop at March 2025 and the main branch's last commit was 16 November 2025; GitHub issues weren't readable today, per the 1 October check (2). pyepsilla 0.3.15 is tagged 19 October 2025 and epsillajs v0.3.6 18 April 2024 in their repositories (3). Docker build workflows only, no test workflow on the server, and the Python client still disables TLS checks (3). 0 + 0 + 2 + 3 + 3 = 8.

LanceDB 93

v0.41.0 on 29 October 2026 (30). v0.37.1 on 10 August, v0.38.0 on 31 August, v0.39.0 on 17 September, v0.40.0 on 7 October and v0.41.0, with daily betas between them, in the 90 days to 2 November (20). Maintainers filed and labelled bugs themselves and merged fixes on 1 October, though 493 issues were open; the main branch had commits on 2 November, and the tracker wasn't readable then (18). Python, TypeScript, Rust and Java clients ship from one version tag (15). CI passing per the 1 October check, with Dependabot and cargo-deny configured in the repository (10). Total 93.

Schema & documentation LanceDB +45

Epsilla Vector Database 36

No OpenAPI file found (0). llms.txt on GitBook now lists 73 pages, each with a Markdown copy (10). The docs have one page per operation, such as "Drop a table" and "Delete records", with purpose but no guidance on when not to use them (8). JSON bodies with typed fields, but filters are expression strings (7). Examples in Python and JavaScript on each operation page, and no documented error responses (6). /api/v3 in the path, but the release notes still stop at March 2025 and cover the agent platform, not the database (5). 0 + 10 + 8 + 7 + 6 + 5 = 36.

LanceDB 81

Typed Python, TypeScript and Rust APIs, and the Lance REST Namespace has an OpenAPI 3.1.1 spec in lance-format/lance-namespace. The docs' own Enterprise OpenAPI link, still listed in llms.txt, returned 404 again on 2 November (20 of 25). llms.txt indexes 235 links to Markdown pages (10). The docs explain which index and query type to use for which job, with less on when not to (12). Typed query builders and schemas, but filters are SQL strings (13). Examples on most pages, errors surface as language exceptions with no catalogue (11). Dated GitHub releases with breaking-change and deprecation sections (15).

Agent ergonomics LanceDB +19

Epsilla Vector Database 55

No MCP server for the database. Queries take limit and a response field list to trim results (15). Retrieval takes primary_keys, a filter expression, skip and limit for pagination, and response_fields (20; the 1 October check missed the documented pagination). Error responses aren't documented (5). Upsert by primary key, available since v0.3.4, makes writes safe to repeat, with no idempotency keys or retry guidance, so the fixed line is partly met and keeps its earlier partial (5 of 20; a partial doesn't move to another in-between value, as roma and checkatrade were held). Official Python and JavaScript clients, but databases can only be created in the web console (10). 15 + 20 + 5 + 5 + 10 = 55.

LanceDB 74

No official MCP server, only a 3-tool reference example, so an agent needs code or its own wrapper (15). select(), limit(), offset(), where() and query types to size and filter results (20). Errors are typed exceptions without documented codes (12). merge_insert gives upserts, and writes create new table versions you can roll back to, but there are no tool annotations to read (12). Python, TypeScript, Rust and Java clients, embedded with sensible defaults and nothing to deploy (15).

Security & auth LanceDB +17

Epsilla Vector Database 27

One project API key in the X-API-Key header, with no scopes or read-only variant found. Self-hosted Docker has no auth by default (15). No read-only or least-privilege mode found (0). Stored text comes back as written and we found no prompt-injection guidance (5). No audit log found (0). A "SOC 2 Type 1 Certified" badge on the site, no security.txt, a Vanta trust centre whose host robots.txt closes to all crawlers (unread), and a SECURITY.md in the official Python client naming a reporting address (written "info#epsilla.com") with no acknowledgement time (7, as for cowagent's SECURITY.md with no time). The client's disabled TLS verification is charged once, as the negative. 15 + 0 + 5 + 0 + 7 = 27.

LanceDB 44

The library has no auth of its own and uses the host's object-store credentials. Enterprise takes an API key in x-api-key or OAuth per the 30 September check (20). Least privilege depends on read-only bucket credentials. The library has no read-only mode and we found no RBAC in the Enterprise security docs (5). Tables return stored data as written and we found no prompt-injection guidance (5). No audit log found (0). SOC 2 Type II, HIPAA and GDPR on the Enterprise security page, a trust centre at trust.lancedb.com and a valid security.txt (security@lancedb.com, expires 31 July 2027, re-read on 2 November), but no SECURITY.md, and OSV holds no record for lancedb on PyPI, @lancedb/lancedb on npm or lancedb on crates.io (14). Total 44.

Reliability LanceDB +15

Epsilla Vector Database 60

Better Stack status page at status.epsilla.com with four components, DISPATCH (the API host), ETL, RAG and LLM, each at 100% uptime over 90 days (20). The previous-incidents page reads "No incidents reported" for September, October and November 2026 and the incidents feed has no entries at all, so the page has never posted an incident, which this run scores 20 (the 1 October 25 isn't a checklist value). No rate limits published (0). No 429 or retry guidance found (0). The Epsilla Cloud SLA (last updated 16 November 2023), linked from the terms and the site footer, promises 99.9% monthly uptime with 10% and 25% service credits (10). The cloud vector database is sold as a working product, not a beta (10). 20 + 20 + 0 + 0 + 10 + 10 = 60.

LanceDB 75

Scored as a local package. Official packages on PyPI, npm and crates.io, with Python 3.10 or later and Node 22 or later stated (20). Public CI with Python, Node, Rust and Java test workflows, and the ten most recent Python runs on main all passed, per the 1 October check, not re-read on 2 November (25). 493 open issues on 1 October, but the newest bug reports were mostly filed and labelled by maintainers themselves; the issue tracker wasn't readable on 2 November (15). Releases follow semver for 0.x. Breaking changes bump the minor version and carry a ! marker, 17 such commits across v0.40.0 and v0.41.0, and GitHub release notes have Breaking Changes and Deprecations sections (15). Still 0.x and not declared stable (0). Total 75.

Payments & pricing Epsilla Vector Database +15

Epsilla Vector Database 45

No x402, MPP or L402 (0). Plan prices are public but cover the whole agent platform, with vector storage as a $18 per GB a month add-on (10). Free plan with "No credit card required" (20). A person signs up in the browser, and databases are created in the console (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

LanceDB 30

No x402, MPP or L402 (0). The only paid product, Enterprise, sits behind a contact form (0). The library itself is free with no account or card, which we count as the free tier (20). Getting the paid product needs a sales conversation (0). This is a judgement call, since the rubric scores the paid option and the library is what most users run. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Score by category

CategoryWeightEpsilla Vector DatabaseLanceDBEdge
Reliability16%6075LanceDB +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3681LanceDB +45
Agent ergonomics13%5574LanceDB +19
Security & auth14%2744LanceDB +17
Payments & pricing10%4530Epsilla Vector Database +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%893LanceDB +85
Transparency & trust7%6475LanceDB +11
Negative events≤15-30
TotalE 40.4/100B 66.3/100

Facts side by side

FactEpsilla Vector DatabaseLanceDB
KindHTTP APISDK + MCP
VendorEpsillaLanceDB
Hosted endpointhttps://dispatch.epsilla.com/api/v3no (local only)
TransportsHTTPHTTP
AuthAPI keyNone
PricingFreemiumFreemium
Price for vector search$18 per GB of trafficnot published
x402nono
LicenceGPL-3.0Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2025-11-292026-10-29
Terms last updatedno date givennot read yet
Privacy policy last updated2023-11-16not read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity875 stars12k stars, 922k npm/wk, 1.9M PyPI/wk
Agent reviews1.5/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate LanceDB higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Epsilla Vector Database

GPL-3.0 vector database you can run from one Docker image, with a cloud service under a published 99.9% uptime SLA and documented pagination and upserts. No tagged release since 29 November 2025, no release notes since March 2025, and the Python cloud client still disables TLS verification.

LanceDB

Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.

Before you call either

Epsilla Vector Database

  1. List databases with GET /api/v3/project/{project_id}/vectordb/list, then load one to get its public endpoint
  2. Hybrid search is assembled client-side with as_search_engine().add_retriever(...).set_reranker(type="rrf")
  3. If you use pyepsilla against the cloud, patch or wrap it to verify TLS
  4. Use upsert rather than insert when a write may be retried; it updates by primary key
  5. Ask a person to create the database in the console first. The API can't

LanceDB

  1. Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
  2. Build an FTS index before calling query_type="hybrid", or hybrid search has no keyword side
  3. When reopening a table in a new process, approve its embedding model or endpoint with get_registry().allow_remote_code() or allow_endpoint(), since v0.41.0 refuses settings restored from table metadata
  4. Use select() to drop the vector column from results unless the task needs it
  5. On object storage, set a read consistency interval if several processes write the same table

Questions

Which is better for AI agents, Epsilla Vector Database or LanceDB?

LanceDB scores 66.3 (B) on agent readiness against Epsilla Vector Database's 40.4 (E), and leads in 6 of 7 scored categories. Epsilla Vector Database leads on payments & pricing.

Can an agent call Epsilla Vector Database and LanceDB without installing anything?

Epsilla Vector Database has a hosted endpoint at https://dispatch.epsilla.com/api/v3. No hosted endpoint is listed for LanceDB.

Are Epsilla Vector Database and LanceDB open source?

Yes. Epsilla Vector Database is open source (GPL-3.0). LanceDB is open source (Apache-2.0).

Other comparisons with Epsilla Vector Database or LanceDB

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.