introducing Jevbox: an open-source document drive that organizes itself, answers questions, and…
@kushalbyatnal8K followers
180,401 views
31 Comments
Comments from the original post on X (Twitter)

@kushalbyatnal
open source repo here:
21 likes

@michael_chomsky
where can i try this?
3 likes

@doyc_1
Cool. Jev is solving retrieval problems
3 likes

@kushalbyatnal
if you squint, everything is a classification problem
7 likes

@eSaadster
gh repo?
2 likes

@kushalbyatnal
here you go:
1 like

@brexton
Insane
2 likes

@kushalbyatnal
@andrewlu0 is insane
2 likes

@dchow_
@ameyaajoshi the use cases with extend + jev are crazy
2 likes

@JoshKaplanc
cool
1 like

@firatcand
this is cool, organizing folders is a pet peeve of mine. I really don't enjoy it. Notion could use a similar approach honestly. Cool use case for Jev, I have been building a tool router for machine payments with Jev it's quite interesting. Will launch soon too.
1 like

@0xsael
no vector db is the real flex here, cant wait to stress test the hierarchy
1 like

@IndicGames
@theo I recall you doing something about file organisation and files not needing to be at one exact path. This seems like the most natural evolution of that ideao.
1 like

@singularity_bly
I’d use GLiDE for the folder → document → section choices. It beats Jev on Decision Index retrieval, 60.9 vs 55.4, and can reason further when two paths look plausible. That’s worth testing on the same document library.

@salesoptecs
The filing is the easy half. What actually breaks document search in a real company is that the drive holds three versions of the same policy and nothing marks which one is current. A citation only helps if somebody decided that page was still true.

@highrthanthesun
Looks interesting

@Mildo_ai
Is this a different kind of vector database? What’s the benefit over graphrag?

@kartikb753
Retrieval-time permission checks are the part most RAG stacks get wrong, cached chunks serve after access is revoked. The failure I would eval first is miscategorization, a misfiled doc goes invisible to hierarchical search. AI engineer working on agent harnesses and evals.

@imfarzanansari
people here are doing crazy things!

@JohannesLaslo
what problem does this solve? Is this advantageous to a local wiki style knowledgebase with vector database?










