What Louvain is
Answers your firm can stand behind — cited to the source and limited to what each person is cleared to see — in the app, through the API, and in the AI assistants your firm connects over MCP.
The answer to a client's question is usually somewhere in the firm already: a mail thread from March, a working paper nobody linked, a note in a Slack channel.
Louvain connects those sources and answers questions from them, with the sources attached and every figure, date and name checked against them. Partners and client teams ask in the app; the AI assistants they already use — Claude, Claude Code, Cursor or your own code — ask through the API and MCP and get the same checked answers.
Every answer, whether a person or an AI assistant asked it, is built only from what that person is already cleared to see.
The part that is different
Most tools that put AI over a firm's documents build one index and hope the prompt keeps the secrets. Louvain resolves permissions before ranking: a question is answered against the subset of the corpus the person asking can already see. Two people can ask the same question, in the same deployment, on the same day, and correctly get different answers.
A correct refusal and a missing record look identical from outside. That is deliberate. Anything else leaks the existence of what it is hiding.
Start here
Quickstart — hosted
Sign in, connect a source, ask your first question.
Quickstart — self-hosted
Run the whole system yourself, including the model.
Connecting an AI assistant
Give Claude, Claude Code, Cursor or your own code the same checked answers, over MCP.
Understand the model
Worth twenty minutes before you connect anything real — the permission and provenance rules are what make the answers trustworthy, and they have consequences you should expect rather than discover.
Records, statements and facts
Original records, verbatim excerpts, statements and state derived for each viewer.
Permissions
How the fence is computed, and why it runs before ranking.
Provenance and time
State intervals, uncertainty, and what 'current' means per viewer.
Connect your sources
Connections
What a connection is, and how it becomes a permission boundary.
OAuth sources
Messaging, mail, calendars and files through an authorization broker, and what each can tell Louvain about who may see a thing.
Structured sources
Work trackers, code, CRMs, helpdesks, HR and identity systems, read as facts with their own history.
Slack
Channels, identity linking, and corporate exports.
Push your own data
Send events from any system to the ingest endpoint.
Library
Files, links and notes in a collection whose readers you choose.
Use it
Today
Your day, ranked for you: what needs you and what changed.
Plate
What your sources put on you, and the evidence that closed it.
Asking questions
What an answer contains, and why it sometimes refuses.
Administration
Members, roles, invites and SSO.
Billing and plans
The trial, seats, and what a lapsed plan does and does not do.
Limits and usage
What is metered and what happens at the ceiling.