Harvest Now, Decrypt Later — The threat is active

Your encryption will be
broken by quantum computers.
Fix it before they arrive.

SQrypt scans your codebase for quantum-vulnerable cryptography and replaces it with NIST FIPS 203 compliant hybrid encryption — in three lines of code.

# Install and scan your codebase in 30 seconds
$ pip install "sqrypt-cyber-sdk[cli]"
$ sqrypt --target ./your-codebase --pdf

Scanning 2,847 files across 9 languages...
⚠ RSA-2048 found: payments/gateway.py:142
⚠ ECDSA found: auth/tokens.py:88
⚠ MD5 hash found: utils/checksums.py:34

Risk score: HIGH — 14 Shor-vulnerable primitives
✓ PDF audit report generated → audit_report.pdf
✓ CBOM exported → cbom_report.json
NIST FIPS 203 — ML-KEM-768 X25519 + ML-KEM-768 Hybrid AES-256-GCM Server-Side HKDF-SHA256 Key Derivation CBOM Audit Reports AST-Based Static Analysis Redis Key Persistence KEK Encryption at Rest NIST FIPS 203 — ML-KEM-768 X25519 + ML-KEM-768 Hybrid AES-256-GCM Server-Side HKDF-SHA256 Key Derivation CBOM Audit Reports AST-Based Static Analysis Redis Key Persistence KEK Encryption at Rest

The clock started
before you knew it.

Adversaries are already storing your encrypted data today, waiting for quantum computers to arrive. When they do, your RSA and ECC keys become useless.

Harvest Now, Decrypt Later

Nation-state actors are capturing encrypted enterprise traffic today. They need only wait for a CRQC to decrypt everything — including data encrypted years ago.

ACTIVE THREAT — 2026

CNSA 2.0 Mandate

The US government requires all national security systems to migrate to post-quantum cryptography by 2030. Financial institutions and contractors are next.

DEADLINE — 2030
🔐

NIST Finalized the Fix

NIST published FIPS 203 (ML-KEM) and FIPS 204 (ML-DSA) in 2024. The replacements exist. The migration hasn't started for most organizations.

STANDARD — FIPS 203/204

Find the risk.
Then eliminate it.

Two tools, one migration. Audit your codebase, then drop in quantum-resistant encryption without rebuilding your key infrastructure.

Cryptographic Bill of Materials

The scanner performs static analysis across your entire codebase — AST parsing for Python, comment-aware regex for 8 other languages. Every RSA key, ECC curve, and legacy hash is surfaced with exact file path, line number, and code snippet.

Output formats are built for compliance teams: PDF audit reports, CBOM JSON aligned to NIST PQC draft standards, and machine-readable findings for CI/CD integration.

  • AST-based analysis for Python — catches aliased imports and call sites
  • 9 languages: Python, JS, TS, Java, C, C++, C#, Go, PHP
  • Detects RSA, ECDSA, Diffie-Hellman, MD5, SHA-1
  • Risk scoring: LOW / MEDIUM / HIGH / CRITICAL
  • PDF report, CBOM JSON, raw findings JSON
  • Parallel scanning via ProcessPoolExecutor
terminal
# Free — no API key required $ pip install "sqrypt-cyber-sdk[cli]" # Scan and generate PDF report $ sqrypt --target ./src --pdf # Export CBOM for compliance $ sqrypt --target ./src \ --cbom cbom.json \ --output-json findings.json \ --pdf report.pdf

Hosted Key Management Service

The SDK wraps a hosted KMS implementing the NIST-recommended hybrid construction: X25519 for classical security today, ML-KEM-768 for quantum resistance tomorrow. All key operations happen server-side — key material never leaves the KMS boundary.

Drop it in wherever you currently use RSA or store sensitive fields. Card numbers, PII, API tokens — three lines of code.

  • Hybrid X25519 + ML-KEM-768 + HKDF-SHA256
  • Server-side AES-256-GCM — key never transmitted
  • Per-tenant keypair isolation
  • KEK encryption at rest in Redis
  • Structured JSON audit log per operation
  • Rate limiting + input validation built in
python
# pip install sqrypt-cyber-sdk
from sqrypt.client import SQryptClient
client = SQryptClient(
    server_url="https://api.sqrypt.io",
    api_key="YOUR_API_KEY"
)
# Encrypt sensitive data
payload = client.encrypt(card_number)
store_in_db(payload.to_dict())
# Decrypt when needed
original = client.decrypt(payload)
# Protect specific fields
safe = client.protect_dict(record, sensitive_keys=["tax_id", "card_data"])

Quantum-safe in
four steps.

01

Scan your codebase

Run the CLI scanner against your repository. SQrypt performs AST analysis on Python and regex analysis on 8 other languages, identifying every file and line using RSA, ECC, DH, or legacy hashes.

02

Review the audit report

Receive a PDF audit report and machine-readable CBOM JSON. Your security team gets file-level evidence and a risk score. Your compliance team gets a cryptographic inventory aligned to NIST PQC standards.

03

Drop in the SDK

Replace vulnerable encryption calls with SQryptClient. Three lines of code. The hosted KMS handles all key operations server-side — you store only ciphertext envelopes that contain no key material.

04

Stay protected as standards evolve

The hybrid construction (X25519 + ML-KEM-768) means both classical and quantum security are maintained simultaneously. If either primitive is found weak, the other provides the security floor.

393+
Weekly PyPI downloads
9
Languages supported
768
ML-KEM security bits
0
Key bytes ever transmitted

Start free.
Scale when you need to.

The CLI scanner is always free. The hosted KMS scales with your usage.

Developer
Free
forever
  • CLI scanner — unlimited scans
  • PDF, CBOM, JSON reports
  • 500 KMS API calls / month
  • 1 tenant
  • Community email support
  • SLA guarantee
  • Dedicated KMS instance
Get API key
Enterprise
Custom
contact us
  • CLI scanner — unlimited scans
  • Unlimited KMS API calls
  • Unlimited tenants
  • Dedicated KMS instance
  • SLA guarantee
  • Security architecture review
  • Compliance documentation

Ready to start your
PQC migration?

Request a free API key. We'll have you running in under 10 minutes.

We respond within 24 hours. No spam, ever.

🔒
NIST FIPS 203 — ML-KEM-768
🛡
NIST FIPS 204 — ML-DSA (Roadmap)
📋
CNSA 2.0 Alignment
🔑
Zero key material in transit