Qpher - Post-quantum encryption & signing — drop-in REST APIs

Post-quantum cryptography as drop-in REST APIs. ML-KEM-768 (formerly Kyber) for encryption and ML-DSA-65 (formerly Dilithium) for signatures — both NIST-standardized in August 2024 (FIPS 203 & 204). Private keys never leave secure enclaves. SDKs for Python, Node.js, Go. MCP server for AI agents. Built by an engineer who spent 12 years on U.S. federal systems (VA, DHS, USCIS, DFC) — making the migration practical for everyone else. Start free.

Hey Product Hunt 👋 I'm Vincent. Spent 12 years building systems for the U.S. government — VA, DHS, USCIS, now DFC. A year ago I realized something uncomfortable: almost everything I've helped build will be broken by quantum computers. NIST says crackable within the next decade. And "harvest now, decrypt later" attacks are collecting encrypted data TODAY. NIST finalized the replacement standards in August 2024 (FIPS 203 & 204). But when I tried to migrate, I couldn't find developer-friendly tools — so I built Qpher. Three things I focused on: → NIST standards from day one (ML-KEM-768 + ML-DSA-65) → Private keys never leave secure enclaves (no export endpoint, by design) → 3 lines of code — Python, Node.js, Go SDKs, plus MCP server for AI agents Free tier for prototypes. Two questions for this community: • If you're in financial service / healthcare / gov — what's your PQC migration timeline? • If you're a dev — what would make you actually try a PQC API vs sticking with AES + RSA today? Happy to answer anything technical. Q-Day is coming whether we're ready or not. 🛡️

Qpher - Post-quantum encryption & signing — drop-in REST APIs

Replies