Skip to content

How it works

Everything your team writes and says, indexed and cited.

Leon syncs your tools and AI assistants, stores every item verbatim, keeps AI conversations private to their author, and answers with sentence-level citations.

01 Capture

Connects to your tools and AI assistants.

42 connectors over OAuth or an API key, synced incrementally every 15 minutes. AI conversations arrive through the browser extension and a coding-assistant hook.

  • Polls each tool every 15 minutes; nothing to set up on the vendor side
  • Extension: explicit consent, per-site toggle, paused in private windows
  • Coding assistant: each session captured when it ends
Illustration: connected tools syncing every 15 minutes, the browser extension with a per-site toggle, and a coding-assistant session sent when it ends. Fictional example · what Leon ingests

02 Store

Stores the originals, with access rules attached.

Leon stores each item verbatim, with a link to the original. Recognizable secrets are redacted before anything is stored.

  • Every result opens in its source tool
  • AI conversations, chats and notes private to their author
  • API keys, tokens and .env secrets redacted before storage
Illustration: three stacked layers. Bottom: the original records, stored verbatim. Middle: the passage index. Top: access control, shared with the team or private to you. Fictional example · what Leon stores

03 Search

Hybrid search across every source, with the answer on top.

Postgres full-text and vector search run side by side and are merged with reciprocal rank fusion, always after the permission filter. A generated answer sits above the results, every sentence cited.

  • Inline filters: from:, tool:, type:, since:, before:
  • Exact-phrase matching in quotes
  • Typo-tolerant title matching

Search syntax

from:julie
written by one person
tool:github
one connector only
type:meeting
ticket, page, email, meeting, conversation…
since:7d
last 7 days; also weeks or months
before:2026-10-01
before a date
"exact phrase"
exact match

Fictional example · Leon’s Search screen

04 Chat

Chat that cites its sources, or says it doesn’t know.

Leon searches, reads and cross-checks sources before it answers. Every claim is cited. When the sources fall short, it says so instead of guessing.

  • Private chats you can delete
  • Morning briefing: done, changed, still open
  • Available to any MCP client
Illustration: a chat where Leon answers with cited sources, the three-part morning briefing, and the four tools the MCP server exposes. Fictional example · chat and morning briefing

Next

Known limits.

None of this is in the product today. We list it so you can plan around it.

  • Planned

    Google Calendar

    Events and attendees. Gmail and Google Drive are already supported.

  • Planned

    Microsoft 365

    Teams, OneDrive and SharePoint. Outlook mail and calendar are already supported.

  • Planned

    Images and scanned PDFs

    Text-based PDF, Word, Excel and PowerPoint files are indexed. Scanned pages and images need OCR, which isn’t built yet.

  • Planned

    Data export

    Export a workspace’s data, and delete it entirely from the interface.

  • Planned

    Source permissions

    Mirroring each tool’s sharing settings, so a page private in its source tool stays private in Leon.

Every answer, cited.

Connect your first tool and ask your first question.