Cited or it didn't happen
Every factual claim links to its source, and a groundedness check audits every answer. No source, no number.
Company
The permission-aware answer layer
Braize turns your scattered documents into one knowledge base that is permission-aware, refreshable, and answers — with citations — over the API and to agents via MCP today, with more channels on the way. It is a product of Aize.
Why we built it
Knowledge that is trustworthy by default
Most internal assistants either overshare — surfacing anything a user can technically reach — or hallucinate confidently from stale context. Braize takes the opposite posture: access control is a pre-filter inside the retrieval query, every factual sentence cites its source, and the system abstains when it does not know. Trust is the feature.
78–100%
Retrieval recall by data type (measured per our benchmark)
~1–3s
Typical passage latency range
≤24h
Content + vector purge on delete
1
Region per workspace, pinned
What we stand for
Principles
Permission-aware by construction
ACLs are enforced inside the SQL on every retrieval leg, default-deny — never a post-filter that can leak.
Region-pinned & isolated
One isolated database per workspace, pinned to a region. Embeddings — personal data — never leave it.
Refreshable
Re-ingest a source and its answers update — the cache clears when the document changes. Every document carries a freshness score and a last-indexed status. (Automated change detection is on the roadmap.)
Neutral & multi-channel
One knowledge base, served over REST and to agents via MCP today, with the widget, WhatsApp, and Slack on the way — not locked to one assistant.
Honest about maturity
Our feature inventory labels what is production, partial, or planned. We promote what is real and tested.
Part of Aize
Built by Aize
Braize is built by Aize, the team building the unified workspace to build, automate, and scale AI. Read our writing on the Aize blog.
See Braize on your own knowledge
Connect a source and ask a question on the Free tier — no credit card. Or talk to us about your use case.