For engineering & data leaders
Which of your repositories are finished, nearly finished, or dead?
AI is writing more of your code every quarter — and your repository count is exploding with it.
Half-built services, abandoned experiments, and agent-generated drafts pile up until nobody can say
what is shippable, what is a liability, and what should simply be deleted. BNLGit gives every repo a
verdict, with the evidence behind it, on infrastructure you control.
The portfolio, at a glance
One page. Every repository. A verdict you can defend.
Not a vanity score — a finish-list. Each repo is classed from deterministic signals
(reachability, wiring, tests, migrations, churn) before any model opinion is added, and every claim
cites its evidence.
billing-service
last real commit · 4d ago
Complete
partner-portal
endpoint defined, never wired
Almost
churn-predictor
unreached · untested · stale
Abandoned
plugin-host
dynamic dispatch · needs review
Unknown
Why it holds up in procurement
The four things buyers actually ask you about.
01 · Data residency
Your code stays in the EU
In the beta your repositories sit on hardware we operate in Helsinki, Finland — not a US
hyperscaler. You supply your own model keys, so your code is never routed to an AI vendor we
picked for you. No third-party index, no telemetry. Self-hosting inside your own perimeter is
the next step, and available on request.
02 · No lock-in
The intelligence is a git repo
Summaries are plain, diffable, mirrorable files in git — readable by any tool, and yours forever. They outlive us, and any vendor.
03 · Triage
A finish-list, not a dashboard
"Endpoint defined, never registered." "Model written, no migration." Specific, cited gaps a team can close — or delete — this week.
04 · BYOK economics
No inference markup
You bring your provider keys and pay them directly. BNLGit records cost and provenance — it never resells you tokens at a margin.
Built for regulated work. BNLGit is designed for organisations where GDPR, data residency and
trade-secret containment are non-negotiable. During the public beta your repositories and their
summaries are held on EU infrastructure we operate, and every model call goes to the provider whose
key you supplied — never to one we chose for you. Fully self-hosted deployment, where nothing leaves
your own perimeter, is the next step and available on request. Built on the open-source Gitea project.