Post-Quantum Readiness Platform

Know your quantum exposure
Fix it before it matters.

Quantinus finds the certificates, keys and protocols running in your environment, and ranks what is weak or quantum-vulnerable.

PCI DSS 12.3.3 PCI DSS 4.2.1.1 HIPAA (proposed) CCCS ITSM.00.501
Check which rules apply — 2 minutes Request early access

No professional services. No implementation team. No consulting fees. Results in minutes.

From first scan to a ranked fix list.

01 — AGENT DEPLOY
Network, machines and cloud.
Run the lightweight Quantinus agent inside your environment, on your schedule. It reads cryptographic configuration, never traffic or private keys: TLS and SSH endpoints and database listeners on your network; certificate files, certificate stores and disk encryption on the machine it runs on; and AWS certificate and key metadata, with your read-only credentials.
02 — CLASSIFY
Quantum risk scoring.
Findings are graded for severity and post-quantum risk, and rolled up into a Hygiene grade and a PQ Readiness score. Inventory records are listed, not scored. Findings are mapped to the framework requirements in our compliance mapping.
03 — REPORT
Four reports, including PCI DSS 12.3.3 evidence.
An executive summary for your board or CISO; a compliance report mapping findings to the frameworks they relate to; technical detail on every finding, with locations; and a 12.3.3 evidence report for your assessor, covering your inventory, monitoring history and changes over the last 12 months. Each opens as a web page you can print or save as a PDF.
04 — MIGRATE
Ranked fixes, each with a target.
Findings ranked by severity, each with the target state to move to. For classical key exchange, that target names the ML-KEM hybrid to enable.

What the platform gives you

Executive dashboard
An executive briefing with a Hygiene grade, a PQ Readiness score and compliance status in one view. Open it as a report and save it as a PDF for your board.
Multi-framework compliance
Findings are checked against the requirements in our framework mapping. The dashboard shows the share of mapped requirements passing, and the compliance evidence report lists each requirement as pass or fail.
Privacy-first architecture
The agent never transmits private keys or plaintext secrets. Only metadata and risk signals leave your environment. Each customer’s data is isolated with row-level security on every dashboard and API read.

Which rules actually apply to you?

A few questions, about two minutes. You get a plain-language summary of the requirements that apply to your situation: what each one asks for, what Quantinus covers, what it does not cover, and what is at stake.

No email required to see your result.

Start the questionnaire

Evidence for 12.3.3 and 4.2.1.1

Requirement 12.3.3 asks for a documented inventory of the cipher suites and protocols you use, reviewed every 12 months. Requirement 4.2.1.1 asks for an inventory of the trusted keys and certificates that protect cardholder data in transit. Both have been required since 31 March 2025.

Quantinus produces a dated inventory of the certificates, TLS settings and SSH keys it finds, with weak algorithms flagged, and a 12.3.3 evidence report covering 12 months of monitoring and changes. It covers the transmission and certificate side, not stored-data encryption or password protection, and it does not decide whether you meet the requirement. Your QSA does.

Source: PCI DSS v4.0.1, Requirement 12.3.3 (p. 299) and Requirement 4.2.1.1 (p. 116), PCI SSC document library.

What Quantinus scans

This list is what the agent does today. Anything not on it, we do not claim.

Network and transport
TLS endpoints: the negotiated protocol version and key exchange, and the certificate chain served
Legacy protocol detection: which of TLS 1.0 and TLS 1.1 an endpoint still accepts, including when it negotiates a modern version with a normal client. The probes can be turned off with --no-legacy-probes where security monitoring flags them.
Optional full enumeration (--enum-suites): every protocol version, cipher suite and TLS 1.3 key-exchange group an endpoint accepts, post-quantum hybrids included
SSH: the host key the server presents, and the host-key and key exchange algorithms it offers
Databases (--scan-db): whether PostgreSQL, MySQL/MariaDB, SQL Server, MongoDB and Redis offer or require TLS, and the certificate they serve. No username or password is ever sent.
On the machine
PEM, DER and PKCS#12 files in directories you point the agent at
Certificate stores (--scan-stores): Windows LocalMachine and CurrentUser, and the Linux trust-store paths. Read-only; private keys are never requested.
Disk encryption (--scan-disk): BitLocker, LUKS and FileVault status. Never recovery keys or passphrases.
The same certificate found in several places is recorded once, with each location listed
Cloud
AWS (--aws): ACM certificates, KMS key metadata, and Secrets Manager metadata, including which key encrypts each secret. Uses your read-only credentials. Never secret values or key material.
What is flagged
SHA-1, MD5 and MD2 certificate signatures
RSA keys under 3072 bits, in certificates and SSH host keys. 2048-bit keys are flagged at medium severity as lacking long-term margin.
DSA keys
Expired certificates
TLS 1.0 and TLS 1.1 still accepted
Static RSA key exchange
TLS or SSH key exchange without a post-quantum hybrid
Certificates with classical keys (RSA, ECDSA, Ed25519) still valid for more than five years
Weak cipher suites, with full enumeration
Database listeners that do not offer or do not require TLS
Unencrypted volumes, and suspended disk encryption
AWS KMS keys using classical algorithms
A note on absence

