I am very picky, hard to place, but from a quick look at the README, I'd say the API interface on display seemed like the right level of abstraction for having to deal with the messy reality.
Since you're asking for feedback:
- perhaps some of the document type specific dependencies by optional?
- could there be LESS config surface?
- I noticed GitHub CI action has a cross.
It's good to add how to use with Astral "uv" these days, especially anything that might pull in PyTorch dependency hell, which they have mostly solved if used correctly!
Love this kind of feedback, thank you.
You nailed it on optional deps and config sprawl; I’m trimming both. CI cross is just coverage noise, and I’ll add uv setup notes it really cleans up the PyTorch mess.
Glad the API felt right — that was the hardest part to get “just enough abstraction” right.
It’s definitely dense, but not as wild as it looks. The mental model was: take the core building blocks from FAISS and Milvus, make them composable in Python, and expose everything clearly.
The “vibe” part came from trying to make it feel like a system that could run in production, not just a toy. So yeah, it’s a little heavy, but it earned the vibe honestly.
I am very picky, hard to place, but from a quick look at the README, I'd say the API interface on display seemed like the right level of abstraction for having to deal with the messy reality.
Since you're asking for feedback:
- perhaps some of the document type specific dependencies by optional?
- could there be LESS config surface?
- I noticed GitHub CI action has a cross.
It's good to add how to use with Astral "uv" these days, especially anything that might pull in PyTorch dependency hell, which they have mostly solved if used correctly!
Nice work!
Love this kind of feedback, thank you. You nailed it on optional deps and config sprawl; I’m trimming both. CI cross is just coverage noise, and I’ll add uv setup notes it really cleans up the PyTorch mess. Glad the API felt right — that was the hardest part to get “just enough abstraction” right.
how much was this vibe coded? looks cool but its too much for me to digest.
where did you get the original mental model to begin building it?
It’s definitely dense, but not as wild as it looks. The mental model was: take the core building blocks from FAISS and Milvus, make them composable in Python, and expose everything clearly.
The “vibe” part came from trying to make it feel like a system that could run in production, not just a toy. So yeah, it’s a little heavy, but it earned the vibe honestly.
What’s the advantage if this being in python?
The point isn’t raw speed it’s hackability. You can plug in new models or indexing layers in minutes without dropping to C++.
I think the “simple, modular, and extensible” makes this interesting. And for those, it being written in Python are relevant.
Exactly Python makes the whole stack composable instead of compiled shut. That’s where the fun (and flexibility) lives.
PYPI: https://pypi.org/project/valori/
Github: https://github.com/varshith-Git/valori
https://valori-python-vector-db.lovable.app/
dude you already missed the window.
nothing is better than sqlite as a library and don't use high perforamnce as your value for a python product
SQLite’s perfect if you’ve got rows and tables. Valori’s for when you’ve got embeddings and chaos.