Question 1

What is post-quantum cryptography?

Accepted Answer

Post-quantum cryptography (PQC) refers to cryptographic algorithms that are secure against attacks by both classical and quantum computers. Current widely-used algorithms (RSA, ECC) will be broken by sufficiently powerful quantum computers using Shor's algorithm. NIST standardized three post-quantum algorithms in 2024: ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205). Quantumize implements all NIST-standardized PQC algorithms plus Round 4 candidates (HQC, Classic McEliece).

Question 2

What are NIST FIPS 203, FIPS 204, and FIPS 205?

Accepted Answer

NIST finalized three post-quantum cryptography standards in August 2024: FIPS 203 (ML-KEM, based on CRYSTALS-Kyber) for key encapsulation mechanisms, FIPS 204 (ML-DSA, based on CRYSTALS-Dilithium) for digital signatures, and FIPS 205 (SLH-DSA, based on SPHINCS+) for stateless hash-based digital signatures. These replace RSA and ECC in quantum-threatened environments. Quantumize supports all three standards with all parameter sets (ML-KEM-512/768/1024, ML-DSA-44/65/87, SLH-DSA).

Question 3

Which post-quantum algorithms does Quantumize support?

Accepted Answer

Quantumize supports all NIST-standardized algorithms: ML-KEM-512/768/1024 (key encapsulation, FIPS 203), ML-DSA-44/65/87 (digital signatures, FIPS 204), and SLH-DSA (stateless hash-based signatures, FIPS 205). NIST Round 4 candidates: HQC-128/192/256 and Classic McEliece. Legacy/hybrid algorithms: CRYSTALS-Kyber, CRYSTALS-Dilithium, Falcon, NTRU. GPU acceleration via NVIDIA cuPQC is available for high-throughput ML-KEM and ML-DSA workloads.

Question 4

How does Quantumize integrate with AWS KMS?

Accepted Answer

Quantumize uses AWS KMS for envelope encryption: each file is encrypted with a unique data key, and that data key is wrapped (encrypted) by an AWS KMS Customer Managed Key (CMK). The connection between Quantumize and AWS KMS is secured with post-quantum TLS using X25519Kyber768Draft00 hybrid key exchange via the AWS Common Runtime (awscrt). This means your key material is protected against harvest-now-decrypt-later attacks in transit. AWS KMS provides FIPS 140-2 validated hardware security modules for key storage.

Question 5

Does Quantumize support NVIDIA GPU acceleration?

Accepted Answer

Yes. Quantumize integrates with NVIDIA cuPQC (CUDA Post-Quantum Cryptography) to accelerate ML-KEM and ML-DSA operations on NVIDIA GPUs. This enables high-throughput batch encryption and signing workloads — for example, encrypting thousands of files per second on A100 or H100 GPUs. GPU acceleration is available for enterprise on-premises deployments and AWS EC2 GPU instances. Quantumize is a member of the NVIDIA Inception program.

Question 6

Is Quantumize FIPS compliant?

Accepted Answer

Quantumize uses FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA) standardized algorithms as finalized by NIST in August 2024. AWS KMS envelope encryption provides FIPS 140-2 validated key management through AWS hardware security modules. SOC 2 Type II audit is in progress. FedRAMP ATO Low baseline is on the roadmap. Enterprise customers requiring a FIPS-compliant deployment should contact sales for a dedicated compliance review.

Question 7

How do I migrate from RSA or ECC to post-quantum cryptography?

Accepted Answer

Quantumize supports a hybrid migration strategy: you can encrypt new files with post-quantum algorithms immediately while keeping existing RSA/ECC-encrypted files accessible. The platform provides: (1) a migration wizard in the admin console to re-encrypt existing files with ML-KEM or ML-DSA, (2) algorithm lifecycle policies that set deprecation timelines and automatically flag files using weak algorithms, (3) a REST API and CLI for scripted bulk re-encryption. NIST recommends migrating to ML-KEM for key encapsulation and ML-DSA for signatures as the first priority.

Question 8

What is the pricing model for Quantumize?

Accepted Answer

Quantumize offers a free tier with core encryption and signing features. Enterprise plans include volume pricing for storage and operations, dedicated AWS KMS keys, SSO (SAML/OIDC), ABAC policy management, multi-cloud KMS (Azure Key Vault, GCP Cloud KMS), audit logs, and SLA guarantees. AWS Marketplace listing is in progress for simplified procurement. Contact sales@quantumize.com for a custom quote or to schedule a compliance review.

Question 9

Does Quantumize have an SDK or API?

Accepted Answer

Yes. Quantumize provides a Python SDK (available on PyPI), a Node.js SDK (@quantumize/sdk on npm), a CLI tool, and a REST API documented with OpenAPI/Swagger (available at /api/v1/docs). Enterprise integrations include SAML 2.0 and OIDC SSO with JIT provisioning, AWS Marketplace, and multi-cloud KMS support for AWS KMS, Azure Key Vault, and GCP Cloud KMS.

Question 10

How does Quantumize handle enterprise key management?

Accepted Answer

Quantumize implements a multi-layer key management architecture: (1) Per-file unique data keys generated with a CSPRNG, (2) Org-level key encryption keys (KEKs) stored in AWS KMS with FIPS 140-2 HSMs, (3) Optional per-org Customer Managed Keys (CMK) in AWS KMS, Azure Key Vault, or GCP Cloud KMS, (4) ABAC (Attribute-Based Access Control) policies that enforce who can encrypt, decrypt, sign, or verify per file and per algorithm, (5) Comprehensive audit logs for all key operations. Key material never leaves the HSM in plaintext.