Skip to content

Early Access

Post-quantum readiness · BFSI

Are youQuantumReady?

A quantum-safe readiness platform for banks: one cryptographic inventory across code, vendor products, key stores and live endpoints, ranked by regulatory deadline and migrated with evidence an auditor accepts. Installed inside your network.

Inventory · prioritise · migrate · prove — on your own server

Tessera PQC at work: it reads source code, a vendor’s compiled delivery, HSM and cloud key inventories and live TLS and SSH endpoints, read-only, and builds one CycloneDX cryptographic bill of materials. Quantum-vulnerable findings such as RSA-1024 and Diffie-Hellman are ranked by risk with the regulatory deadline that applies. A probe of a live endpoint waits for a second person to approve it, and the re-test confirms hybrid X25519MLKEM768 key exchange. Compliance scores for the DST roadmap, CERT-In, PCI DSS and RBI are produced from evidence, and the evidence pack is signed with Ed25519 and ML-DSA-65.

What it solves

The problem, and what changes.

Before

With Tessera PQC

01

Nobody knows where the bank's cryptography is, and the DST roadmap wants an inventory by December 2027.

One CycloneDX CBOM from code, vendor applications, images, HSMs, cloud KMS and live endpoints, in weeks.

02

Most of it sits inside vendor products and payment schemes you cannot change yourself.

Compiled vendor apps read without source, signed vendor CBOMs verified, and the vendor or scheme named as the owner.

03

Security will not let a scanner loose on production, and the regulator will ask for evidence.

Default-deny scope, two-person approval for every probe, and a signed evidence pack per regulation.

How it works

From where is it, to proof it is fixed.

Tessera PQC reads your estate without writing to it, ranks every finding against the deadline that applies, holds anything that touches the network for a second person, plans the work in waves, and proves the result in an evidence pack signed classically and post-quantum.

Source code7 languagesVendor applicationsno source neededKeys, HSMs, cloud KMSmetadata onlyLive TLS and SSHhosts you nameread, never written toCryptographic inventoryCBOMalgorithmriskRSA-102491DH-102491ECDH · TLS71RSA-204871X2551964ECDSA P-25648Ed255194479 findings · one CycloneDX 1.6 CBOMBy regulatory deadlineNow11Dec 202836Dec 202932Live probependingnetbanking:443in scope · requested by operatorawaiting a second personMigration plan53 tasksWave 1 · weak keysWave 2 · key exchangeWave 3 · signaturesEvidencesigned64DST roadmap scoreCERT-In CBOMPCI DSS 12.3.3RBI Q-SAFEDORAEd25519 + ML-DSA-65verifiable after Q-day

← Swipe for the whole diagram →

Why it's different

The short case for Tessera PQC.

01

10+

Source types

Code, vendor apps, images, keystores, HSMs, cloud KMS, TLS and SSH, in one CBOM.

02

0

Bytes sent out

On your own server, air-gapped if needed. No telemetry, no cloud AI.

03

14

Regulatory profiles

DST, RBI, CERT-In, PCI DSS 12.3.3, DORA, NIST IR 8547 and more.

04

4 wks

To a migration plan

A pilot on your own estate, from install to a prioritised plan.

Questions

Asked first.

Because data recorded today can be decrypted later — harvest now, decrypt later — and because migration takes years. Large institutions have found that the inventory alone takes 12 to 24 months, and it is exactly the first milestone the DST roadmap sets for December 2027.

Tessera PQC is in early access

See it on a synthetic bank engagement, or book a four-week pilot.