PQVault is a product of QuantiCor Security Visit QuantiCor Security LinkedIn

PQVault SDK

Post-quantum SDK – quantum-safe in your product, without building a crypto team.

PQC library for your own applications: NIST-standardised schemes per FIPS 203 and FIPS 204, with file format and KMS integration. Your developers call a handful of functions — algorithms, keys and future upgrades are taken care of.

Book a SDK demoFAQ
PQVaultSDK
Share and build

SDK: quantum-safe in your product

Post-quantum encryption in your own product, without building a crypto team. With file format and KMS integration.

PQVault SDK

Post-quantum encryption in your own apps.

Five functions instead of crypto decisions. Your app seals data before it is stored or sent; content and private keys never reach the platform.

  • Five functions: seal, open, sign, verify, keys
  • For web, server and scripts — encrypt single JSON fields
  • Apps with their own keys and scoped credentials
  • Usage, errors and rejections per app in one dashboard
  • IP lists, expiry and developers per plan
Talk to us about the SDK →
PQVaultSDK
SDK in practice

Quantum-safe in your product — without building a crypto team

Your developers call a handful of functions. Algorithms, keys and future upgrades are taken care of.

Health & care software

Encrypt patient data field by field before it reaches your database or a cloud backup.

Finance & insurance

Sign transactions, policies and statements so that any later change is detectable.

SaaS platforms

Offer end-to-end encryption as a feature — customer data stays unreadable even for your own operations.

Devices & industry

Seal telemetry, configurations and update packages between machines and your backend.

01
Register an app

Create the app in the platform and receive credentials that may only do what the app needs.

02
Build it in

Seal, open, sign and verify with a few calls — for web, server and scripts.

03
Run it with oversight

Usage, errors and rejected calls per app at a glance, with IP lists and an expiry date per credential.

Talk to us about your integration

SDK

What SDK does for you

01

What teams use the SDK for

Encrypt patient data field by field, sign transactions, offer end-to-end encryption as a feature of your SaaS.

  • Health and care
  • Finance and insurance
  • SaaS platforms
02

NIST-standardised: FIPS 203 and FIPS 204

The standards NIST published in 2024 for post-quantum key exchange (FIPS 203) and signatures (FIPS 204), optionally hybrid with classical schemes.

  • FIPS 203 / 204
  • Hybrid possible
  • Crypto agility
03

Your KMS. Your keys.

Integration with your existing key management — keys stay in your hands.

  • KMS integration
  • File format
  • Key rotation
04

From trial to OEM

Try it with developer access, then build it into your product — up to an OEM licence. Our sales team will send you a quote.

  • Developer access
  • Built into your product
  • OEM licence
Comparison

SDK compared

PQVault SDKOwn implementationClassic library
Post-quantum schemesYesEffortPartly
File format and KMS integrationYesBuild yourselfNo
Future migrationIn the SDKYourselfYourself
Crypto team neededNoYesPartly
To be honest

What you should know

What SDK can do — and where the limits are.

Part of the duties

The SDK covers state-of-the-art encryption. The other Cyber Resilience Act duties remain with the manufacturer.

Keys

The SDK protects data as well as the key management behind it — hence the KMS integration.

Migration

Schemes may change. The SDK encapsulates them so a switch works without rebuilding your application.

FAQ

Frequently asked questions about SDK

Answers about post-quantum sdk. Your question is not here? We will show you PQVault in a short demo.

01

What does NIST-standardised (FIPS 203 and 204) mean?

In 2024 NIST published the first post-quantum cryptography standards: FIPS 203 for key exchange and FIPS 204 for signatures. The SDK uses exactly these schemes so data stays protected against future quantum computers.

02

Can I use my own KMS?

Yes. The SDK works with your key management; keys stay with you.

03

Which languages are supported?

The SDK is available for Rust, Node.js and Python and as a command line tool (pqv). Further languages on request.

04

Does it help with CRA obligations?

It covers the "state of the art" part for encryption. The other Cyber Resilience Act obligations remain with the manufacturer.

Goes well with

More solutions you may be interested in

Begin in under a minute

Create a free account, then choose a plan whenever you are ready. No card to start, nothing to install — encryption happens on your device, our servers only see ciphertext.

Free plan · 1 user · Upgrade inside your account