VecturaDB

VecturaDB is an independent fork of Chroma, under the Apache License 2.0. The original code is copyright Chroma Inc. and its contributors. Independent project. Not affiliated with, endorsed by or sponsored by Chroma Inc. CHROMA is a registered trademark of Chroma Inc., used here only to describe compatibility. We use the name "Chroma" only to say which software our projects work with. It does not mean that Chroma Inc. made, approved or supports them.

VecturaDB is an open-source vector database, compatible with the Chroma API. This repository keeps the full git history of Chroma and its Apache 2.0 license.

Why VecturaDB

Chroma Cloud is winding down: it stops accepting writes on 22 November 2026 and stops serving reads on 22 December 2026. Some features of Chroma exist only in Chroma Cloud and in its distributed version: sparse vectors, the BM25 index and hybrid search. VecturaDB brings them to the single-node database, the one that runs with Docker, as a server, or inside a Python application, so that they stay available to everyone, as open source.

Sparse vectors, BM25, the Search API, hybrid search included, and collection fork work on the single node.

The releases are previews, 1.0.0-preview.N, until VecturaDB has been proven in use; then comes 1.0.0.

Python

pip uninstall -y chromadb
pip install VecturaDB

The VecturaDB package keeps the import name chromadb, so existing code runs as it is.

import chromadb

client = chromadb.HttpClient(host="localhost", port=8000)

While only previews exist, pip install VecturaDB installs the newest preview. Once 1.0.0 is out, a preview needs pip install --pre VecturaDB.

Packages that depend on chromadb

VecturaDB and chromadb install the same modules, so they cannot be installed side by side. Packages that declare a dependency on chromadb, such as langchain-chroma, make pip install chromadb too, and its files replace those of VecturaDB. Install those packages first and VecturaDB last:

pip install langchain-chroma
pip install --force-reinstall --no-deps VecturaDB

• Run the last line again after any command that installs or upgrades chromadb.
• Do not uninstall chromadb afterwards: it removes files that VecturaDB uses.
• A constraints file does not help: pip cannot exclude chromadb and still install a package that requires it.

Docker

docker run -p 8000:8000 -v ./data:/data ghcr.io/vecturadb/vecturadb:preview

Images for amd64 and arm64. preview is the newest preview; every release also has a tag with its version. The data lives in /data.

CLI

Linux (x86_64 and arm64) and macOS (x64 and arm64):

curl -sSL https://raw.githubusercontent.com/VecturaDB/VecturaDB/main/rust/cli/install/install.sh | bash
chroma run --path ./data

Windows (x64), in PowerShell:

iex ((New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/VecturaDB/VecturaDB/main/rust/cli/install/install.ps1'))

The scripts install the newest release, previews included. Every binary is also in the releases. The binary keeps the name chroma.

Moving data out of Chroma Cloud

The CLI copies collections from Chroma Cloud into a running VecturaDB:

chroma login --api-key <your Chroma Cloud API key>
chroma copy --from-cloud --to-local --host http://localhost:8000 --db <database> --all

To copy only some collections, use --collections <name> once per collection instead of --all. The collections must not exist yet in VecturaDB.

The copy stops at the first collection it cannot create. The collections copied before it stay in VecturaDB: copy the rest with --collections. Collections whose metadata holds the legacy hnsw:* settings fail with Cannot set both collection config and schema simultaneously; Chroma gives the same error.

What arrives: every record with its document, metadata, embedding and URI, the metadata of the collection, and its schema, sparse and BM25 indexes included. Sparse and BM25 searches give the same scores as on Chroma Cloud. The settings of the dense index do not arrive: Chroma Cloud uses SPANN, VecturaDB uses HNSW with its default settings.

Clients

A client that needs to know which server it talks to reads GET /api/v2/pre-flight-checks. VecturaDB answers with the fields of Chroma and adds a server block, for example:

{"max_batch_size": 5461, "supports_base64_encoding": true, "server": {"name": "VecturaDB", "version": "1.0.0-preview.N", "features": ["sparse_vector_index", "bm25", "search", "fork", "api_keys"]}}

features lists what VecturaDB has beyond single-node Chroma:

• sparse_vector_index: sparse vector indexes in the schema of a collection;
• bm25: sparse indexes with BM25 scoring;
• search: the Search API, hybrid search included;
• fork: collection fork and fork count;
• api_keys: API keys, as on Chroma Cloud.

With API keys, only a request with a valid key gets the block. Chroma does not send the block, and the clients of Chroma ignore it. GET /api/v2/version answers 1.0.0, as Chroma does.

Telemetry

Telemetry is off by default. Setting ANONYMIZED_TELEMETRY=TRUE turns on the anonymized telemetry inherited from Chroma (PostHog, Python package only). The server binary sends none.

License

Apache License 2.0: see LICENSE and NOTICE.