Obliviate
Verify
Chats
…
starting…
Default ·
start here

The 60-second demo

  1. 1 — drop a file or paste text in Upload.
  2. 2 — a graph-grounded answer.
  3. 3 — watch the 3-part proof + signed certificate, then re-ask and see it say not on record.
  4. 4 — the erased subject's nodes are gone (its ghosts greyed out).

Subjects

Every subject in this workspace's memory. Forget & Prove one and it's verifiably erased — documents, graph nodes, edges, and its encryption key crypto-shredded.

Upload

Feed your own records and notes. Each is stored encrypted under its subject's key, then an LLM extracts entities and relationships into the knowledge graph.

Ingestion is synchronous — it uses your configured model to extract the graph, then returns a receipt immediately.

or paste text

Knowledge graph

The live graph extracted from your records. Click a node to see what it connects to; Forget & Prove a subject, then refresh — watch its nodes vanish (shared ones greyed as ghosts).

entity ghost · erased demoted

Curation

Keep memory current between hard erasures — catch surviving text that still mentions an erased subject, and records that have gone stale by age. Demote a subject to sink it (reversibly), or restore it.

Stale references

Surviving nodes and edges whose text still mentions an already-erased subject. Free · 0 tokens

Aging records

Records not reviewed in over 180 days — likely stale by age. Demote to sink a subject (reversible), or restore it. Free · 0 tokens

Timeline

A durable audit log of what this memory has learned and forgotten — and when. Every erasure lands here, and links to its signed certificate. Free · 0 tokens

ingested demoted · reversible restored forgotten · with certificate

Ingest a record or Forget & Prove a subject and the coloured events 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 mutating API route. Set OBLIVIATE_AUTH_TOKEN before any public deploy.

Add a record

Name the subject and paste its record or notes — Obliviate stores it encrypted and builds it into the knowledge graph.

Access token

Writes are token-gated — an erasure product should never let anonymous visitors delete data. Judges: paste the access token from the submission notes to run Forget & Prove. Browsing, recall, the graph, and /verify stay open.