Overview
What Chordian is, who it is for, and how to find your way around these docs.
Chordian is memory infrastructure for organisations. It takes the knowledge scattered across your CRM, your drive, your wiki, your inbox and your uploads, and turns it into a single typed, temporal memory that answers questions with citations.
The part that usually matters most in an evaluation: it can run entirely on your own infrastructure, with none of your content on ours.
What you get
Answers, not search results
Four retrieval engines run in parallel and are reranked before a model synthesises the answer — with the sources shown before the prose.
A knowledge graph
Typed entities and relationships with bi-temporal facts, so you can ask what was true at a point in time — not just what a document says today.
Memory that defends its accuracy
Conflicting sources are surfaced instead of silently overwritten, and the memory grades its own health.
Sovereignty as architecture
Run a memory on your own server or cloud account. Content, embeddings, graph and usage stay there.
Who these docs are for
| You are… | Start here |
|---|---|
| Evaluating Chordian | Quickstart, then Core concepts |
| Integrating an application | Platform API and Memory API |
| Wiring an agent or IDE | MCP integration |
| Assessing security | Security overview |
| An AI agent | /llms.txt — every page is also available as .md |
How the product is put together
At the centre is a memory: a complete, self-contained stack — application, vector engine, graph engine, cache and object store — that can be deployed in four postures without changing a line of its code.
That single design decision — a memory as a deployable unit rather than a row in a database — is what makes the sovereignty story possible without forking the product. A feature that ships to the hosted service is simultaneously available to a customer running a box in their own data centre.
A note on honesty
These docs distinguish carefully between what is live, what is partial, and what is roadmap. Where a capability depends on how you deploy — several do — the condition is stated rather than glossed. If something here reads as hedged, that is deliberate.