Skip to main content

langchain-chassisdb

A LangChain vector store on Chassis: semantic search over your documents, kept in two files, inside your own process. No server to run, nothing to connect to.

pip install langchain-chassisdb
from langchain_chassisdb import ChassisVectorStore
from langchain_openai import OpenAIEmbeddings  # or any LangChain embeddings

store = ChassisVectorStore("docs.chassis", embedding=OpenAIEmbeddings())
store.add_texts(
    ["Refunds take five working days.", "We ship to the EU and the UK."],
    metadatas=[{"topic": "billing"}, {"topic": "shipping"}],
)

retriever = store.as_retriever(search_kwargs={"k": 4, "filter": {"topic": "billing"}})
retriever.invoke("how long does a refund take?")
  • Files: docs.chassis holds the vectors and docs.db the documents and metadata. Open the same path again, with the same embeddings, to pick up where you left off. Everything added or deleted is saved when the call returns. A call that a crash or an error stops changes neither file: the store brings its vectors back in step when it is next opened or written.
  • Ids: give your own with ids=; adding a document with an id that is stored replaces it. get_by_ids and delete take them.
  • Filters: filter={"key": value, ...} keeps documents whose metadata has every key with that value.
  • Scores: similarity_search_with_score gives distances (smaller is closer); similarity_search_with_relevance_scores gives 0 to 1. max_marginal_relevance_search picks documents that are close to the query and different from each other.
  • Options: metric="cosine" (the default) or "euclidean"; precision="half" keeps vectors in about half the space, with the same recall on the embeddings measured. They're fixed when the store is created: open it again with the same ones, or an OptionsMismatchError says which to pass. A read_only store takes them from the file.
  • More processes: one process writes a store at a time. Others open it with read_only=True, take no lock, and see what the writer last saved.

It passes LangChain's standard tests for vector stores, sync and async.

Metadata

Release files for langchain-chassisdb 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for langchain-chassisdb 0.1.1
File Size Uploaded
langchain_chassisdb-0.1.1.tar.gz 13.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for langchain-chassisdb 0.1.1
File Interpreter ABI Platform
langchain_chassisdb-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 25.8 kB

Release files / langchain_chassisdb-0.1.1.tar.gz

Download URL langchain_chassisdb-0.1.1.tar.gz
Size 13.2 kB
Tags Source
SHA-256 checksum
How to use checksums
d3f6de5d31cca3f113279c2788d680720038e6a182dec4b321b643568a7c015f
BLAKE2b-256 checksum
How to use checksums
6950c4005e3683ac822e7344a000c8ff1098172dc3835b01bfd492d8583d46b4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / langchain_chassisdb-0.1.1-py3-none-any.whl

Download URL langchain_chassisdb-0.1.1-py3-none-any.whl
Size 12.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
02c92a00722fb807ccefcd5aad5bb581f323790cb853203ed7f2606dd357280d
BLAKE2b-256 checksum
How to use checksums
a62827a9ca86da97689489753180ca0eefe2149c30320f8d81e6ac0bfb2acd07
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.2

2 release files

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page