If the agent does not detect something, that means it was not detected. It does not mean the thing is absent, and we do not report it as such. A server that refuses a probe may still support what we could not confirm.

Not covered today
Azure Key Vault (in progress), Google Cloud and HashiCorp Vault key stores
Java keystores (JKS)
Hardware security modules and TPMs
Code signing and CI/CD secrets
Email and messaging keys
Database and backup encryption at rest, application-level encryption, and how passwords are stored
STARTTLS on mail and directory services
The macOS Keychain

Some of these are on the roadmap. None of them are in the product today.

Two questions for every finding

Every finding has a severity — critical, high, medium or low — for how weak it is today, and one badge for what kind of problem it is. These are the same badges you see in the dashboard.

PQ Blocker
Quantum-vulnerable: prioritise it
Key exchange without a post-quantum hybrid, which traffic recorded today exposes once a quantum computer can break it; static RSA key exchange; certificates with RSA or ECDSA keys valid for more than five years.
PQ Signal
Quantum-relevant, with a longer window
Classical certificate keys that expire within five years, and the post-quantum hybrid key exchanges we detect.
Agility Gap
Sound today, needs replacing in time
For example RSA-2048 keys, which meet current minimums but lack long-term margin, flagged at medium severity.
Security Gap
Weak today, unrelated to quantum
A database listener that does not require TLS, an unencrypted volume, or disk encryption that has been suspended.

A larger RSA or elliptic-curve key does not protect against a quantum computer; only migrating does.

Pricing

Not published yet. Email hello@quantinus.io and we will talk about your situation.

Help your clients get quantum-ready. Earn recurring revenue.

Quantinus partners help their clients find and fix weak and quantum-vulnerable cryptography. You bring the relationships. We bring the platform.

Apply: partners@quantinus.io →

Referral Partner
Recurring commission
Introduce clients and earn recurring revenue on them, on terms we agree with you in writing. No certification required. Ideal for consultants, advisors, and VARs.
Certified Partner
Services alongside the platform
Deliver services alongside the platform, with direct access to the team building it. Ideal for MSSPs and cybersecurity consultancies.
Strategic / MSSP
By invitation · Custom terms
For larger MSSPs and consultancies with significant client bases. Custom commercial terms and joint go-to-market, by conversation.
Assessors and QSAs
No commission
If you assess clients against PCI DSS 12.3.3 or 4.2.1.1, we will walk you through what our evidence report contains and how it is produced. No commission: assessors stay independent of what they assess.

How we protect your data

Security is not a feature we add — it is the foundation we build on.

Data minimization

The agent sends cryptographic metadata only. Private keys, plaintext secrets and the contents of network traffic never leave your environment.

Encryption in transit and at rest

Encrypted in transit with TLS 1.2 or 1.3; older versions are refused. Data at rest is encrypted by our hosting providers, Railway and Vercel, as their data processing agreements state.

Vulnerability disclosure

Report vulnerabilities to hello@quantinus.io with the subject line “Security Disclosure”, or see our security.txt. We will acknowledge your report and keep you updated as we investigate.

Access controls

Admin and member roles for each organization. Every change to a finding’s status is recorded with who made it and when.

Customer data isolation

Each customer’s data is isolated with row-level security on every dashboard and API read. Those reads use a database role that cannot bypass it.

Our own PQ readiness

Our website and dashboard negotiate the X25519MLKEM768 post-quantum hybrid. Our API does not yet; our own scanner flags it, and we track it like any customer finding.

Ready to know your
quantum exposure?

Join early access. We are onboarding a small number of teams now.
If you have a 12.3.3 finding to close or an assessment coming, we want to hear about it.

Or email us at hello@quantinus.io

By submitting you agree to our Privacy Policy and Terms of Service.