About
Not a place to write things down, and not a search box over a folder. Breno keeps the material an organization produces, keeps it tied to where it came from, and treats being able to leave as a feature rather than a concession.
- Earlythe core works end to end
- Open formatsMarkdown and your original files
- Yours to runon your own infrastructure if you want
What Breno is
Every organization already knows a great deal. It is in documents, in meeting notes, in decisions that were argued out once and then half-remembered. Most of it is not lost so much as unreachable: present in the building, absent at the moment somebody needs it. Breno is the layer that holds it.
It keeps
Uploads, notes, links and the sources you connect, brought into one place.
It connects
Every passage keeps its provenance: which document it came from, who wrote it, when, and what else it relates to.
It retrieves
Search returns passages, not answers alone, so what you are told can be checked against where it came from.
What it is not
A chatbot
Asking a question is one way in. The point is what the system holds, not the conversation in front of it.
A notes app with a search box
A folder of files does not know what a decision was, which document superseded it, or that the two are related.
A black box
Answers are built from retrieved passages that carry their citations. Where the evidence is not there, it says so instead of guessing.
A lock-in
This is the part worth reading. See the next section.
The part that matters most
A memory system is only useful if using it does not cost you the thing it is holding. So the ability to leave is not a settings-page afterthought; it is one of the two things the product is being built around.
› sha256sum -c checksums.sha256One archive, and it is documented
Items with their metadata and relationships, the full text of every item and its superseded versions as Markdown, your original uploads byte for byte, and a checksum file so you can verify you got all of it. It is meant to outlive the product.
It goes both ways
The same archive can be read back in, so a workspace can move between instances; the round trip is a test rather than a hope. Import also reads an Obsidian or plain Markdown vault and a Notion export, auto-detecting which it has been given.
Self-service, same shape
No request form and nobody to ask. Delete an item, or your whole account, from inside the product.
How it is built
A few rules the code enforces, because they decide whether a memory layer can be trusted.
One rule for every read and write
Not a check per feature: one shared rule, in one place, that every path must pass through.
Tenancy is the database’s job
A query that forgot to scope itself to a workspace still cannot return another workspace’s rows.
No model decides access
Who may read what is decided by rules, not by a language model’s judgement.
No fake functionality
Every control works end to end or does not exist. A missing credential is an honest refusal, never a plausible-looking success.
You can run it
Operate it on your own infrastructure, with a model on your own hardware if you want one. An instance you run sends nothing you have not configured.
There is a public API and a Model Context Protocol server, so the same knowledge can be reached from the tools you already work in: search, fetch, capture and export, over the same access rule that governs the interface itself.
Where it is now
Early, and it works end to end
Tests run against real infrastructure: a real upload that becomes searchable, a real export downloaded and inspected, account deletion proved by the sign-in stopping.
The load test with a thousand connected sources failed its latency budget: scheduling lag at the 95th percentile ran over. Throughput held, and every connection completed all four syncs. That is why a thousand is written as a target. The changelog has the detail, including the parts that did not go well.
Who runs this
Operated by [to be supplied], of No 6A, Old CBN Road, After House Of Assembly, Jos, Plateau State, Nigeria. Breno can also be self-hosted, in which case the operator is whoever runs it and the responsibility for your data is theirs.
How to reach somebody is on the contact page, and what is done with your data is in the privacy notice.