Mari
Mari is the product knowledge platform. It reads the places your team already writes, keeps one searchable copy of what it knows, and shows which parts have an owner, a source, and a recent check behind them.
Where a search tool stops at ten links, Mari carries on:
- Which of these assertions still holds? Facts have owners, a verification state, and a freshness date.
- Where did this answer come from? Answers cite the document, commit, or thread they came from.
- What changed, and what did it break? A lineage graph ties documents, commits, and decisions together.
- Now put it to work. Curated knowledge goes back out through chat destinations, MCP servers, and bots.
How it fits together
Sources are ingested on a schedule or by webhook, chunked, hashed, and embedded. Unchanged content is never re-embedded, so re-syncing a repository that has not moved costs almost nothing.
Retrieval is hybrid: Postgres full-text scoring and pgvector cosine similarity over the same chunks, weighted by the tags you apply. Answers stream with numbered citations.
An agent sits on top with the same permissions you have. It can search, read and edit documents, tag, manage facts and answers, trigger a sync, and move the console around you. Every action it takes lands in the audit trail.
How you can run it
Mari is open source under Apache 2.0, and the open-source build is free to run yourself: a Docker Compose stack with Postgres (pgvector included), plus ollama if you want local models. Every model-backed feature has a deterministic fallback.
The enterprise plan runs it for you, two ways:
- Bring your own cloud. Mari deploys, runs, and maintains the product inside your VPC. Data and access stay in your account.
- Hosted. Mari operates the deployment, and your team signs in.
The enterprise plan also carries features that are not in the open-source build. Data handling for either option is set out in the MSA and DPA you sign. Talk to us if you want it run for you.
Where to start
Then one guide per thing:
And the reference pages:
About these pages
This documentation is new and does not yet cover every screen. Pages are written against the code they describe, so what is here is accurate, but the set is not complete. The console reference lists every screen, including ones without a guide yet.