Calame wires your databases and documents into Claude, Cursor, ChatGPT or Copilot, and governs every exchange: PII masked in the answer, writes held for approval, everything audited.
Postgres · MySQL · SQLite · Notion · SharePoint · Drive · S3
Every Calame answer shows what was masked, every write waits for a human, every query lands in the audit log. Here is what that looks like.
Calame detects emails, phone numbers, addresses and card numbers, then applies your rule per column: redact, hash, partial mask. The AI never sees the raw value.
| name | email mask | phone mask |
|---|---|---|
| Margaux Lefèvre | m***@acme.io | +33 6 ▓▓ ▓▓ 41 |
| Diego Álvarez | d***@acme.io | +34 6▓▓ ▓▓▓ 09 |
| Ana Kovač | a***@acme.io | +386 ▓▓ ▓▓▓ 22 |
Tick tables, columns, folders. Add row-level conditions per user. One source, many governed views.
Schema introspection for SQL, vector search for documents. Read-only connections, parameterized queries, optional SSH tunnel.
Read-only by default. When a profile allows writes, each one lands in a pending queue with the exact statement, the actor and the diff, until someone approves it.
Open, token, password, OIDC SSO, OAuth 2.1 with dynamic client registration, or an external validation URL. Every user revocable in one click.
Every query, every actor, every result: recorded, filterable, exportable. The kind of trail your security team asks for on day one.
Put Calame in front of any external MCP server: tools allowlisted fail-closed, calls audited, writes routed through the same approval queue.
Plug in sources, draw what the AI is allowed to see, hand the endpoint to your clients. Everything happens with a mouse.
Postgres, MySQL, SQLite, Notion, SharePoint, Drive, S3. Read-only introspection, optional SSH tunnel.
Tick tables and folders, mask what should be masked, add per-user row rules. Save: a governed MCP server is published.
One click connects Claude Desktop. Cursor and VS Code discover it via OAuth. Copilot and ChatGPT reach it through the tunnel.
Calame speaks MCP, the protocol your AI clients already use. Local clients connect in one click; cloud assistants like Copilot and ChatGPT reach your machine through a built-in HTTPS tunnel.
New MCP clients ship every month. Calame stays compatible because it follows the spec, not a vendor SDK.
Calame is dual-licensed. The core (connectors, profiles, MCP runtime, PII masking, chat, audit) is Apache 2.0. The ee/ modules (SSO + document RAG) are BUSL 1.1: Pro unlocks them on one instance, Enterprise on as many as you need.
Self-host without limits.
Unlock SSO + RAG, scale to many instances, or get hosted.
Your data stays where it is. Calame decides what your AI is allowed to see, and keeps the receipts.
