Practical overview
When it fits
Use it when you need a visual administration and exploration interface for a ChromaDB instance, particularly for collection maintenance, record inspection, metadata-filtered browsing or search.
Who it is for
- Developers who administer or inspect ChromaDB collections and records.
- Teams that want a visual interface for search, metadata filtering, bulk record changes or CSV export.
Documented uses
- Browse, create, rename, clone or delete Chroma collections.
- Search records, build metadata filters and apply bulk record actions.
- Inspect and edit documents, metadata and embeddings.
- Run semantic text queries or nearest-neighbor search with raw vector JSON.
- Add or upsert records and export the current table view as CSV.
Requirements & limits
The project documents a deployed GitHub Pages interface, local Vite use and Docker Compose deployment. It is open source under the MIT license.
- The Chroma server must use the Chroma v2 API.
- Connection details include a server URL, tenant and database.
- Semantic query and automatic embedding generation can use OpenAI or Ollama.
- CORS configuration may be needed on the Chroma backend for the chosen frontend origin.
- The project is a Vue-based application and can be run locally or with Docker Compose.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Run the UI locally with Vite
Start the ChromaDB UI development server on the documented local address.
Before you start
- A cloned ChromaDB UI repository
- npm
Steps
Clone the repository with git clone https://github.com/BlackyDrum/chromadb-ui.git.
Install dependencies by running npm ci in the repository.
Start the development server with npm run dev.
Expected outcome
The app runs at http://localhost:8090 by default.
Guide limitations
- The UI works only with the Chroma v2 API.
- A Chroma backend must allow requests from the frontend origin if CORS errors occur.
Start the UI and ChromaDB with Docker Compose
Launch the UI container, ChromaDB, or both through the repository's Docker Compose configuration.
Before you start
- Docker installed and running
- The repository's docker-compose.yml
Steps
To start only ChromaDB, run docker compose up -d chromadb.
To start only the UI container, run docker compose up -d --build chromadb-ui.
To start ChromaDB and the UI together, run docker compose up -d --build.
Expected outcome
The UI container serves the production build at http://localhost:8090.
Guide limitations
- The UI works only with the Chroma v2 API.
- If CORS errors occur, configure the Chroma backend to allow the frontend origin and restart the containers.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- BlackyDrum/chromadb-ui · Official homepage title · retained in its source language

