Mneme

Mneme is an agentic enterprise search system that performs deep research over heterogeneous corpora—PDFs, contracts, memos, emails, spreadsheets, and more—while producing verifiable, cited answers. It is not a “chat with your PDFs” toy and it is not naïve RAG.

What makes Mneme different?

• Multi-hop query planning: Automatically decomposes complex questions into sub-queries, retrieves relevant passages across sources, and reasons to a final answer.
• Hybrid retrieval stack: Layout-aware chunking of long PDFs, BM25 + dense retrieval, and cross-encoder re-ranking to minimize false positives.
• Structured citations: Passage-level attributions with page/section anchors; answers must be backed by evidence. When evidence is insufficient, Mneme abstains.
• Auditable traces: Deterministic research logs (JSON) capturing retrieval steps, filters, and reasoning summaries for internal review or compliance.
• Enterprise controls: Document/row-level access filters, retention policies, and PII-aware redaction options.
• Low-variance responses: Guardrails and retrieval-gating reduce hallucination; we prefer “I don’t know without X” to confident fabrications.

Core capabilities

• Heterogeneous corpora: Contracts, filings, PDFs with tables, slides, spreadsheets, emails, and wikis.
• Connectors: File shares, S3, Google Drive, SharePoint, and local folders (watchers for incremental updates).
• Incremental indexing: Versioned indexes with background refresh; ingestion pipelines preserve document structure.
• Answerability score: Confidence and coverage heuristics with a rationale for why an answer is (un)supported.
• Export: Answers + citations + trace as JSON or Markdown for matter files or downstream systems.

Why law firms use Mneme

• Faster first-pass review: Identify controlling clauses and exceptions across thousands of pages in minutes, not days.
• Consistent memo drafts: Evidence-linked paragraphs you can paste into drafts; no scavenger hunts for sources.
• Explainable internally: Audit logs you can hand to partners or QA—what was retrieved, what was omitted, and why.

Deployment

• Pay-as-you-use: Hosted option for trials and small teams.
• Dedicated deployments: Private deployments with data residency controls; SSO and per-repo/drive ACL mapping.

Get access

Interested in a pilot? Reach out via Contact. We’ll scope a corpus, success metrics, and guardrails before enabling ingestion.