30 seconds
Quantum exposure calculator
Three questions. Find out whether data you store today will still matter when quantum computers can read it.
Open →
QuorVault Lab · lattice n = 256
Test it. Break it. Trust it.
Two tools, zero install. Measure your quantum exposure, then encrypt real data with post-quantum cryptography, right here in your browser.
01Risk check
Are you already exposed?
Hackers can steal your encrypted data today, store it, and read it the day quantum computers can break today's encryption. The only question: will your data still matter on that day? Answer three questions to find out.
Keep this result
Your data is at risk
1year exposed
Quantum computers arrive before your data stops being sensitive. Anything stolen today could be read for 1 year while it still matters.
10 yrs secret+3 yrs to switch=13 yrs needed>12 yrs until quantum
Quantum arrives
Today+20 yrs+40 yrs
Switching to new encryption Must stay secret Stolen data readable
Based on Mosca's theorem, a standard risk model
Get a quote →02Live demo
Don't trust us. Try it.
Real ML-KEM-768, X25519 and AES-256-GCM, running right now in your browser, with the same scheme QuorVault uses. Nothing you type leaves this page.
stored in customers.email#42
Now try to break it
Hover or tap an attack to see what it simulates, then click to run it.
- 1
Data key generated
AES-256 · random 32 bytes
································
A unique secret key is drawn at random for this value. This is what will lock the data.
- 2
Value encrypted
AES-256-GCM · bound to customers.email#42
································
The value is encrypted with that key and tied to its exact place (table, column, row). Without the key, it's unreadable gibberish.
- 3
Hybrid key agreement
X25519 ‖ ML-KEM-768 → HKDF-SHA256
································
Two independent locks build the vault key: X25519, today's classic algorithm, and ML-KEM-768, built to resist quantum computers. To get in, an attacker would have to break both.
- 4
Data key wrapped
Stored in the vault, never in the clear
································
The value's secret key is itself locked with the vault key. Nothing is ever stored in the clear in the database.
sealed in 0 msML-KEM ciphertext 1088 bytes100% client-side
Convinced?
Now protect the real thing.
Tell us about your database. We'll reply with a tailored quote to bring this protection to your production data.
or write to contact@quorvault.com · read the FAQ