BNLGit ← Home
Business cases

Two teams. Two setups. The same payoff.

BNLGit meets you where your constraints are — run it entirely inside your own walls, or let us host a dedicated instance and never touch a server. Either way, your agents finally understand the code, and you finally see what's alive across your repositories.

Case 01 · Sovereignty-first

The regulated SME that self-hosts.

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.

Self-hosted · BYOK

Meridian & Co. — internal platform team

Fit: Self-hosted Business
The problem

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.

The BNLGit setup

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.

The outcome

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.

0 bytes
leave the network
1 VM
their infra, their keys
days → hoursillustrative
new-dev orientation
100%
audit-friendly, on-prem
Case 02 · Zero-ops

The small dev shop we host.

A ~6-person agency juggling ~40 client repositories on GitHub, with no appetite — or capacity — to run servers.

BNL-hosted · dedicated instance

Northlight Studio — client delivery team

Fit: Hosted Team · $149/mo
The problem

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.

The BNLGit setup

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.

The outcome

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.

~40 repos
one portfolio view
0 servers
for them to run
attach
stay on GitHub, no migration
$149/mo
predictable, unlimited users
Which is you?

Same product. Pick the deployment that fits.

 
Self-hosted
BNL-hosted
Best for
Regulated / sovereignty-critical teams
Small teams that want zero ops
Where code lives
Entirely inside your network
Dedicated instance, isolated per customer
You run
A VM + your own model keys
Nothing — we operate it
Data path
Nothing leaves the perimeter
Your keys; no inference markup
Starts at
Annual bundle licence
$149/mo, unlimited users

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.