Product · Klara
Post-quantum encryption for what you already share.
Klara encrypts files and messages on your device with post-quantum cryptography. You send them by email, messaging, cloud or USB, as always, and only the recipient can open them.
01 · The problem
What travels encrypted today can be read tomorrow.
Someone can copy your files encrypted with RSA or elliptic curves today and keep them until a quantum computer capable of reading them exists. If that information has to stay secret for years, the risk has already started.
02 · How it works
Three steps, none of them new to your team.
Protect
Pick the file or message and who it is for. Klara encrypts it on your device before it leaves.
Share
Send it over the usual channel: email, messaging, cloud or USB. Only encrypted content travels.
Verify
The recipient checks that it came from you and that nobody changed it, and opens it on their own device.
03 · Architecture
Encryption happens at the ends.
Klara does not need you to trust the channel. It encrypts and decrypts on the devices, and the decryption key never leaves them.
Your device
- Encrypts the content for each recipient.
- Adds proof of who the sender is.
- Your private key stays here.
The channel
- Email, messaging, cloud or USB.
- Carries encrypted content only.
- Nothing to change or configure.
The recipient
- Checks who sent it and that it did not change.
- Decrypts it with their private key.
- That key never leaves their device either.
04 · Standards
Published algorithms, not secret ones.
| Purpose | Algorithm | Standard |
|---|---|---|
| Key exchange | ML-KEM-768 | NIST FIPS 203 |
| Content encryption | AES-256-GCM | NIST FIPS 197 · SP 800-38D |
| Sender authenticity | ML-DSA-65 | NIST FIPS 204 |
05 · Deployment
Run by us or by your team.
In both models, encryption happens on your team's devices.
Run by CampUs
We run the server side. Your team starts without setting up any infrastructure of its own.
Self-hosted
Klara runs on your infrastructure, under your policies and with your own access controls.
06 · FAQ
What people usually ask us.
Do I have to change my email or cloud provider?
No. Klara encrypts the file or message on your device and you send it over the channel you already use: email, messaging, cloud or USB.
Who can read what I encrypt?
The recipients you chose, on their devices. The channel, and anyone who intercepts the transfer, see encrypted content.
Why post-quantum, if no quantum computer breaks RSA today?
Because whatever is intercepted today can be stored and read later. The NIST IR 8547 draft (2024) proposes deprecating RSA and elliptic curves from 2030 and disallowing them from 2035. Information that must stay secret beyond those dates is already exposed.
Does it protect what I already sent under classical encryption?
No. Klara protects what you encrypt with it. Whatever was already intercepted under classical encryption stays exposed, which is why it pays to start with the information that must stay secret the longest.
Why ML-KEM-768?
It is the middle security level of ML-KEM, the key-exchange mechanism NIST standardized in FIPS 203 (2024) to resist attacks by quantum computers.
Shall we try it with your own files?
We show you Klara over the channels your team already uses.