louvain turns Slack, Teams, Drive and your CRM into a live, permission-aware knowledge graph. Every answer is scoped to the person asking — and never anything more.
Free to self-host · runs entirely in your VPC
Switch viewers and watch the same answer change with clearance.
That’s why security blocks the rollout, and why the AI budget sits idle. The fix isn’t a better assistant. It’s a memory layer where permissions are physics, not filters.
Permission-aware answers
Every fact inherits the permissions of the place it was said. A claim built from a private channel and a shared doc is visible only to people who can see both — intersection semantics, enforced in the graph itself.
Live revocation
Membership changes ride the same pipeline as messages. When access is revoked at the source, it’s revoked in every AI answer — within a published SLO we benchmark on every commit.
Total recall, with receipts
louvain stores typed, sourced claims, not text chunks. Beliefs supersede each other without erasing history, so decision audits, disputes and board prep become a single query.
How it works
Slack today, and any source that can POST — one open event contract.
A local LLM gate decides what's knowledge-worthy. Zero API cost.
Typed, sourced, bi-temporal claims with full provenance.
Tuples sync from your source systems into SpiceDB.
MCP and API, scoped per person. Every claim cites its source.
Security
louvain exists because security teams keep blocking AI rollouts — for good reasons. So it’s designed to survive their review.
Self-hosted with docker compose. Your messages, documents and permissions never leave your cloud.
The engine is MIT-licensed — including the permission layer. Your security team reads the code instead of trusting a vendor deck.
Access derives from what you already administer: channel membership, doc sharing, record ownership. Nothing new to misconfigure.
Claims cite the exact message or document they came from. “Why did the AI say that” always has an answer.
Create a workspace, connect Slack, and ask your first question in about two minutes. Or run the whole thing inside your own network — same code, same permissions.