BNLGit
For developers & platform teams

Typed, line-anchored facts for every file — stored as a git mirror your agents can read.

BNLGit sits beside your repo and generates a summary twin for every source file: auth.py → auth.py.llm, carrying structured facts — symbols, imports, endpoints, DB entities, side effects — each anchored to a line and pinned to a blob SHA. It's a real git mirror: diffable, reviewable in PRs, greppable, offline, and consumable by any tool that speaks MCP.

Start free trial → See the executive view
Availability during the public beta

BNLGit is currently offered as a hosted service only — one shared instance, operated by us, with your own model keys. The self-hosted and dedicated-instance deployments described on this page are not part of the beta, and there is no public Lite source release yet.

The product capabilities below are real and are what you get on the hosted service; the deployment models are what changes. If a dedicated or on-premise instance is a requirement rather than a preference, mail hello@bnlgit.com — it changes how we prioritise. See pricing and security and data handling for what the shared beta does and does not isolate.

The mechanic

A summary mirror, versioned right next to the source.

src/auth.py
Your source. Untouched. The source of truth.
src/auth.py.llm
Typed facts · line-anchored · pinned to this blob SHA.
src/auth.py.llmverified_current
# generated fact block — schema v3
symbol   verify_token(token: str) -> Claims   @ L42
  reads    env "JWT_PUBLIC_KEY"
  raises   ExpiredSignatureError, InvalidToken
  security signature checked before payload is trusted   @ L51
endpoint POST /api/session  ->  verify_token          @ L88
db       none
stale?   no  # tracks blob 9f3c1e… ; re-derives on change

Agents retrieve the facts over MCP, then jump straight back to the exact source line at the pinned commit — no re-reading whole files, no stale context, no hallucinated behaviour. When a source blob changes, its twin is marked stale and re-derived; coverage is honest to the SHA.

Why it's different

Built for sovereignty and for machines — not another hosted wiki.

git-native

Summaries are a real repo

Diffable, blameable, mirrorable, greppable, offline. No proprietary index, no vector lock-in — the artifact is git, and it's yours.

typed facts

Structure, not prose

Symbols, imports, endpoints, DB entities, side effects, security notes — a published schema you can query, join across repos, and diff for drift.

self-host · byok

Your keys, your box

Bring your own models. Dial-time SSRF egress control, fail-closed key handling, redacted secrets, zero telemetry. Nothing phones home.

two-tier provenance

Derived vs inferred

Every triage signal is marked deterministic (AST, git, tests) or model-inferred with confidence — so an agent never acts on a guess dressed as a fact.

Built on Gitea (MIT). BNLGit is a commercial code-intelligence layer over an open-source forge — it attaches to the repositories you already have. Your keys, your infrastructure, no telemetry. The .llm typed-fact schema will be published as an open specification.

Start free trial →