Security
Security you can point at
Chordian’s defence is structural — from post-quantum key exchange in transit to memories that run entirely on your own infrastructure. This is the posture, layer by layer, with honest status on each.
Post-quantum cryptography
Hybrid post-quantum key exchange
At the public TLS edge, the 1.3 handshake negotiates X25519MLKEM768 — classical X25519 combined with ML-KEM-768 (NIST FIPS 203). The session key is derived from both, so it stays safe even if one algorithm is later broken, and it defends against harvest-now, decrypt-latercapture of today’s traffic. This covers key exchange — certificate signatures remain classical.
One session key derived from both algorithms — safe unless both are broken.
Post-quantum here means key exchange at the edge — not encryption at rest, and not the in-cluster or box legs, which are on the cryptographic-resilience roadmap (FIPS 203 / 204).
GDPR & data residency
Residency by shape, not by policy
The core platform meets a GDPR baseline for identity, billing and metadata. A Secure Dedicated memory adds regional residency: content — and inference — stay in the region you choose, on EU or self-hosted models, and erasure is as concrete as deleting the box.
GDPR is a per-memory choice — a regulated workload runs on a GDPR tier without forcing every workload onto regional infrastructure.
Never leaves the region. Inference pinned to EU / self-hosted models.
Defence in depth
Post-quantum transport and regional residency sit on top of the same layered defence that protects every memory.
Tenant isolation
A tenant scope on every read and write, produced by fail-closed helpers and verified in CI on every pull request. Tenant is derived server-side, never read from a request body.
Read moreData sovereignty & air-gap
Run a memory on your own server or cloud. Content, embeddings, graph, files and usage stay on your box — accessed only through a signed seam, never platform storage. Boxes install air-gapped, and a sovereign box with no LLM egress configured fails loud rather than silently calling a public model.
Read moreMutual TLS to your boxes (BYOI)
On the platform-to-box path, every caller presents a client certificate signed by the private Chordian BYOI CA — over HTTP and WebSocket. Certless calls are rejected; a valid cert returns 200. Inside the platform, services authenticate with signed HMAC tokens.
Read moreSecrets & Vault
Credentials live in Vault; a box holds its own encryption key, generated on the box and never transmitted. Secrets are never written to logs, the audit trail, or any model call.
Read moreEncryption at rest
Secrets and connection bundles are sealed with AES-256-GCM and Vault-wrapped envelope keys (DEK/KEK) — a database leak alone yields only ciphertext. On a BYOI box, content is encrypted with a key generated on the box that never leaves it.
Read moreRBAC & audit
Five roles and fifty-plus granular permissions with resource-scoped grants; revocation hits the gateway before the database. Every privileged action is recorded immutably, tenant-scoped, credential-free.
Read moreData perimeter (DLP)
Secrets and PII are detected, classified and masked at the value level — before anything is embedded, stored, or shown to a model. Fail-closed.
Read moreAPI gateway
Customer traffic passes through Kong — key authentication, per-plan rate limits, RBAC and credit metering — so no public route bypasses the gateway.
Read more