01
Features
Post-quantum data encryption software with the features you need across the data stack: CLI, GUI, TUI, and MCP server. From personal use to business deployments. Professional services (database migration, cold storage PQC, migration-as-a-service, PQC readiness assessment) are scoped separately; see Pricing.
These are the features of the Standard edition. The Approved Mode and CNSA 2.0 editions (not released) offer fewer algorithms and features: compare the three editions.
Core Capabilities
02
Argon2id
Memory-hard KDF: every password guess costs real memory, even on GPUs and ASICs.
03
AES-256-GCM
Authenticated encryption. Detects any tampering instantly.
04
Network Lock
File operations run on your device, and there is no cloud storage of your files. Apart from remote backup that you set up yourself (ciphertext only, to storage you choose), the only network path is an encrypted licence check (operation type, data size, algorithm and program version; never file names or contents), pinned to billing.quantumsequrity.com by application-layer controls. On Linux, seccomp-bpf then blocks every network call before any cryptographic work (seccomp cannot filter by host); on Windows, run as administrator, a firewall rule does the same.
05
Secure Shred
Three-pass overwrite, then delete. On SSDs and copy-on-write file systems old copies can survive any overwrite, so encrypt sensitive data from the start.
06
Zstd Compression
Compress before encrypt. Smaller files, same security.
NIST ACVP Test Vectors
19,769 NIST ACVP vectors passed, zero failures, out of 31,071 attempted in ACVP-Server v1.1.0.43 (commit 975de31eb83d87), replayed against the open-source libraries QNSQY ships (September 2026 sweep). 11,302 vectors skipped, each with a logged reason (options QNSQY does not implement, such as bit-oriented hash messages, SP 800-56C two-step key derivation, Ed448 and Curve448). 36 of 55 algorithm directories at 100% NIST coverage, including HMAC (all 22 directories), ML-KEM keyGen and encapDecap, ML-DSA keyGen, sigGen and sigVer, SLH-DSA across all 12 parameter sets, SHA-2-256 / 512 / 512-256, and SHAKE-128 (FIPS 202).
Reproducible: a standalone, self-contained reproducer harness with step-by-step instructions is published on the Validation page; full source access for customers and auditors is available on request under NDA. These are NIST ACVP test vectors replayed against the algorithm implementations compiled into the shipped qnsqy binary's own source tree, plus internal end-to-end format tests. This is reproducible test-vector evidence, not FIPS 140-3 / CMVP certification (on the roadmap), and not an external audit. See the full write-up.
New in Recent Releases
Shipped in the standard downloads since late September 2026. The release notes say which apps have each one.
- CBOM export.
qnsqy scan <dir> --format cyclonedxwrites a CycloneDX 1.6 cryptography bill of materials of the keys, certificates and encrypted files it finds. The read-only scan is free on every plan (an account is needed). - OMB M-23-02 inventory report. The scan writes the memo's nine-item inventory of one system as CSV, Excel or JSON, and flags each algorithm that is not a FIPS-approved security function.
- Standard formats with post-quantum keys.
encrypt --carrierwrites CMS or S/MIME for an ML-KEM recipient certificate, age for a post-quantum age recipient, or JWE. Checked against published test vectors; tests against other tools are still to come. - Size sealing.
--paranoidpads the data to a published bucket size, so the file length reveals only the bucket, not the exact size. - Text form.
--armorwrites the encrypted file as ASCII text, for channels that carry text only. - SHA-512 hash profile.
--hash-profile sha512uses the SHA-2 family for the file format's own hashing, chosen per file. The default stays SHA3 and BLAKE3. - AI agents. The MCP server works with standard MCP clients.
- Security notices. Signed-in Pro and Business apps name the fixed version when a released version has a security problem. Nothing stops working.
- Hardening. Hedged ML-DSA signing, and a Linux sandbox guard against the x32 system-call route.
Approved-Mode and CNSA 2.0 Builds
Built and tested internally. Not yet released. Two new builds of QNSQY: an approved-mode build that allows approved algorithms only (ML-KEM, ML-DSA, AES-256-GCM, SHA-256/384/512, SHA3-256 for the hash command, HMAC-SHA-512 and PBKDF2-HMAC-SHA-512) and runs start-up self-tests before first use, and a CNSA 2.0 build narrowed to ML-KEM-1024, ML-DSA-87, AES-256-GCM and SHA-384/SHA-512, with an offline license and no network use. Both ran on Windows 11 in a virtual machine, as a standard user and as an administrator. The approved-mode build refuses features that are not approved, such as the vault and steganography; they stay in the standard build described on this page. Its MCP server for AI agents offers only the tools of approved commands.
QNSQY is not FIPS 140-3 validated. QNSQY holds no CMVP certificate, and no lab has tested it. The CNSA 2.0 build carries no NSA, NIAP or CSfC approval. FIPS 140-3 validation is on the roadmap, not started; it needs an accredited lab and NIST review. Details, limits and the roadmap: Approved-mode and CNSA 2.0 builds.
Feature Comparison by Tier
| Feature | Free | Pro | Business |
|---|---|---|---|
| Key Encapsulation (Hybrid KEM) | |||
| ML-KEM-512 + X25519 | |||
| ML-KEM-768 + X25519 | |||
| ML-KEM-1024 + X25519 | |||
| HQC-128 + X25519 (Code-based) | |||
| HQC-192 + X25519 | |||
| HQC-256 + X25519 | |||
| Symmetric Encryption | |||
| AES-256-GCM | |||
| XChaCha20-Poly1305 | |||
| Digital Signatures | |||
| ML-DSA-44 (NIST Level 2) | |||
| ML-DSA-65 (NIST Level 3) | |||
| ML-DSA-87 (NIST Level 5) | |||
| SLH-DSA (Hash-based) | |||
| Ed25519 (classical, inside the hybrid signatures) | |||
| Hybrid ML-DSA + Ed25519 | |||
| FN-DSA-512 (Falcon, NTRU lattice) | |||
| FN-DSA-1024 (Falcon) | |||
| Hybrid FN-DSA + Ed25519 | |||
| LMS (Stateful hash-based, SP 800-208) | |||
| Hashing & Integrity | |||
| BLAKE3 | |||
| Merkle Tree Verification | |||
| HKDF-SHA3-256 | |||
| Password Hashing (Argon2id) | |||
| 128 MB / 3 iterations | |||
| 256 MB / 4 iterations | |||
| 512 MB / 6 iterations | |||
| Custom Parameters | |||
| Commands | |||
| encrypt / decrypt | |||
| shred (secure delete) | |||
| hash / hash-verify | |||
| encode / decode | |||
| sign / verify | |||
| batch (multiple files) | |||
| rekey (password change) | |||
| symmetric (password-only) | |||
| vault (password manager) | |||
| split / combine (Shamir) | |||
| threshold-encrypt / threshold-decrypt (M-of-N) | |||
| keyfile (generate/encrypt/decrypt) | |||
| deniable (create/open) | |||
| timelock encrypt / decrypt / calibrate | |||
| stego hide / extract / capacity | |||
| scan (read-only, CycloneDX CBOM and OMB M-23-02 reports) | |||
| migrate (re-encrypt what the scan finds) | |||
| groups / policy / escrow | |||
| polyglot (embed in PDF/ZIP/PNG) | |||
| provenance (account provenance signing) | |||
| push / pull / sync (zero-knowledge remote backup to R2 or S3) | |||
| verify-release (check a QNSQY download's ML-DSA-87 signature) | |||
| Advanced (Pro & Business) | |||
| Triple-polyglot (JPEG + ZIP + PDF in one) | |||
| Self-extracting polyglot (.sh / .bat carrier) | |||
| Tripwire URL (canary token in PNG) | |||
| Keyfile-from-any-file (BLAKE3 derived AES key) | |||
| ABE (Attribute-Based Encryption, PQC-safe) | |||
| Interfaces | |||
| Command-line (CLI) | |||
| Graphical UI (GUI, Linux .deb/.rpm and Windows installer) | |||
| Terminal UI (TUI) | |||
| MCP server (Model Context Protocol, JSON-RPC 2.0; tools follow your plan) | |||
| Limits & Features | |||
| Max File Size (command line) | No limit (ML-KEM-512) | No limit up to ML-KEM-768; 25 GB with ML-KEM-1024 | No limit |
| Zstd Compression | |||
| Streaming Mode | |||
| Security & Audit | |||
| Memory Protection (mlock) | |||
| Sandbox (seccomp-bpf) | |||
| Audit log kept (encrypted, hash-chained; view it on Pro) | |||
| Audit log view, export (CSV, JSON, syslog, CEF) and chain check | |||
| Signed audit trail (ML-DSA signatures on the hash chain) | |||
| Shamir Secret Sharing | |||
| License | |||
| Personal Use | |||
| Commercial Use | |||
| Priority Support | |||
Who QNSQY Is For
Legal Professionals
Client confidentiality with decades-long retention requirements
Healthcare Organizations
Long-retention patient record protection. HIPAA encryption requirements are your auditor's call; QNSQY provides the algorithm choices and audit artifacts.
Financial Institutions
Long-retention protection for financial data and trade secrets (QNSQY is not SOC 2 or PCI DSS certified; your auditor owns the compliance call)
Journalists & Activists
Source protection and confidential communications
Research Institutions
Intellectual property and grant data security
Privacy-Conscious Individuals
Family documents, passwords, private memories
Pro Tier Features
A
Streaming Encryption
Process files of any size without loading them entirely into memory. Essential for encrypting large databases, backups, and video files on systems with limited RAM.
B
Memory Locking
Keeps passwords and keys out of swap, so they are not written to disk. Every plan has it. It does not protect the memory of a running machine.
C
Hash-Based Signatures (SLH-DSA)
Sign files with FIPS 205 hash-based signatures. SLH-DSA doesn't rely on lattice mathematics, providing an alternative post-quantum approach. Choose SLH-DSA-128s/192s/256s based on your security level needs.
D
Key Management
Generate, import, and export signing keypairs. Share public keys with colleagues. Manage multiple identities. Full control over your cryptographic keys.
E
Audit Logging
Track all cryptographic operations. Know when files were encrypted, decrypted, signed, or verified. Essential for compliance and security audits.
F
Commercial License
Use QNSQY in commercial settings. Deploy across your organization. Integrate into business workflows without licensing concerns.
Pro Tier Exclusive
01
Hybrid Signatures (ML-DSA + Ed25519)
Defense-in-depth signatures using AND construction. Both ML-DSA (post-quantum) and Ed25519 (classical) signatures are computed. Verification requires BOTH to be valid. If either algorithm is broken, the other still protects.
02
Password Change (Rekey)
Change the password on encrypted files without decrypting and re-encrypting the entire file. Required for key rotation policies across many files.
03
Higher Argon2 Presets
Access the 256 MB / 4-iteration Argon2id preset for stronger password hashing. Business tier adds the 512 MB / 6-iteration preset and fully custom parameters.
04
Algorithm Selection
Full control over cryptographic algorithms. Choose between AES-256-GCM and XChaCha20-Poly1305. Select ML-DSA or SLH-DSA signature algorithms. Configure hybrid modes for maximum security.
05
Password Vault
Encrypted password/secret manager. Master password → Argon2id → AES-256-GCM vault. Single encrypted blob prevents metadata leakage. CSPRNG password generator.
06
Batch Operations
Encrypt, decrypt, or shred multiple files in a single command. Essential for workflows involving large numbers of documents or automated pipelines.
07
Audit Logging
Track all cryptographic operations in an encrypted, hash-chained log you can view and export. Know when files were encrypted, decrypted, signed, or verified. Business adds ML-DSA signatures on the chain.
08
Large Files
On the command line, Pro has no file-size limit with ML-KEM-512 or ML-KEM-768 and allows up to 25 GB per file with ML-KEM-1024. Files are encrypted in chunks, so databases, backups and media libraries do not need to fit in memory. The desktop app in the current release stops at 25 GB per file on Pro.
Advanced (Pro & Business)
Five capabilities on the Pro and Business plans. The data they carry is encrypted with QNSQY's post-quantum encryption (key-from-file uses AES-256 directly), and all five run on your device. Free accounts can upgrade to Pro to use them.
R1
Triple-Polyglot
One artefact that opens correctly as JPEG, ZIP, and PDF at the same time, with the encrypted payload hidden inside. Survives upload to platforms that strip metadata, because every byte serves three legitimate formats. Available on Pro and Business.
R2
Self-Extracting Polyglot
A .sh or .bat carrier that re-execs qnsqy on itself when run, decrypting in place. Rename the same artefact to .png and it opens as an image. Two faces, one signed payload. Pro and Business.
R3
Tripwire URL (Canary Token)
Embed your own tracking URL in a PNG carrier (stored unencrypted, in a text chunk). A tool that loads remote resources and follows it contacts your URL, which can alert you; most image viewers do not follow it. Useful for bait data and leak attribution. Pro and Business.
R4
Keyfile-From-Any-File
Derive a 256-bit AES key from any data you already own. An MP3, a photo, a scanned document, anything. BLAKE3 turns the carrier into a deterministic 256-bit key. The key is only as secret as the file: pick one no one else has a copy of. The carrier looks innocuous; only you know it doubles as a key. Pro and Business.
R5
ABE: Attribute-Based Encryption
Encrypt under a policy expression like (role=doctor AND dept=cardio) OR clearance>=4. Every recipient whose attributes satisfy the policy can decrypt. On Pro the policy picks the recipients when you encrypt; Business adds authority-issued attribute keys, so only a key set that satisfies the policy can rebuild the file key. Post-quantum ML-KEM keys, no classical pairings. Pro and Business.
Business Tier: Full Platform
Business includes everything in Pro plus advanced algorithm families, threshold cryptography, and organizational tools. Maximum algorithm diversity means if a vulnerability is found in one family, you have alternatives ready.
01
FN-DSA (Falcon) Signatures
NTRU-lattice signatures, pre-standard: FIPS 206 is not yet published. FN-DSA-512 produces signatures around 666 bytes, the most compact of the NIST-selected post-quantum signatures. Standalone or hybrid with Ed25519.
02
HQC Key Encapsulation
Code-based KEM selected by NIST as a backup to ML-KEM. Uses error-correcting codes instead of lattices. Hybridized with X25519 by default for defense in depth; pure HQC is available on Business. Three security levels: HQC-128, HQC-192, HQC-256.
03
LMS Stateful Signatures
Hash-based signatures per NIST SP 800-208. Security rests only on the hash function (second-preimage resistance of SHA-256, RFC 8554), with no algebraic assumptions. Stateful: each signature consumes a one-time key leaf. Four parameter sets, from 32 signatures to about 1 million.
04
Threshold Encryption (M-of-N)
Encrypt to N recipients, requiring M keys to decrypt. Each share protected by ML-KEM public keys. Ideal for organizational key escrow and multi-party access control.
05
Key Recovery (Shamir)
M-of-N threshold key recovery using Shamir's Secret Sharing. Split your secret among trusted parties. Any M of N shares can reconstruct it. Ideal for organizational continuity and disaster recovery.
06
Groups, Policy & Escrow
Define recipient groups, enforce encryption policies across your organization, and configure key escrow for compliance. Set minimum password requirements, mandatory signing, and other security baselines.
07
Deniable Encryption
Two passwords, two payloads, one container. Real password reveals real data; decoy password reveals plausible cover data. Container is indistinguishable from random bytes.
08
Time-Lock Encryption
Encrypt data so it requires a calibrated amount of sequential computation to decrypt. No secret key needed for time-release. It uses an RSW time-lock puzzle (repeated squaring modulo a 2048-bit RSA number), which cannot be parallelized. The delay rests on factoring, which a large quantum computer could break, so treat the delay as a classical guarantee; add a recipient key (ML-KEM) or a key file when the data must stay protected after the delay.
09
Steganography
Hide encrypted data inside PNG images. The output looks like a normal photo. Useful when you need to conceal the existence of encrypted data, not just its contents.
10
PQ Migration Scanner
Scan directories for files protected with classical-only cryptography (free on every plan, with CycloneDX CBOM and OMB M-23-02 reports), then migrate them to post-quantum hybrid encryption (Business).
11
Keyfile Encryption
Encrypt/decrypt using only a 256-bit key file (no password). AES-256-GCM with the key file directly. Generate, encrypt, and decrypt with qnsqy keyfile. Pro and Business.
12
Unlimited File Size
No restrictions on file size. Encrypt multi-terabyte databases, complete system backups, and large media libraries without artificial limits.
Ready to get started?
Download the free tier and start encrypting your data with quantum-safe algorithms today. For database, backup, or cold-storage migration at scale, see professional services.