Sovereign AI memory infrastructure.
Your documents, embeddings, knowledge graph and files live on infrastructure you own. Chordian orchestrates the memory — it never keeps a copy of what is in it.
See the four deployment modelsAI memory infrastructure
Your documents, embeddings, knowledge graph and files live on infrastructure you own. Chordian orchestrates the memory — it never keeps a copy of what is in it.
See the four deployment modelsVector, graph, episodic and cache retrieval run in parallel across every source you connect, then are reranked before a model writes a single word — and every answer arrives with the documents that produced it.
Inside the retrieval stackSearch a company or a contact and Chordian works down a waterfall of sources until the record is filled — every field keeping the source it came from and how confident that source was.
How records are resolvedClaude, Cursor, ChatGPT and any other MCP client connect to the same Space over one endpoint. What you work out in one of them is there in the next, instead of dying with the session.
How the MCP endpoint worksAnswer with a model running inside the box, or with your own provider key under your own contract — your content never reaches a shared public model, and never becomes training data for one.
Where your content is allowed to goThe memory installs from a signed offline bundle with no call to a public registry, and answers using your own model or one running inside the box — so your knowledge never has to touch the open internet.
How the boundary is enforcedA complete OpenAPI reference, live request examples, and an MCP endpoint that puts the same memory straight into your IDE and your assistant. Nothing in the product is off-limits to your engineers.
Open the developer portalEvery request proves its identity and its permissions, secrets are stripped before anything is written, tenant isolation fails closed, and every privileged action lands in an append-only audit record.
Read the security modelIn development
Every tunnel will negotiate a hybrid key — the classical exchange in use today and a lattice-based post-quantum exchange together — so traffic captured now cannot be unlocked by a quantum machine later.
Inside the quantum-safe layerThe problem
The context lives in a CRM record, a Slack thread, a contract PDF and somebody's inbox. No system holds all four, so every question starts from zero and every assistant forgets between sessions.
Each tool answers from its own silo. The most recent sync silently overwrites whatever disagreed with it, and nobody is told the data ever conflicted.
Answers cannot be traced to a source, so they cannot be trusted for anything that matters.
One typed graph across every source, with conflicting facts surfaced for a human instead of quietly overwritten.
Every answer carries its citations — and, if you need it, none of it ever leaves your infrastructure.
What makes it different
Run the memory on your own server or cloud account. Content, embeddings, graph and usage stay there — we store none of it.
The same company arriving from four systems becomes one entity, not four near-duplicates — resolved continuously, on every write.
When two sources disagree, the conflict is surfaced and resolved with an audit trail — instead of the last write silently winning.
Secrets and personal data are detected and masked at the value level before anything is stored — or shown to a model.
Every fact records when it was true and when we learned it — so you can ask what you believed at a point in time, not just today.
Four retrieval engines run in parallel and are reranked before a model writes the answer — with sources shown before the prose.
The wedge
Most “private AI” is single-tenant hosting — the vendor still holds your data, just in a separate database. Chordian is architecturally different: the memory engine runs on your machine.
A breach of Chordian exposes no customer knowledge, no SSH keys and no encryption keys, because none of them are on our side. A subpoena served on us produces nothing to hand over.
Compare deployment optionsA WireGuard tunnel encrypts the line; mutual TLS proves both ends on every single request — enforced from the box’s first boot.
The box installs with no calls to public registries. Fit for regulated and disconnected sites.
One action tears down the box, its volumes and the tunnel — on infrastructure you control.
Trusted search
Connect Gmail, Drive, Outlook, Notion, Slack, Confluence and HubSpot, plus a catalog of 350+ more. Everything lands in one memory, and every answer comes back with the documents behind it — so the person reading it can check the claim instead of trusting it.
Company and contact intelligence
Describe the accounts you want and Chordian finds them, then works down a priority waterfall of sources — your own store first, then licensed providers, then the open web — until each field is filled by something it can point at.
Private models
Answer with a model running inside your own boundary, or with your own provider key under your own contract. Either way your content reaches no shared public model, and becomes training data for none.
In development
A model shaped by your organisation's own language and history, in an isolated namespace — so an answer is written the way your company writes, not just retrieved from it. Landing shortly; until it does, the two modes above are what runs, and this note stays here.
Quantum-safe encryption
In development
An attacker does not need a quantum computer today to hurt you tomorrow. They only need to record your traffic now and wait. We are closing that window: every tunnel will negotiate a hybrid key, combining the classical exchange in use today with a lattice-based post-quantum exchange.
Not live yet, and we will say so here until it is. Transport today is a WireGuard tunnel with mutual TLS proving both ends on every request — strong against every attacker that exists, and the thing the post-quantum layer is being added underneath.
Security
Most “private AI” is single-tenant hosting — the vendor still holds your data, just in a separate database. Chordian is architecturally different. On your own infrastructure the memory engine runs on your machine, so there are no keys, no content and nothing to subpoena on our side.
No trusted network and no trusted caller. Every request proves its identity, its permissions and its tenant boundary before any data is touched.
Keys, passwords, card numbers and personal identifiers are detected and masked at the value level before a write — and before anything is shown to a model.
Tenant scoping is applied at the query layer on every vector, graph and document call — and proved by an automated suite on every build, not by code review.
Every privileged action is recorded with who did it, when and the outcome — appended, never updated, always scoped to a tenant, and never containing a credential.
A WireGuard tunnel encrypts the connection to your box and mutual TLS proves both ends on every single request — enforced from the box's first boot.
The box installs from a signed bundle with no call to a public registry, which makes it fit for regulated and disconnected sites.
What we will not claim: SOC 2 and HIPAA readiness mapping exists, certification does not. We would rather tell you that now than during your security review. The full model, including the gaps
Deployment
Start on our infrastructure and move to yours later, or start on yours from day one. The API is identical either way, so the decision is never permanent.
Managed by us, isolated per tenant by a mandatory scope on every query. The fastest way to see it working on your own data.
Live in minutesYour own engines and storage in a separate namespace on our infrastructure, with physical separation rather than a shared store.
Isolated stackInstalled onto your hardware over an encrypted tunnel. Runs fully offline from a signed bundle for air-gapped sites.
Full sovereigntyProvisioned into your own account. AWS and DigitalOcean are self-serve today; GCP and Azure are available on request.
Your accountHow it works
# One call. Cited answer back.
curl https://api.uni-flow.ai/api/v1/memory/search \
-H "x-api-key: $CHORDIAN_API_KEY" \
-H "content-type: application/json" \
-d '{"query": "What is blocking the Acme deal?"}'
# {
# "answer": "Blocked on BAA approval and EU
# hosting confirmation [1].",
# "citations": [{ "index": 1, ... }]
# }
Start on our infrastructure, or run it entirely on yours. The integration is identical either way — so the decision is never permanent.