Post-Quantum Cryptography · NIST-Standardized

Encryption for the age of the quantum adversary.

Raziel encrypts your files with ML-KEM lattice cryptography standardized by NIST — and never stores your secret keys or unencrypted files.

How it works

Three plain steps

Encrypt in Local mode in your browser, or over TLS in server mode; store the envelope and retrieve it anywhere. No mysticism — just post-quantum cryptography.

01

Upload

Pick a file or type a message. In Local mode, files are encrypted in your browser with ML-KEM-768 and AES-256-GCM before anything leaves your machine; Message mode and server mode send data to the server over TLS.

02

Store

Your envelope lands in your vault cache under a content-hash label — we never hold your plaintext.

03

Retrieve

Download the .raziel file or fetch it from your vault, then decrypt with your secret key on any device. Done.

Encrypt & decrypt

Files first, messages too

Encrypt a file and download a .raziel envelope, or switch to the message tab. File mode can run fully in your browser; the Message tab always uses the server API.

// ENCRYPT FILE

Encrypt a file

Choose a file. In Local mode it is encrypted in your browser and downloaded as a .raziel envelope before anything is uploaded; server mode sends the file over TLS.

Drop a file or click to choose
Local mode ON — your key stays on this device
Local mode — size is limited by this browser.
Get a free key
// DECRYPT FILE

Decrypt a file

Provide a .raziel envelope and your secret key. In Local mode the plaintext is reconstructed in your browser; server mode sends the envelope and key over TLS.

Drop a .raziel file or click
Local mode — your secret key stays on this device
Local mode — size is limited by this browser.
// ENCRYPT MESSAGE

Encrypt a message

Type text and get back a .raziel envelope you can copy or store. No signature is added during encryption.

Get a free key
// DECRYPT MESSAGE

Decrypt a message

Paste a .raziel envelope and your secret key to recover the plaintext.

Your vault

Encrypt, download, decrypt — anywhere

Seal a file into a .raziel envelope with post-quantum ML-KEM, download it, and decrypt with your secret key from any browser. The vault keeps only encrypted envelopes, for a limited time per tier.

Encrypted copies in the vault auto-delete after 6 hours (Watcher) / 12h (Messenger) / 24h (Guardian) / 48h (Sanctum). This is a transfer cache — download your envelope; it is not long-term storage.

// PREVIEW

Your encrypted transfer cache

When you seal a file, the encrypted envelope is held briefly so you can retrieve it from another device — it is a cache, not cloud storage. Download it and it is gone from our side.

Create account
Pricing

Pay for what you process

Start with Watcher. Scale to Messenger credits or a Guardian plan. Sanctum stays behind a conversation.

Developer API

Encrypt from your own code

POST a file or message to our endpoint with your API key. You get back a .raziel envelope. No account required to try — grab a free key below.

# 1. one-time: generate a recipient keypair (keep the secret key; the public key goes in a header)
curl -X POST https://raziel-pqc.cc/api/v1/kem/keypair \
  -H "Authorization: Bearer $RAZIEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"algorithm":"ML-KEM-768"}'

# 2. encrypt raw bytes: the request body IS your file, the response IS the .raziel envelope
curl -X POST https://raziel-pqc.cc/api/v1/encrypt/raw \
  -H "Authorization: Bearer $RAZIEL_API_KEY" \
  -H "Content-Type: application/octet-stream" \
  -H "X-Algorithm: ML-KEM-768" \
  -H "X-Public-Key: $PUBLIC_KEY" \
  --data-binary @document.pdf \
  -o document.pdf.raziel

The response is the raw envelope (X-Filename: encrypted.raziel). For inline messages instead POST JSON to /api/v1/encrypt with {filename, algorithm, recipient_public_key, plaintext_b64} and read data_b64. Reference: OpenAPI spec — free key at /api/v1/key/free.

Standards & advisories

Why post-quantum, and why now

Standards bodies and national-security agencies are telling organizations to begin their post-quantum migration today. Raziel is already built on the NIST-standardized algorithms they point to.

PQC Coalition · September 26, 2023

Industry coalition forms

IBM Quantum, Microsoft, MITRE, PQShield, SandboxAQ and the University of Waterloo launched the Post-Quantum Cryptography Coalition to accelerate commercial and open-source adoption of NIST’s post-quantum algorithms.

SandboxAQ press release →

NSA · CNSSP-15

2027 requirement for new systems

As mandated by Committee on National Security Systems Policy 15, from 2027 all new commercial National Security Systems must be capable of supporting quantum-resistant algorithms; legacy systems that cannot support them are to be phased out by 2030.

NSA press release →

CMVP · 21 September 2026

FIPS 140-2 is now historical

NIST’s Cryptographic Module Validation Program moved every remaining FIPS 140-2 certificate to its Historical list on 21 September 2026 — the Active FIPS 140-2 list is now empty, so a 140-2 validation no longer counts for new deployments. FIPS 140-3 is the current module standard.

Raziel does not claim 140-2 or 140-3 module validation. We implement the NIST PQC algorithm standards: ML-KEM-768/1024 (FIPS 203), ML-DSA-65 (FIPS 204), SLH-DSA-PURE-SHA2-128S (FIPS 205) — and do not claim FIPS 206 (FN-DSA).

Raziel encrypts with NIST-standardized post-quantum cryptography today: ML-KEM-768 / ML-KEM-1024 (FIPS 203) for key encapsulation, with ML-DSA-65 (FIPS 204) and SLH-DSA-PURE-SHA2-128S (FIPS 205) in the shipped stack.