English 
Tiếng ViệtAPPLICATION INTEGRATION PRODUCT FAMILY
Trusted PQC Provider Suite
Expose governed cryptographic services through the native interfaces that Windows, Java, .NET, OpenSSL and PKCS#11 applications already understand.
WHY THIS FAMILY EXISTS
Application teams need provider-level integration, not abstract algorithm claims. Every build must define API semantics, key backend, package, compatibility and rollback.
OPERATING JOURNEY
One connected flow, with a clear decision at every boundary.
Provider validates profile and parameters
Key reference resolves to protected backend
Backend performs approved operation
Application receives artifact or result
Diagnostics and manifest prove the combination
NAMED MODULES
Choose the module that solves the actual problem.
01
Windows CNG/KSP
NCrypt integration, certificate store, packaging and application matrix.
Open detailed profile →02PKCS#11
Slot/session/object/mechanism model for native middleware.
Open detailed profile →03Java JCA/JCE
Provider SPI, KeyStore, CMS and Jakarta EE integration.
Open detailed profile →04.NET SDK
Typed C# APIs, CMS examples and native/API bridge.
Open detailed profile →05OpenSSL 3 Provider
Provider dispatch, property governance, CLI, CMS and TLS tests.
Open detailed profile →06macOS & Mobile Track
CryptoTokenKit, keystores, remote signing and user confirmation.
Open detailed profile →NEXT STEP
Select one application integration pilot
Start with one bounded system, exact versions, named owners and measurable evidence.