Our first quantum-safe steps are live, ahead of their dates.

This week we put a date on every step of our move to quantum-safe cryptography. Today's release completes five of them, the furthest eight months early.

What changed today

Every connection our engine makes now offers AES-256 first, and offers a hybrid key exchange first: X25519 with ML-KEM-768, the new standard for key agreement (FIPS 203), beside the classical exchange. That is the defence against traffic being recorded now and decrypted later, and the major cloud services already accept it. AWS's own logs show it: after the upgrade, the engine's calls to AWS Key Management Service negotiated AES-256 with X25519 and ML-KEM-768.

From today, what the engine learns, kept on the customer's own hardware, is sealed with AES-256-GCM, and the keys that protect it are sent under ML-KEM-1024, the strongest setting of the new standard and the one the Information Security Manual names. The engine software itself is sealed with AES-256-GCM, and the engine verifies the new post-quantum certificates (ML-DSA, FIPS 204) as authorities begin to issue them. Every one of these is our own code, with no third-party library, checked against public test vectors.

Built differently

We do not use models. No LLMs. No SLMs. Of any kind.

No GPU. No data centre. No AI token costs, ever. Senua AI learns cause and effect directly from your own system's data, and runs on low-end CPUs. The rest of the roadmap keeps its dates: ML-DSA-87 signatures on our releases and licences in June 2027, and everything Senua AI controls by December 2027.

The roadmap · The register · The datasheet (PDF)