Enterprise & Government
QNSQY for organizations and public agencies. Pricing depends on scope: tell us what you need to protect, and we will quote it.
What you can buy
Every item is quoted for your scope.
| Offer | What you get |
|---|---|
| Enterprise site license | Organization-wide use under one contract: volume seats, a signed SLA, guided onboarding, a named contact and a quarterly readiness review. |
| Archive server license | One backup or archive server, licensed per machine instead of per person. |
| PQC readiness assessment | A review of your cryptography: inventory, CBOM report and a ranked migration plan, at a fixed price agreed before work starts. |
| Migration services | Re-encryption of databases, backups and cold storage, migration as a service, and help integrating with your KMS, HSM and SIEM. |
| Government builds | The approved-mode build and the CNSA 2.0 build for agencies and defense, by proposal. See the comparison below. |
Services deliver working post-quantum protection and evidence your own auditor can review. They do not create a certification.
Security built in
Available now in the standard build, on the plans shown. Team features in detail.
| Control | What it does | Plans |
|---|---|---|
| Post-quantum encryption | ML-KEM (FIPS 203) with an X25519 hybrid and AES-256-GCM. Data and keys never leave your machines. | Every plan |
| Post-quantum signatures | ML-DSA (FIPS 204) and SLH-DSA (FIPS 205), plus LMS (SP 800-208) on Business. | Free (ML-DSA-44), Pro and up |
| PQC scan and CBOM report | Finds data still protected by RSA or ECC and exports a Cryptographic Bill of Materials for auditors. | Every plan |
| Bulk migration | Re-encrypts the data the scan finds with post-quantum encryption. | Business, Enterprise |
| Two-person rule | Threshold (M-of-N) encryption: sensitive data opens only when several trusted people approve together. | Business, Enterprise |
| Key escrow and recovery | Organizational recovery without the user's password; every recovery is written to the audit log. | Business, Enterprise |
| Organizations, roles and single sign-on | Owner, admin and member roles; SSO over OIDC; magic-link onboarding; device sign-in for the command line. | Business, Enterprise |
| Signed encryption policy | An Ed25519-signed, versioned policy that the client enforces on each device before any data is touched. | Business, Enterprise |
| Audit trail | A hash-chained log of cryptographic operations, a per-organization admin log, and SIEM export (CEF, JSON, Syslog). | Pro and up; admin log and SIEM on Business |
| Network lock | On the Linux command line, QNSQY blocks its own network access while an operation runs. Other programs keep their network. | Every plan |
| Open file format | The .qs format is publicly specified, and its media type has been submitted to IANA, so you can always read your own data. | Every plan |
| Public test evidence | NIST ACVP vectors, Google Wycheproof and fuzzing, reproducible on our validation page. Tested, not certified. | Public |
Standard, approved-mode and CNSA 2.0 builds
The approved-mode build allows approved algorithms only. The CNSA 2.0 build narrows it for defense, fully offline. Both are built and tested internally and not yet released.
Swipe sideways to see every build.
| Topic | Standard buildPlans on the pricing page | Approved-mode buildFIPS 140-3 preparation | CNSA 2.0 buildDefense, offline |
|---|---|---|---|
| Status | Available now | Not yet released | Not yet released |
| Who it is for | Companies, hospitals, banks and individuals | Agencies that allow approved algorithms only (FIPS 140-3 preparation) | Defense and national-security users |
| Encryption | ML-KEM-512/768/1024 with X25519 hybrids, HQC, AES-256-GCM, XChaCha20-Poly1305 | ML-KEM-512/768/1024 (FIPS 203) and AES-256-GCM | ML-KEM-1024 and AES-256-GCM only |
| Signatures | ML-DSA, SLH-DSA, FN-DSA, LMS, Ed25519 hybrids | ML-DSA-44/65/87 (FIPS 204), with hedged signing | ML-DSA-87 only. Every encrypted item is signed, and the signature is checked before any plaintext is written |
| Hashing and passwords | BLAKE3, SHA-3, Argon2id for passwords | SHA-256/384/512, SHA3-256 for the hash command, HMAC-SHA-512, PBKDF2-HMAC-SHA-512 | SHA-384/SHA-512. No SHA-3, no passwords |
| Can the limits be switched off? | — | No. Fixed when the program is built: no flag, setting or license can switch it off | No, same as approved-mode |
| Start-up self-tests | — | Known-answer tests, a software integrity test, and a pairwise test on every new key pair. Any failure stops the program (exit code 70) | Same as approved-mode |
| Features that are not approved | Included by plan: vault, steganography, time-lock, threshold, deniable, polyglot, keyfile, escrow, MCP server | Refused | Refused |
| License | Online check with our billing server; works offline up to 7 days after a check | Online check with our billing server | Offline license signed with ML-DSA-87 and bound to one device; decrypt and verify keep working after it expires |
| Network | Network lock during operations on the Linux command line | Online license check; on Windows it blocks its own outbound traffic while an operation runs | No network use. On Linux a kernel filter ends the process if it opens a network socket; on Windows there is no network code |
| Apps | Desktop app, command line, terminal app and MCP server | Desktop and terminal apps; MCP server refused | Desktop and terminal apps |
| Platforms | Linux and Windows | Linux x86-64; full Windows 11 test still in development | Linux x86-64; full Windows 11 test still in development |
| Certification | Not FIPS 140-3 validated | Not FIPS 140-3 validated; no CMVP certificate. On Linux part of the cryptography runs in the AWS-LC FIPS module, whose certificate does not cover this build | Not FIPS 140-3 validated; no NSA, NIAP or CSfC approval |
| How to buy | Plans on the pricing page | By proposal | By proposal |
All safeguards in the restricted builds Full list
| Safeguard | What it does |
|---|---|
| Random numbers | An SP 800-90A deterministic random bit generator: AWS-LC's CTR_DRBG on Linux, QNSQY's own HMAC_DRBG with SHA-512 on Windows. |
| Service indicator | An "Approved service" line for every operation, and a second line when a service that is not approved (the license check) ran. |
| Separate state | Its own state folder, never shared with the standard build. The zeroize command overwrites and removes it. |
| Private keys at rest | Always passphrase-protected with PBKDF2-HMAC-SHA-512 and AES-256-GCM in the approved-mode build. Unprotected keys are refused. |
| Header tamper protection | A keyed MAC over the header, which also covers the key-encapsulation block, and strict checks of reserved header bytes. |
| Size sealing | Optional. Hides the original data size. Older readers refuse sealed data instead of misreading it. |
| Text form | A text (ASCII) form of protected data, for channels that carry only text. |
| CMS and S/MIME | Signing, checked with OpenSSL. Encryption is checked against published examples only, not yet against another implementation. |
| Data inventory | Scan, migrate and audit commands, with an OMB M-23-02 nine-item inventory report (CSV, XLSX, JSON) that holds no file names, paths or host names and can carry an ML-DSA signature. |
| Signed audit trail (CNSA 2.0 build) | A SHA-512 hash chain signed with ML-DSA-87. It cannot be reset. |
| Certificate checks (CNSA 2.0 build) | Public keys can be checked against your certificate chain, without revocation checking because the build is offline. |
The CNSA 2.0 build is the approved-mode build narrowed to the CNSA 2.0 algorithms, with no passwords. Everything here is built and tested internally and not yet released. Full details: Approved-mode and CNSA 2.0 builds.
Certifications, honestly
QNSQY is not FIPS 140-3 validated, holds no CMVP certificate, and no lab has tested it. It is not SOC 2 audited, FedRAMP authorized or HIPAA audited, and we do not sign HIPAA Business Associate Agreements. The CNSA 2.0 build carries no NSA, NIAP or CSfC approval. QNSQY implements the algorithms NIST standardized (FIPS 203, 204 and 205, and SP 800-208) and publishes its test results on the validation page.
How buying works
Tell us your scope
The data, servers and people involved, and any rules you must meet.
We scope it with you
A short call to agree what is in and out.
You get a written quote
A fixed price and a contract. Nothing is billed before you sign.
Tell us what you need to protect
We reply with a scope and a written quote.