What is Breno
Breno is an intelligence layer for what an organization knows. What it does, what it does not, and how these docs are organized.
Breno is an intelligence layer for what an organization knows. It brings in the material your team produces (documents, notes, links, meetings, and the tools you connect), keeps each piece together with where it came from, and lets you ask questions of it, with the answer pointing back to its sources.
Its promise is narrow on purpose: your knowledge stays with you. You can capture it, keep it, organize it, retrieve it, understand it, and take all of it with you in open formats.
What you can do with it#
- Capture files, notes, links, voice, photos and meetings, and connect tools such as Slack, Google Drive, Gmail, Notion, GitHub, Jira and Linear. See Capture knowledge and Connect sources.
- Ask a question in plain language and get an answer built from your own material, with numbered citations you can open. See Ask and citations.
- Keep decisions, not just documents: who decided what, when, and why, and the connections between people, projects and other entities. See Memory and decisions.
- Control access with workspaces, spaces and sensitivity labels, enforced by one rule everywhere. See How access works.
- Use it from your AI tools over MCP, or from your own code over the REST API. See Connect AI tools and the API reference.
- Take it with you. Export everything as Markdown, JSONL and your original files, with a checksum for every member, and import it back. See Export your knowledge.
What it is not#
Where it is today#
Breno is early. The core works end to end and is tested against real infrastructure: an upload that becomes searchable, an export you can download and inspect, an account deletion that actually removes the data. Some parts are not finished, and the docs say so where it matters. The page Known limits lists them in one place.