Run the open-source build free. Pay for the enterprise features and the operations.
Mari is Apache 2.0, and the self-hosted build is free to run yourself. The enterprise plan adds features that aren't in the open-source build and has us run it, in your cloud or ours. Pricing scales with your team, not your stack.
Self-hosted
The open-source build, on your infrastructure. Clone it, compose up, connect a source, and the record is yours to run.
- 12 connectors, cited answers, facts with owners, lineage, and drift audits
- Docker Compose, Postgres with pgvector, optional ollama for local models
- Slack bot and GitHub webhooks, self-serve
- The console and the agent, with the audit trail
- Community support (GitHub)
Bring your own cloud
Runs in your VPC. We deploy, run, upgrade, and maintain Mari inside your cloud account. You get the record without the operations.
- Everything in Self-hosted, plus the enterprise features
- Data and access stay in your account, and you can see and revoke what we reach
Hosted
Runs in an environment we operate. Your team signs in. Nothing to provision on your side.
- Everything in Self-hosted, plus the enterprise features
- Where it runs, who can reach it, and retention set out in the MSA and DPA
Both enterprise shapes come with a dedicated solutions engineer from rollout onward, onboarding for support, product, and engineering, and a custom MSA, DPA, and security review.
Custom procurement, on-prem, or a different shape entirely? Book a demo (opens in a new tab) and we'll figure it out.
Before you pick a shape
- What does it take to run?
- Self-hosted: a Docker Compose stack with Postgres (pgvector included) on infrastructure you control. Add ollama only if you want local LLM answers, and every feature has a deterministic fallback without it. If you'd rather not operate it, the enterprise plan runs it for you: bring your own cloud, where we deploy and run Mari inside your VPC, or hosted, where we operate the deployment and your team signs in.
- Bring your own cloud or hosted: which should we pick?
- Bring your own cloud if your data has to stay inside your account, or procurement already has a VPC story it wants to reuse: we run Mari there, and you can see and revoke what we reach. Hosted if you want nothing to provision: we run the environment, and where it runs, who can reach it, and how long anything is kept are set out in the MSA and DPA. Same product, same enterprise features, same engineer either way.
- Where does our data go?
- Self-hosted: nowhere. Sources sync into the Postgres you run, and the embeddings and answers come out of that same database. Connectors use tokens you create and can revoke. On the enterprise plan, bring your own cloud keeps all of it in your account, and the hosted option runs in an environment we operate, under the MSA and DPA we sign together.
- Is it open source?
- Yes, twice over. Mari is Apache 2.0, and the self-hosted build is free to run yourself: the connectors, cited answers, facts, lineage, drift audits, and the Slack and GitHub bots. Mari Kit, at kit.mari.guru, is the open-source Python toolkit for building a knowledge system of your own, also Apache 2.0. The enterprise plan, bring your own cloud or hosted, adds the operations, a dedicated engineer, and features that are not in the open-source build.
Where the data lives under each shape is on security, and compare has Mari next to a wiki, enterprise search, and a chatbot over your docs.