BNLGit
BNLGit meets you where your constraints are. Today that is our hosted service; the deployment models below are where it is going. Either way, your agents finally understand the code, and you finally see what's alive across your repositories.
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.
An illustrative scenario, not a customer. A ~60-person firm in a regulated field — legal, accounting, health — with an in-house dev team and code that is not allowed to leave the building. The figures below describe what this deployment model would give them; self-hosted deployment is not part of the public beta.
They want AI coding help, but sending proprietary and client-confidential code to a US cloud is a non-starter for GDPR, Schrems II, and their own client contracts. Onboarding a new dev to the sprawling codebase takes weeks.
They run the BNLGit bundle on a VM inside their own network and point BYOK at their own model endpoint. Typed summaries generate in-house; agents retrieve them over MCP. No code, no summaries, no model calls ever cross the perimeter.
Agents answer with cited, exact context instead of guesses. New hires ramp against a readable, queryable map of the system. And there's a clean sovereignty story that sails through procurement.
An illustrative scenario, not a customer. A ~6-person agency juggling ~40 client repositories on GitHub, with no appetite — or capacity — to run servers. Closest to what the beta actually offers, with one difference: the beta is a single shared instance, not a dedicated one.
Forty repos, constant context-switching, and no one can say which client projects are finished, which are limping, and which are quietly dead. Standing up and babysitting AI infra isn't where a 6-person shop spends its time.
We host a dedicated instance for them. They attach their existing GitHub repos (no migration), and BNLGit builds the summary mirrors and serves them to their agents. Repo Triage grades every project — finished, nearly, or abandoned.
One dashboard across the whole client portfolio, agents that work from real context on every repo, and a predictable monthly bill. Zero servers to run — they ship, we host.
Both are BYOK. You bring your own model keys and pay providers directly — BNLGit records cost and provenance, and never resells you tokens at a margin. And because the summaries are a real git repo, whichever path you pick, the intelligence is yours and portable — no lock-in.