Architecture playbook: crypto-agility for the post-quantum era. Learn more
New · Sovereign. Quantum-safe. Agile by design. →

Sovereign, post-quantum security
as a platform.

MyPQC is Malaysia's post-quantum digital security platform. You get four ready-to-use quantum-safe apps, managed PKI and crypto-monitoring services, and a developer API.

It all runs on a Crypto Agility Core Engine, so you can change cryptographic algorithms by policy without touching application code.

NIST FIPS 203 / 204 / 205, plus Malaysia's sovereign KAZ-SIGN · W3C DID · Digital Signature Act 1997

MyPQC platform architecture: API layer, ready-to-use PQC apps, managed services, and the Crypto Agility Core Engine

The NIST post-quantum standards, plus Malaysia's sovereign KAZ-SIGN

NIST FIPS 203 · ML-KEM FIPS 204 · ML-DSA FIPS 205 · SLH-DSA Sovereign KAZ-SIGN W3C DID v1.1

The platform

One platform for the move to post-quantum

The Crypto Agility Core Engine sits at the bottom and decides which algorithms run. On top of it are ready-to-use apps, managed PKI and monitoring, and an API for the vendors and integrators who build on it.

Crypto Agility Core Engine

Risk scoring, agility middleware, PQC orchestration, and policy enforcement. This is the foundation.

Ready-to-use apps

Digital ID, signing, secure file sharing, and quantum-safe messaging. Deploy in days.

Managed services

PQC certificate issuance, digital ID management, and continuous cryptography monitoring.

API layer

One integration surface for enterprise software vendors and Tier-1 system integrators.

Why MyPQC

Sovereign. Quantum-safe. Agile by design.

Sovereign by design

Built and run in Malaysia. It includes KAZ-SIGN, a Malaysian post-quantum signature, alongside the NIST standards.

Post-quantum by default

Post-quantum algorithms are the default for identity, signing, and encryption.

Crypto-agile core

Change algorithms centrally by policy as standards and threats change.

One integrated platform

Inventory, migrate, and run quantum-safe security from one place.

For developers

Quantum-safe crypto in the API you already use

The Antrapol JCE provider keeps the standard Java Cryptography classes (Signature, KeyPairGenerator, Cipher). What changes is that algorithm choice and output packaging are driven by policy. It ships the NIST algorithms ML-DSA, ML-KEM, and SLH-DSA, plus Malaysia's sovereign KAZ-SIGN.

QuantumSafeSigning.java
import java.security.*;
import com.antrapol.jce.Antrapol;

Antrapol.install();

// Post-quantum ML-DSA (FIPS 204) via the standard JCE API
KeyPairGenerator kpg = KeyPairGenerator.getInstance("ML-DSA", "Antrapol");
KeyPair kp = kpg.generateKeyPair();

Signature signer = Signature.getInstance("ML-DSA-65", "Antrapol");
signer.initSign(kp.getPrivate());
signer.update(payload);
byte[] sig = signer.sign(); // agility-encoded, quantum-safe
2035
When NIST's draft roadmap would disallow RSA and ECC
Now
"Harvest now, decrypt later" already puts today's encrypted data at risk
3
Finalized NIST PQC standards: FIPS 203, 204, 205

Start your post-quantum migration

See MyPQC in action and get a quantum-readiness assessment for your organization.