Security

Security is the architecture,
not an afterthought.

GitNexus was designed around one constraint: your code never has to leave your network. Everything else follows from that.

Your network
Your repossource of truth
GitNexus engineparse · cluster
.gitnexus/ graphlives beside the repo
Your agentsmcp · queries
index · storage · queries · all inside
Public internetzero code egress
Fig. 3.1: every byte stays inside your perimeterdelete .gitnexus/ and the graph is gone. that's the whole uninstall.

How we think about security

Most tools ask you to send your code somewhere and trust what happens next. We built GitNexus so you never have to. The strongest security posture is the data that never leaves.

Local-first by architectureIndexing, storage, and queries run where your code already lives. Privacy is not a setting you enable; it is how the product works.
The graph lives beside the repoEverything GitNexus knows sits in a .gitnexus/ folder next to your code. You can inspect it, back it up, or delete it. No hidden state anywhere else.
No code telemetryWe never see your source. There is no phone-home, no snippet sampling, no usage payloads carrying code. Your codebase is not our training data.
Open source and auditableThe engine is public on GitHub. Your security team does not have to trust our word; they can read the code that touches yours.
Air-gapped readyGitNexus makes zero external calls by design, so it runs in fully offline environments without a special build or a feature flag.
Your models or oursPoint GitNexus at your own model endpoints, inside your own network. Nothing about the architecture requires our infrastructure in the loop.
How we operate
01
We dogfood our own blast radiusEvery change to GitNexus goes through GitNexus. Impact analysis runs on our own pull requests before they merge, so regressions surface as graph diffs, not incidents.
02
Least privilege, smallest surfaceThe engine asks for read access to the code it indexes and nothing else. No shell hooks it does not need, no background daemons, no credentials harvested along the way.
03
Honest scope, in writingWhat the product reads, where it writes, and what would happen if you ripped it out are documented and verifiable in the open source code, not buried in a policy PDF.
Found something?Tell us directly.If you believe you have found a vulnerability in GitNexus, email the founders and we will respond quickly, work with you on a fix, and credit you if you want it.
Report an issue