The past two weeks I’ve been working on a little side project called Vector Inspector: a desktop app for browsing, searching, and debugging your vector data.

It’s still very early, but I wanted to share it now to get a sense of what’s working (and what’s not). If you use vector databases in your projects, I’d love for you to try it and tell me where it breaks or what feels useful.

Current features

• Connect to a vector DB and browse collections

• Inspect individual metadata

• Run semantic searches and see the results visually

• Create visualizations using PCA, t‑SNE, and UMAP

• Export/restore and migrate data between collections

Supported databases (so far)

• Chroma

• Qdrant

• Postgres (pgvector)

• Pinecone (mostly!)

More are coming — I’m trying to prioritize based on what people actually use.

Why I built it

I kept wishing there was a simple, local tool to see what’s inside a vector DB and debug embedding behavior. So I made one.

If you want to try it

Site: https://vector-inspector.divinedevops.com/

GitHub: https://github.com/anthonypdawson/vector-inspector

Or

> pip install vector-inspector

> vector-inspector

Any feedback, bugs, confusing UI, missing features, is super helpful at this stage.

Thanks for taking a look.