@bluenotelogic/harness
Apache-2.0
The setup CLI. One command points a machine at your memory service and writes a tokenless MCP config. Published on npm; run it today without an account of any kind.
Read about the CLI →Open source
One is out. Two are coming. Here is which.
We open-source the parts that let you adopt our tools without a contract, verify our claims without trusting us, and leave without being trapped. This page is the honest ledger of what has actually shipped — and what has not.
The ledger
What is released, and what is still on the way.
caveauMEM public core
Apache-2.0
Documentation, SDK and provider examples, a local demo, and the community-safe runtime pieces of the memory service. Enough to build against it, run it locally, and understand what it does with your data.
Read about caveauMEM →BNLGit Lite source release
AGPL-3.0-or-later
The Lite edition of the forge: core Git hosting, repository pairing and sync, the Sync Cockpit, the drift signal, and lexical search. Tied to BNLGit reaching general availability rather than to a calendar quarter, because that is the honest way to date it.
Read about BNLGit →Why we do it
Open where it earns trust, commercial where it funds the work.
We are a small company with a real payroll. Open core is not a philosophical position here — it is the arrangement that lets us keep building while you keep your options.
Adoption
The on-ramp should not need a contract
The piece that wires your machine up is the piece most likely to be run on a laptop before anyone has spoken to us. That piece is free and open, and it always will be.
Verifiability
Claims you can check yourself
We say the harness writes no credential into your repository. Open source is how you confirm that rather than take our word for it.
Exit
An open core is an exit route
Sovereignty means little if leaving is impossible. An open Lite edition and an open memory core mean the floor under you is not ours to remove.
Honesty
Unreleased is labelled unreleased
Two of the three rows above have not shipped. They are badged as planned everywhere they appear on this site, and a pre-publish check blocks any page that describes them in the present tense.
Licences
Which licence covers what.
| Component | Licence | Notes |
|---|---|---|
| Upstream Gitea / Gogs | MIT | Notices preserved verbatim. BNLGit is an independent product and is not affiliated with or endorsed by Gitea Ltd. |
| BNLGit Lite modifications | AGPL-3.0-or-later | The Lite edition's changes to the upstream tree. Not yet released — see the roadmap above. |
| BNLGit Pro bundle | Proprietary | The BNLGit Pro EULA, plus third-party notices. Licences are Ed25519-signed tokens; an instance can report its own licence status. |
| @bluenotelogic/harness | Apache-2.0 | Released. Source and package published; no account needed to use it. |
| caveauMEM public core | Apache-2.0 | In preparation. The commercial service around it stays proprietary. |
Start with the part that is already free.
The harness CLI needs no account, no card, and no conversation with us. Run it on a scratch repository and see what it writes.