Mari connects the tools where your product knowledge already lives, GitHub, Slack, Confluence, Jira, your help center, and turns them into one record your team can ask. Answers come with citations. Facts come with an owner and a freshness date. When a source changes, Mari flags what leaned on it. It runs in your cloud, and it does one job: knowledge.
Run it yourself, or have us run it: in your cloud, or hosted.
Apache 2.0 · 12 connectors · your cloud or ours
12 connectors: GitHub, Slack, Google Drive, Confluence, Notion, Jira, Airtable, Asana, Dropbox, Linear, Trello, and your Zendesk help center. Drop in files too. Mari reads them in place and re-syncs as they change. Nothing to migrate, no new tool for the team to learn.
Search and chat over everything connected. Answers stream with numbered citations back to the doc, commit, or thread they came from, so a support rep or a new hire can check before they repeat it.
Facts carry an owner, a verification state, and a freshness date. Approved answers are the ones your team signed off on. Unsigned assertions show up as exactly that.
A lineage graph ties documents, commits, PRs, and decisions together. When a source changes, Mari flags the facts that leaned on it and routes them to their owner.
@mention Mari in Slack and it answers from the record. @mention it on a GitHub pull request and it checks the change against what's known. Point an MCP client or a knowledge chat at the same record. The agent in the console can tag, approve, sync, and edit, with each action in the audit trail.
A customer asks whether the API supports it. The rep @mentions Mari in Slack and gets the answer with the doc it came from and the PR that changed it. No tap on an engineer's shoulder.
Every support team has a pile of saved replies nobody dates. In Mari an approved answer carries an owner and a freshness date, and gets flagged when the source behind it moves.
Eng cut the feature last sprint. The help center still promises it. Mari flags the fact and routes it to its owner before the next call, not after.
Every "where's the doc for" lands on whoever remembers. Point people at Mari instead. It cites its sources, so nobody has to take your word for it or interrupt your afternoon.
The repo audit scans connected repositories for documentation drift, coverage gaps, and stale pages, and offers one-click fixes that pull the missing docs in.
Each fact carries its source, owner, and sign-off. The security review stops being archaeology: filter the registry and hand it over.
Wikis and search tools store and find what someone once wrote. They can't tell you who owns it, whether anyone checked it, or whether the source has since moved on. Mari does that part, and only that part. If any of these read like your week, it will earn its keep.
Every hard question routes to the engineer who remembers. Their answers are correct, unwritten, and unavailable the week they take off.
Support asks in Slack, engineering points at a Confluence page, product corrects both in a DM. Three answers, none written down, and the customer got the first one.
The wiki holds six stale pages for every good one, and new hires learn to distrust all of them. Search finds all six with equal confidence.
The coding agent, the support bot, the chat in Slack: each one repeats what it retrieved, with no idea whether it's canonical, approved, or two releases old.
What Mari doesn't do
Mari is the knowledge layer, not the whole stack. It won't write your marketing, run your help desk, replace your wiki, or take over your coding agent. It connects to those, keeps the record of what's known, who owns it, and whether it still holds, and hands the answer, with its source, to whatever asks. If your problem is a good corpus that deserves a prettier website, a publishing platform will make you happier than we will.
AI removed the cost of writing. It didn't remove the cost of being wrong.
Mari is the record of what your team knows, org-wide. Three problems it exists to stop, each with a demo below:
tap a problem below to open it
Six months on, nobody knows where a fact came from or whether the source still says it. Once every tool in the company answers questions, "says who" stops being answerable.
Mari pins each fact to the source it came from, the doc, the commit, the thread, the reviewer, and forward to everything downstream that reused it.
A fact with no owner is just a rumor with better formatting.
| Task | Status |
|---|---|
| Verify the new proration rule in the billing runbook | Open |
| Approve the SSO onboarding guide for publish | Open |
| Retire two stale screenshots in auth/README | Done |
| Review the incident escalation ladder | Open |
You answer the same question forty times a week from a saved reply you didn't write, and learn it was wrong when the customer replies with a screenshot.
with mariAsk Mari in Slack and get the answer with its source. Approved answers carry an owner and a date, and get flagged when the product moves on.
You find out on the customer call that the help center promises a feature eng cut two sprints ago. You own what the product says everywhere, and none of the pages.
with mariWhen the product changes, Mari flags the pages that leaned on it and routes the fix to its owner. You stop being the human changelog.
Every question about how it works routes to you, and the doc you'd point at was true two releases ago.
with mariMari cites the doc, the commit, and the PR, so people check the source instead of you. The repo audit finds the pages that fell behind.
You sign off on what the company publishes with no way to see it. Then a security review asks who approved a number, and the answer is a week of archaeology.
with mariOne dashboard over every fact's source, owner, approval, and freshness. The audit trail exists before anyone asks for it.
companies will have shipped generative AI by 2026
of outbound messages will be synthetically generated, per Gartner
trust, risk & security management is a named Gartner priority
Mari is open-source software, Apache 2.0. Run it yourself, have us run it inside your VPC, or have us host it. Your data lives where you decide.
The full security page →A Docker Compose stack with Postgres and pgvector, in your VPC. Local models through ollama are optional, and every feature has a deterministic fallback without them.
Connectors read with tokens you create and can revoke, scoped to what you choose to share. Sources stay where they are: Mari syncs, it doesn't migrate.
Each fact carries its owner, sign-off state, and freshness, and answers cite their sources. A review gets receipts, not recollections.
A custom MSA, DPA, and a security review with your team come with the paid plan.
The dashboard on demo data, no install. Trace a fact, fire a drift event, all from your phone.
Open the demo →02Apache 2.0. Clone, compose up, connect a source. The docs walk through it, and the first cited answer takes about ten minutes.
Read the docs →0320 minutes with us on your rollout, and a full demo on your own sources if you want one.
Book a demo →Mari is Apache 2.0. Run it yourself for free, or have us run it on the enterprise plan, in your cloud or ours. Pricing scales with your team, not your stack.
The open-source product, on your infrastructure. Clone it, compose up, connect a source, and the record is yours to run.
We deploy, run, upgrade, and maintain Mari inside your VPC. Your data and access stay in your account. You get the record without the operations.
We operate the deployment in an environment we run, and your team signs in. Nothing to provision on your side.
Custom procurement, on-prem, or a different shape entirely? Book a call and we'll figure it out.