Most modern post-quantum cryptography (PQC) discussions focus heavily on live network traffic—like Signal’s PQXDH or Chrome's X25519Kyber768.
But what about local, offline, file-based applications? Desktop tools, local backup vaults, and offline embedded/IoT systems are often left hardcoding legacy cryptographic stacks. If that math gets broken or weakened in the future, the whole application requires a painful, massive rewrite.
To explore a solution, I built CryptoFlex: an open-source, local-first crypto-agility policy engine for Python 3.10+.
Crypto-agility means your application can dynamically swap its underlying encryption primitives without breaking your core application logic or requiring a code redeploy.
cryptoflex doesn't invent new math. Instead, it orchestrates existing, trusted primitives—classical X25519 and post-quantum ML-KEM (via liboqs)—behind a localized decision engine.
