Lethe
Chats
…
starting…
Incidents ·
start here

The 60-second demo

  1. 1
  2. 2Then — watch the removal receipt.
  3. 3Ask the exact same question again — watch the answer flip to the live system.
  4. 4 — watch aging knowledge sink (reversibly), and the very stale ones queue for your approval.

Systems

Everything in the knowledge base. Decommission one and it's hard-deleted from the graph + vectors.

Upload

Feed your own runbooks, post-mortems or notes. They're parsed into the knowledge graph.

Ingestion runs a real cognify pass — about a minute, and it uses your LLM key. The default Incidents workspace is read-only to protect the demo data; create a workspace to ingest into.

Hosted demo: anything you ingest lives only until the instance restarts — nothing is kept. Self-host for persistent memory.

or paste text

Knowledge graph

The live graph Cognee built from your docs. Click a node to see what it connects to; decommission a system, then refresh — watch its node vanish.

system / concept type demoted

Curation

Proactive memory hygiene — catch knowledge that has gone stale or contradicts itself, before it misleads you.

The decay loop

Run a curation cycle

One bounded pass over every runbook by review-age. Aging knowledge is auto-demoted (reversible — it sinks in answers but stays restorable); the very stale are also queued for your approval before any permanent delete. Preview is free · 0 tokens · nothing changes until you apply.

Stale references

Remaining docs that still mention a decommissioned system. Free · 0 tokens

Conflicting runbooks

Docs that contradict each other on a fact. Uses your model · capped at 8 checks

Aging knowledge

Runbooks not reviewed in over 180 days — likely stale by age. Free · 0 tokens

Retirement proposals

Long-overdue runbooks that look retired — candidates to forget. Free · 0 tokens · Proposals only — nothing is deleted until you confirm.

Timeline

A durable audit log of what this memory has learned and forgotten — and when. Every decommission lands here with its verifiable removal receipt. Free · 0 tokens

reviewed demoted · reversible restored / self-healed forgotten · with removal receipt

Run a curation cycle or decommission a system and the coloured receipts land here.

New workspace

A separate knowledge base with its own graph — isolated from your other workspaces.

Delete workspace?

This permanently hard-deletes and all of its knowledge — graph and vectors. This can't be undone.

Model & API key

Bring your own provider. The key is stored locally on this machine and applied instantly — it only ever talks to the provider you pick.

Security
checking…

Single-tenant guard — one shared token gates every API route. Set LETHE_AUTH_TOKEN before any public deploy.

Add a system

Name it and paste its runbook, notes or post-mortem — Lethe builds it into the knowledge graph.

Access token

This Lethe instance is protected. Paste the access token to continue.

Re-arm the demo

This re-ingests the 2 legacy-cache runbooks into the knowledge base so you can run the forget demo again. It runs a real cognify pass — about 30 seconds — and uses your LLM key. The original forget receipt on the Timeline stays — this is a re-ingest, not an undo.