Aere Shield
Find every vulnerable key, certificate and protocol in an organization, plan the post-quantum migration, and keep a verifiable report of what changed.
Every migration to post-quantum cryptography starts with three questions: what do we run, what of it is exposed, and what do we change first. Shield is the set of published tools that answer them for a domain, a source tree or a fleet of keys, and that leave behind a report another party can verify without asking us.
What exists today, measured
Every line below names the date its module was published in the public repository, the page or the contract behind it. Each module ships its README, its tests and its negative controls; nothing here asks you to take our word.
- Readiness scanner, 2026-09-29. For one public hostname it opens real TLS connections and reports whether the edge offers post-quantum key exchange; it measures, it does not estimate. Public page: quantum readiness; module readiness.
- Quantum exposure report, 2026-10-14. Classifies Bitcoin and Ethereum addresses by whether their public key is already readable from chain data, in three declared modes, and writes a dated report bound in an AIP-23 compliance envelope that anyone can check later. Page: quantum exposure report; module exposure-report.
- Cryptographic inventory, 2026-09-29. Reads a source tree and finds every use of cryptography (algorithms, key sizes, curves, modes, TLS settings, JWT algorithms, key and certificate files), classifying each by exposure; 37 fixtures with the exact expected findings. Module crypto-inventory.
- Post-quantum PKI, KMS and TLS gateway, 2026-09-29. A private certificate authority issuing ML-DSA X.509 v3 certificates as RFC 9881 specifies (pq-pki); a transit-style key service where every key is hybrid classical plus post-quantum (pq-kms); a TLS 1.3 terminating proxy that offers X25519MLKEM768 in front of any HTTP service you already run (pq-gateway).
- Control plane, 2026-09-29, updated 2026-10-11. Turns scans into a plan with each action named, and the console that shows it; module control-plane. Managed operation of the same tools is part of Aere Cloud, priced in US dollars on that page.
What it is not, yet
- Not a one-click migration. Shield produces the inventory, the plan and the tools; the changes to your keys, certificates and servers are run by you, or by us on contract, and each one is recorded.
- The report for a regulator is a verifiable AIP-23 envelope. It is not an acceptance by any regulator, and no regulator has endorsed it.
- No third-party audit of these modules has been published yet; the README of each names its own tests and negative controls.
- The supported targets are the ones each README names today; a target it does not name is not supported.
How it uses the engine
The exposure report and the migration plan can be notarized on chain 2800, a public network whose every 32nd block carries a post-quantum certificate under its hash, so a report dated today can be shown later to have existed today. The chain is the notary under the tools, not something you buy; what it is and how to check it is at Developers.
Verify it yourself
git clone https://git.aere.network/aere-network/aere-quantum cd aere-quantum/crypto-inventory && node test/proba.mjs # 37 probes with the exact expected findings cd ../readiness && cat README.md # the scanner, its measurement and its limits