Practical overview
When it fits
Use LynseDB when a Python application needs vector or similarity retrieval and you want a documented path from a local embedded database to shared HTTP access or a lightweight sharded cluster.
Who it is for
- Python developers adding retrieval to AI applications
- Teams building RAG or document question-answering systems
- Developers implementing semantic search, agent memory or recommendation features
- Applications that need to move from single-process embedded storage to shared service or cluster access
Documented uses
- Store vectors alongside stable IDs and metadata, then retrieve relevant records by similarity.
- Filter or combine retrieval using metadata, BM25, dense or sparse vectors, and hybrid search.
- Return stored fields as grounded context for an LLM.
- Search non-embedding data such as coordinates, binary fingerprints, numeric profiles or probability distributions.
Requirements & limits
The repository is public and identifies the project as Apache-2.0 licensed. Python 3.9 or newer is required. The README lists Linux, macOS and Windows native support.
- Embedded mode is for one Python process owning the data directory; use the HTTP service when independent processes need shared access.
- The same Python client is documented for embedded, HTTP service and cluster modes.
- Document-based insertion and search can use the optional local embeddings adapter; existing vectors can instead be passed directly.
- The README distinguishes logical commits from checkpoints and recommends checkpoints for specified durability-sensitive operations.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build a small document retrieval collection
Store knowledge snippets with metadata and retrieve a matching result using a question and metadata filter.
Before you start
- Python 3.9 or newer
- The LynseDB Python package
- Install the optional embeddings adapter with
pip install "lynsedb[embeddings]"when using document-based insertion and search with local embeddings
Steps
Install LynseDB and, for local document embedding, its optional embeddings adapter.
Create a
VectorDBClientwith a local data directory, then create a database and collection.Add documents with stable IDs and metadata fields inside the collection context.
Search with a question, a result count and a metadata filter; request returned fields and inspect the results.
Expected outcome
A local collection returns matching stored fields that can be used as context for an LLM.
Guide limitations
- The example uses local embedded storage; multiple independent processes should not share the same embedded data path.
- For production, choose and version the embedding model, or pass vectors directly if embeddings are already generated.
- The README recommends checkpointing before backups, snapshots, controlled shutdowns or critical durability acknowledgements.
Compare options for Vector search
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Lynsedb | Store vectors alongside stable IDs and metadata, then retrieve relevant records by similarity. | Cloud, Linux, macOS, Self-hosted | The repository is public and identifies the project as Apache-2.0 licensed. Python 3.9 or newer is required. The README lists Linux, macOS and Windows native support. |
| Mettis | Index text documents through an HTTP endpoint. | Linux, Self-hosted, Server |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- BirchKwok/lynsedb · Official homepage title · retained in its source language

