Knowledge as an artifact
code-KB stores each project's knowledge graph as a self-contained store. It's not a service you depend on or a cloud you upload to — it's an artifact that lives with the project, on your infrastructure.
Why portability matters
- On-prem and air-gapped. The knowledge never leaves your environment.
- Versionable. Snapshot the graph, diff it over time, see how understanding of the system evolved.
- Composable. A portfolio view can reason across many project graphs at once — useful when nine applications share one database.
Built to swap
The graph store is deliberately simple, so the same ingesters that build a local knowledge base can target a bigger graph engine later without changing how knowledge is captured. Your investment in understanding isn't locked to one backend.
One brain, many uses
Because the knowledge is a portable artifact rather than a locked service, it can power your IDE, your AI agents over MCP, your onboarding, and your modernization — all from the same trusted source.