A writing environment where the outline is a real object, not a heading hierarchy
If you are writing the document rather than searching it.
An AI research assistant that shows its sources or says it does not know
Anchor answers research questions against your own document corpus and cites the exact passage behind every claim. When the corpus does not contain an answer it says so instead of generating a plausible one — which is the only behaviour that makes an AI research tool usable for work that matters.
Every claim links to the exact paragraph behind it, not just the document.
Returns "I don't have that" rather than falling back to model knowledge.
A corpus under NDA never leaves your network.
A tunable threshold below which Anchor declines to answer at all.
A research interface, not a chatbot. Query in, cited answer out.
Shows which answers changed when you add or remove documents.
Language models are already fluent enough. The failure mode that matters for research is that a confident wrong answer costs more than no answer at all, and you cannot tell them apart by reading.
Anchor is built around making that distinction visible.
Every claim in an Anchor answer is anchored to a span in a source document — not a document-level citation, a passage-level one. Click any sentence and you land on the exact paragraph it came from.
When retrieval returns nothing above the confidence floor, Anchor returns "I don't have that" and shows you what it did find. It does not fall back to the model's parametric knowledge, because a tool that silently switches between "from your documents" and "from the model's training data" is worse than useless for compliance, legal or technical research.
Anchor is not a chatbot. There is no persona, no follow-up small talk, and no attempt to be conversational. It is a research interface: query in, cited answer or an honest miss out.
It is also not a general-purpose assistant. It only knows what you have given it.
Your documents are embedded and stored in your own infrastructure. Anchor supports self-hosted embedding models, which means a corpus under NDA never leaves your network — the usual blocker for teams who would otherwise have adopted something like this two years ago.
Free up to 500 documents. Self-hosted embeddings on all plans.
Free
$24/month
Custom
Adding or removing documents now shows which previously-answered questions changed, so you can see when a policy update invalidated an earlier answer.
Every claim is anchored to a retrieved passage, and when retrieval returns nothing above the confidence floor Anchor declines rather than generating. That eliminates the specific failure of inventing facts from parametric knowledge. It cannot eliminate misreading a passage it did retrieve, which is why the citation is always one click away.
Embeddings can run entirely on your own infrastructure using a self-hosted model, on every plan including the free tier. In that configuration your documents never leave your network.
PDF, DOCX, Markdown, HTML and plain text, plus Notion and Confluence via read-only connectors. Scanned PDFs are OCR'd on ingest.
Comfortably into the low millions of passages. The free tier caps at 500 documents; paid plans are limited by your own storage rather than by us.
You can ask it follow-up questions, but it will not maintain a persona or answer anything outside your corpus. That is deliberate — the moment a tool blurs "from your documents" and "from training data", its citations stop meaning anything.
Similar products worth comparing before you commit.
A writing environment where the outline is a real object, not a heading hierarchy
If you are writing the document rather than searching it.
A local-first sync engine you can drop into an app you already shipped
Shares the commitment to keeping data on your own infrastructure.
Ranked by shared categories, tags and explicit alternative relationships.
A writing environment where the outline is a real object, not a heading hierarchy
A local-first sync engine you can drop into an app you already shipped
Observability a two-person team can afford to run and actually understand