GitNexus Review (2026): Pricing, Features & Honest Verdict

GitNexus indexes your codebase into a knowledge graph and serves it to coding agents over MCP, replacing grep with resolved call chains and blast-radius analysis. The benchmark is real and the engineering is excellent. The word “open source” in the tagline is not. Best for: teams running coding agents across many repos. Price: From $29/seat/mo (free plan: yes, noncommercial only). Rating: 7/10

What is GitNexus?

GitNexus launched on Product Hunt on 27 August 2026 at #8 for the day with 113 upvotes. It is built by Akon Labs, a Y Combinator S26 company, and the idea is simple to state and hard to build: your coding agent sees files, not systems. A real codebase is tens of thousands of symbols tangled across packages and repos, and an agent that greps its way through it misses dependencies, breaks call chains and ships blind edits.

So GitNexus parses every file with Tree-sitter and resolves imports, call chains, field types and return types with static analysis, producing a graph rather than an embedding. Their own example: one pass over microsoft/vscode yields 262,322 symbols and 1,030,565 relationships. Leiden community detection then clusters those symbols into functional modules with cohesion scores, so the auth flow and the billing engine get discovered rather than documented. Agents query it through seven MCP tools, including query, context, impact, detect_changes, rename and a raw cypher escape hatch. The public repository sits at 45,895 GitHub stars and the npm package has moved 205,374 downloads in the last month.

What Are GitNexus’s Key Features?

A benchmark that argues against itself

Most launch-day benchmarks are cherry-picked. This one comes with a caveat the company wrote itself. On DeepSWE, across 113 tasks, 89 projects and 3,471 trials, a bare model solved 37.0 percent of issues and the same model with GitNexus solved 68.4 percent. That is a 31.4 point gain, or 1.85 times the solve rate, on 10.6 percent fewer steps and $0.88 per solved task against $1.79. The caveat is on the page: DeepSWE is single-issue solving and cannot exercise multi-repo graphs, impact analysis or taint tracking at all, which is what the product is actually for. Publishing the trial count and then telling you the benchmark understates your product is not normal behaviour, and it is the main reason we trust the number.

Blast radius before you edit, not after review

Change one function and GitNexus traces every downstream caller, grouped by depth with confidence scores. Their worked example: one change, 47 affected symbols across three depth levels, six execution flows. The detect_changes tool maps a git diff to the affected execution flows before you commit. This is the feature that justifies the graph over embeddings, because similarity search cannot answer “what breaks” and a resolved call graph can. The example they lead with, user.address.getCity().save() resolving at every hop, is exactly where vector search loses the thread after one jump.

Cross-repo edges in one unified graph

Group repos together and cross-repo edges connect your API to its consumers, so a breaking change in one service surfaces in every dependent repo. Their demo on the trpc org spans three repos and 1,816 cross-repo edges. If you run microservices, this is the whole pitch, and it is the capability the DeepSWE benchmark cannot measure. It is also gated behind Enterprise, which we will come back to.

Local by default, and broad agent support

The open-source engine indexes, stores and queries entirely on your machine. Nothing leaves your network. It works with Claude Code, Cursor, Antigravity, Codex, Windsurf, OpenCode and anything MCP-compatible, with the deepest integration on Claude Code, which gets MCP tools plus agent skills plus hooks that enrich grep and file reads with graph context automatically. There is a browser web UI with zero install. Language support is where the marketing trips over itself: the pricing card says 13 languages via Tree-sitter, while the FAQ two screens below names 17, including COBOL through a dedicated standalone processor. The FAQ is the accurate one. Understating your own coverage is a forgivable sin, but it is still a contradiction on a single page.

How Much Does GitNexus Cost?

Three tiers. GitNexus OSS is listed at $0 forever for individual developers. Enterprise is $29 a seat for the managed SaaS, adding automated PR review with blast-radius analysis, multi-repo unified graphs with cross-repo impact, auto-reindexing on every commit, an auto-updating code wiki and dedicated support. Self-hosted is custom pricing for teams whose code cannot leave the network, adding air-gapped deployment, SSO and access controls. There is a fourth card, Nexus Agent, which is a private beta with a waitlist and no payment.

