It is Gitea. Plus one thing.

The migration is one command.

BNLGit is not a fork that drifted. It tracks the Gitea codebase, and the additions sit alongside upstream behaviour rather than replacing it. If a thing worked on your Gitea, it works here.

# point the remote at BNLGit
git remote set-url origin git@app.bnlgit.com:your-org/your-repo.git

# ...that's it. Same protocol, same clients, same everything.
# Bringing issues and PRs across? Gitea's own migration tool is inherited unchanged.

Pairing is opt-in, per repository. An unpaired repository on BNLGit is exactly a Gitea repository — no extra cost, no different behaviour, nothing generated.

Everything BNLGit adds, and nothing it doesn't.

Each row below corresponds to a capability the running instance reports at GET /api/v1/bnlgit/capabilities, which needs no authentication. You never have to take our word for what is switched on — ask the server.

The four rows marked + Lite (soon) above are also the planned scope of BNLGit Lite, an AGPL-3.0-or-later, self-hosted edition. It has not shipped yet — see editions and capabilities for the exact plan, or mail docs@bnlgit.com to hear the day it does.

What BNLGit does not do.

You are a technical audience evaluating a tool that puts an LLM near your codebase. The limits are more useful to you than the pitch, so here they are without being asked.

• Source code is always authoritative — a summary never is. The .llm mirror is a derived artefact. Every retrieval path hands back the backing source span alongside the summary specifically so a human or an agent can check it. If the two disagree, the code is right.
• Stale summaries are labelled and down-ranked, never silently trusted. Freshness is tracked per blob SHA. A summary whose source has moved on is marked stale, pushed down the trust ladder, and excluded from results unless you explicitly ask for it. A summary imported without provenance is shown as unverified rather than backdated with an invented model and date.
• Nothing is inferred about your provider, credential or model. Pairing requires you to name the connection and the model explicitly. There is no default, no fallback provider, and no free-text model box — only models the connection's own catalogue returned. If your key stops working, BNLGit stops generating rather than silently substituting something of ours.
• The steward never deletes code on an LLM's say-so. It writes a proposal with evidence, risk and rollback steps. It cannot target your default branch, and it does not commit, push or open anything — a human does. There is no "apply" button that skips review.
• Nothing generates itself by default. Pairing a repository spends nothing. A source change raises a flag; it does not queue work. Generation happens when a person asks for it and confirms an estimate first, and that confirmation is checked on the server, not just in the browser.
• Semantic search is not on for every repository. Vector-ranked retrieval requires an embedding model configured on the pair and indexed chunks for the ref. Where that is not in place, queries fall back wholesale to lexical results and say so in the response. Within one repository it is vector or lexical, not a blended fusion of both. Cross-encoder reranking is off unless an operator turns it on. Read the search page before you rely on this.
• We publish no benchmark numbers. We have not run a comparison we would be willing to defend in public, so we do not quote one. The argument on this page is mechanical — typed, current, line-anchored context is better input than a pile of raw files — and you should test it on your own repository during the trial rather than believe a chart.
• The beta is hosted and shared. One instance, operated by us. Your repositories are isolated by the permission model, not by separate hardware. Instance-level settings are ours to set, not yours. There is no self-serve download and no public Lite source release in this beta, and there is no uptime SLA. The full security and data-handling page spells out what that does and does not mean.

Ask the server, not us. Every capability claim on this page is reported by the instance itself at GET /api/v1/bnlgit/capabilities, unauthenticated. If a page of ours ever disagrees with that endpoint, the endpoint is right and the page is a bug — mail docs@bnlgit.com and we will fix it.

14-day trial, then from $12 per month — billed by repository and storage, never per seat (prices in US dollars). A card is required at signup and is charged when the trial ends unless you cancel — full terms. The documentation is public and needs no account.