Eon Path Quantum-safe encryption for apps you already run. Ride the wave before it catch you.

// hybrid braid — X25519 + ML-KEM-768

Close the "harvest now, decrypt later" gap before attackers exploit it. No code changes required.

Who this is for

CISOs and engineering teams at organizations running critical infrastructure who:

How it works

Under the hood

Setup

Quantum-safe crypto. Apps you already run. No code change.

Bad guy grab your data now. Decrypt later when quantum come. Call it "harvest now, decrypt later." Threat real — maybe this decade. Eon Path stop it. Today.

How it work

Eon Path sit as transparent proxy between app and network. It catch normal TLS, swap in quantum-safe crypto, pass traffic on. App never know. Dev never touch code.

Why good

Under hood

Set up

Eon Path — NIST-standardized hybrid post-quantum key exchange and signatures. Drop-in; no application code changes.

Cryptography

KEMML-KEM (FIPS 203) — 512 / 768 / 1024
KEM defaultML-KEM-768 (NIST level 3)
signatureML-DSA (FIPS 204) — 44 / 65 / 87
signature defaultML-DSA-65 (NIST level 3)
key exchangehybrid: curve25519 (ECDH) + ML-KEM, combined via KDF
alt KEMFrodoKEM-640 (conservative)
fallbackclassical, for backward compatibility
crypto backendOpenSSL 3.5+ (statically linked)

Architecture

Two tunnelling methods:

Defaults

proxy address127.0.0.1:9999
ssh address127.0.0.1:2022
pqc-mlkemtrue
pqc-ordermlkem
platformsWindows · macOS · Linux
configflags > YAML > env > defaults

Deploy

Documentation

Full reference at docs.eoncore.eu/eon-path/. Every page there is also Markdown: append index.md to its URL. All products in one file: docs.eoncore.eu/llms-full.txt.