The $0 card needs an asterisk that the pricing page does not put on it. The footer of that same page reads “GitNexus OSS is PolyForm Noncommercial 1.0.0”, and the npm package declares the same licence. PolyForm Noncommercial is not an OSI-approved open source licence, and GitHub itself classifies the repository’s licence as “Other”. The FAQ, once you expand it, is honest: “The engine is open source under PolyForm Noncommercial 1.0.0, free for personal and noncommercial use. For commercial use, and for the managed SaaS or self-hosted Enterprise platform, reach out to founders@akonlabs.com.”

Read that against the tagline, “The open-source kernel for coding agents”, and against a free card addressed to “individual developers”. An individual developer working on their employer’s code, or on their own commercial product, is not covered by that $0. There is no self-serve commercial licence at any price. The only route is $29 a seat with a “Talk to founders” button next to it. That is a legitimate business model and plenty of good tools use it, but calling it open source at the top of the page and burying the restriction in an accordion at the bottom is the kind of thing that costs a company trust it did not need to spend.

On price alone, $29 a seat is competitive. At $348 a seat per year it matches Sourcegraph’s $16,000 entry point at about 46 seats, so smaller teams are far better off here. What is missing is any published detail on what a seat includes, whether indexing volume is metered, and whether the private-beta Nexus Agent will cost extra when it ships.

Who is GitNexus Best For?

Use GitNexus if you run coding agents across more than one repository and you have watched them confidently edit something without noticing three downstream callers. Cross-repo impact analysis is the feature nobody else packages this cleanly, and the graph approach is right for the job.

Use GitNexus if you are on Claude Code specifically. The hook integration that enriches every grep and file read with graph context is a deeper hook than the other editors get, and it means the tool works without you remembering to invoke it.

Use the free engine if you are a hobbyist, a student, or working on a noncommercial open source project. It runs locally, indexes 17 languages and costs nothing, and for that audience the licence restriction never bites.

Skip GitNexus if you were planning to adopt the free tier at work. You cannot, and finding that out after you have wired it into a team workflow is worse than finding out now. Budget $29 a seat or do not start.

Skip it if your codebase is a single small repo. The graph pays for itself on scale and tangle. On a 40-file service, grep is fine and the indexing step is overhead.

Best GitNexus Alternatives

Greptile is the closest thing to a direct competitor with real self-serve pricing. Starter is free for one active developer with unlimited repositories and 50 credits a month, Pro is $30 a seat per month with 50 credits included per seat and $1 per additional credit, and Enterprise is custom with a self-hosting option. It is free for qualified MIT or Apache open source projects and half price for pre-Series A startups under $2M in revenue. Greptile is a code review product rather than a context layer, so it answers a narrower question, but its free tier is unambiguously free.

CodeRabbit is the best-funded option, having raised $143M. Pro is $24 per user per month billed annually, Pro Plus is $48, a separate security product is $40, and the Slack agent bills at $0.50 per agent minute. There is a 14-day trial on everything and a free plan for public repositories. Again this is PR review rather than an agent context kernel, but the budget comes out of the same line item and the free public-repo tier carries no commercial restriction.

Sourcegraph is the enterprise incumbent for code search and navigation, with Deep Search, an MCP server and agentic batch changes. It is Enterprise-only and starts at $16,000, including credits for AI features and scaling with team size. If you have hundreds of engineers and a compliance department, this is the safe answer. If you have twelve, GitNexus costs $4,176 a year for the same seats.

Final Verdict: Is GitNexus Worth It?

The technology here is the real thing. Deterministic graph resolution beats embedding similarity for structural questions, the Leiden clustering is a smart way to discover architecture nobody documented, and blast-radius-by-depth is a feature every team with microservices will want the moment they see it. The benchmark is reported with trial counts and a self-authored caveat about its own limits. The repository has 45,895 stars and 5,072 forks, the npm package ships constantly, and the whole engine runs locally so your code stays put. On engineering, this is an easy recommendation.

Two things hold the score at 7. First, the licence. Marketing a PolyForm Noncommercial product as “open source” with a “$0 forever” card aimed at individual developers is misleading in the one direction that matters, because the people most likely to try it are developers at companies who are not licensed to. Say “free for noncommercial use” on the card and the problem disappears. Second, the headline 1.85x figure appears on the Nexus Agent card, and it is the same 68.4 against 37.0 the MCP server already produces, so it is not evidence about the agent you are joining a waitlist for. Fix the licence copy and GitNexus is one of the better developer tools launched this year. Until then, read the FAQ before you install it at work.