Knowledge Graph Engine for Codebases
Hi HN , I built a knowledge graph engine for codebase that is accessible through API . Maintaining codebase , flagging and blocking the stale files along with 78% to 99.74% token savings are some of the main features .
I will be happy to talk about the graph schema, how we stay in sync with git, and overall philosophy of me on the product ?
visit trynovaya.com to use the product !
15 comments
[ 0.23 ms ] story [ 31.5 ms ] threadWe record why each change was made, written back by the agents as they work, so the graph gets better the longer you use it . You can even check out the dashboard that is always in synch with Commits and updates from GitHub and Gitlab .
We especially flag the stale files and code and derank them in internal . So, Graph stays in synch and updated .
Token savings are in range of 78 to 99.74 percent .
API is a source of distribution is much more scalable and comfortable as well especially if user is actively engaging with multiple different Agents Eg you use Claude code ,codex or grok build for a single repository .
I would be eager to know your feedback as well