GitNexus vs CodeGraph

GitNexus gives an agent the deeper view of a codebase, but CodeGraph is the one most companies can actually install, and the one whose graph stays current without extra work.

By Sheela · Checked Oct 26, 2026 · How we review

GitNexus

3.9/5

Choose GitNexus if your project is personal, academic or open source and you want impact analysis, execution flows, renames and graph queries in one server.

Read our GitNexus review

CodeGraph

4.1/5

Choose CodeGraph if you work at a company, want a graph that updates itself as files change, and prefer a small read-only tool surface.

Read our CodeGraph review

GitNexus vs CodeGraph, side by side
Feature	GitNexus	CodeGraph
Our rating	3.9/5	4.1/5
Price	Free for noncommercial use (PolyForm Noncommercial 1.0.0). Commercial use, managed SaaS and self-hosted enterprise deployments need a licence from Akon Labs; prices are not published.	Free and MIT-licensed. A hosted pull-request analysis platform is in waitlist beta at getcodegraph.com; prices are not published.
Best for	Individual developers, researchers and open-source maintainers on noncommercial projects who want the deepest structural view of a codebase for their agent.	Teams who want their coding agent to answer from an always-current local code graph under a licence their employer will accept.
Licence	PolyForm Noncommercial; commercial use needs a paid licence, price not published	MIT
MCP tools	19 tools, 10 resources and 2 prompts	1 tool by default; 7 more via CODEGRAPH_MCP_TOOLS
Write access	rename can apply edits; cypher runs arbitrary queries; read-only mode by env var	None; every tool reads
Keeping the graph current	Stale without --watch; auto-reindexing is enterprise-only	Watcher re-syncs about 2 seconds after a save; catches up on reconnect
Depth of analysis	Execution flows, clusters, API impact and statement-level data flow with --pdg	Call paths, blast radius, routes for 17 frameworks and affected tests
Languages	18 with registered providers	34 listed, 20 in the Rust kernel
Transport	stdio, or one shared HTTP server on port 3111	stdio, with a shared local background daemon
Data leaving the machine	Local indexing; optional remote embeddings and AI chat send code to your chosen provider	Anonymous usage telemetry on by default; daily update check
Main drawback	Licence keeps it out of most offices	Shallower analysis; large backlog of open pull requests

Both index a repository locally into a graph of symbols and calls, with no LLM, and serve it to coding agents over MCP. GitNexus exposes 19 tools, including previewed renames, raw Cypher queries and data-flow analysis, under a noncommercial licence. CodeGraph lists one read-only tool by default, re-syncs on every save and is MIT-licensed.

The two servers start from the same idea. Both parse a repository locally into a graph of symbols, calls and dependencies, without sending code to a model, so an agent can ask how something works or what a change would break and get an answer in one call rather than twenty rounds of grep. Where they part is how much they hand the agent and on what terms.

GitNexus goes deeper. Its 19 tools cover impact grouped by depth with a confidence score, detect_changes for mapping a diff to execution flows, rename with a preview step, API route tracing and, for indexes built with --pdg, statement-level data flow. CodeGraph lists a single tool, codegraph_explore, which returns source, call paths and a blast-radius summary together; seven narrower tools are hidden unless you enable them. Its maintainer argues one strong tool steers agents better than a menu, and on the README's own seven-repo benchmark, run on Claude Opus 4.8, it reported 88% fewer tool calls and 44% lower cost than an agent without it. Those figures are self-reported, and the same README says CodeGraph leaves about 80% more retrieved text in the context window over a long session.

The licence settles it for most readers. GitNexus is PolyForm Noncommercial, so a company needs a commercial licence even for a pilot, and the price is not published. CodeGraph is MIT. Freshness is the second practical gap: CodeGraph's watcher re-syncs about two seconds after a save, while GitNexus goes stale without --watch and keeps automatic re-indexing for its enterprise offering. Graphify, a similar tool reviewed under GitHub repos, sits between them, Apache-2.0 and broader in what it indexes, but stale after a git pull until updated.

Each has defaults to change. GitNexus writes hooks, skills and context files into your repository unless you pass --index-only, and exposes raw Cypher and applied renames unless GITNEXUS_MCP_READ_ONLY=1 is set. CodeGraph is read-only by design but sends anonymous usage telemetry unless you turn it off, and its backlog of about 400 open pull requests is large. For noncommercial work that needs the deepest structural view, GitNexus is the stronger tool; for everyone else, CodeGraph is the sensible default.

Which should you choose?

The jobs each one is best at, from our reviews.

Pick GitNexus if you are…

A maintainer of a large open-source TypeScript monorepo
See what a contributor's pull request really touches before merging
Check out the branch, run gitnexus analyze --index-only, then have the agent run detect_changes and impact on the diff to list affected flows by depth. Noncommercial open-source use is within the licence and indexing is local, so it costs nothing.
A PhD student studying a legacy COBOL and Java system
Map how a batch job flows through code nobody documented
Index once, browse clusters and processes in the Web UI through gitnexus serve, and use trace to follow the call path between two symbols. Academic research is covered by PolyForm Noncommercial.
An engineering manager at a 50-developer fintech
Decide whether to roll it out to the team
Even a pilot is commercial use, so it starts with a licence enquiry to Akon Labs. For the trial, set GITNEXUS_MCP_READ_ONLY=1 and GITNEXUS_MCP_ALLOWED_REPOS so agents cannot run raw Cypher or apply renames, and expect PR review to need the enterprise tier.

Pick CodeGraph if you are…

A backend developer on an 11,000-file TypeScript monorepo
Stop the agent grepping through dozens of files before it can explain a flow
Run npx @colbymchenry/codegraph once, then codegraph init in the repo, and set alwaysLoad so Claude Code sees codegraph_explore from the first prompt. On the README's VS Code benchmark that cut a question from 28 tool calls to 2; budget for the larger context footprint in long sessions.
A platform engineer at a 30-developer SaaS company
Run only the tests a change can affect in CI
Pipe git diff --name-only into codegraph affected --stdin --quiet and pass the result to the test runner. It follows imports to a depth of 5 by default, so tests reached through dependency injection or reflection can be missed; keep a nightly full run.
An engineering manager rolling an agent out across a team
Give every developer the same code context without a licence negotiation
MIT means no commercial deal, unlike GitNexus. Use codegraph install --yes in the dev-container image and set CODEGRAPH_TELEMETRY=0 there if usage statistics leaving company machines is a concern. The hosted PR product is waitlist-only, so there is no vendor contract to sign or price to compare.