Press & Media Kit

Everything a journalist, analyst, podcast host or conference organizer needs to cover QNSQY (Quantum Sequrity): logos, boilerplate, founder bio, screenshots, and talking points on post-quantum cryptography.

Boilerplate (150 words)

QNSQY (Quantum Sequrity) is a post-quantum cryptography tool for protecting data that outlives today's cryptography. It implements the NIST post-quantum standards (FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA, and FIPS 206 FN-DSA draft) in a hybrid construction with classical X25519, Ed25519 and AES-256-GCM, so a break in either family still leaves one layer of protection standing. QNSQY ships as a single Rust binary (CLI, TUI, GUI and MCP server in one executable) that runs all cryptographic operations locally, with kernel-level network isolation on Linux via seccomp-bpf; data never leaves the machine. QNSQY is built for hospitals, defense integrators, and regulated enterprises that need to protect records, design files and long-lived secrets against harvest-now-decrypt-later attacks. The name is spelled with a Q (intentionally), as a nod to the quantum threat model it was built to resist.

Shorter versions

One-line: QNSQY is a NIST-aligned post-quantum cryptography tool for protecting data, with all cryptographic operations running locally.

50 words: QNSQY (Quantum Sequrity) encrypts data using NIST post-quantum standards (ML-KEM, ML-DSA, SLH-DSA, FN-DSA) hybridized with classical cryptography. Single Rust binary (CLI, TUI, GUI, MCP) runs all cryptographic operations locally, with kernel-level network isolation on Linux via seccomp-bpf; data never leaves the machine. Built for hospitals, defense integrators, and regulated enterprises worried about harvest-now-decrypt-later attacks.

Brand spelling

"Sequrity" with a Q is intentional. It is a deliberate nod to the quantum threat model the product defends against, not a misspelling of "security". Please preserve the spelling in coverage. The acronym QNSQY stands for QuaNtum SeQuritY.

Talking points

NIST finalized FIPS 203/204/205 in 2024; FIPS 206 is in draft. QNSQY ships all four.
"Harvest now, decrypt later" is the real near-term threat. Encrypted traffic captured today can be decrypted the moment a cryptographically-relevant quantum computer (CRQC) exists.
The NSA's CNSA 2.0 sets a staggered timeline for US National Security Systems: a January 2027 acquisition preference for post-quantum algorithms, exclusive use by 2030 for firmware/software and network equipment, and by 2033 for operating systems, web/cloud, and general-purpose systems. Regulated industries are expected to follow the same curve.
QNSQY never transmits file content or keys. The only network path is an encrypted billing envelope, blocked by seccomp-bpf to everywhere else.
The product is built in Rust with memory-safe patterns, zeroization on drop, constant-time comparisons, and a Landlock/seccomp sandbox on Linux.

Logos, screenshots, brand assets

Wordmark (SVG) Download favicon.svg

Open Graph image Download og-image.png

App icon (PNG 512) Download app-icon.png

Screenshots Available on request — email press@quantumsequrity.com

Please do not re-color the wordmark or compress below 128 px. Typography is Syne Bold (wordmark) and Outfit (body).

Facts & figures

Algorithms shipped: ML-KEM-512/768/1024, ML-DSA-44/65/87, SLH-DSA (6 parameter sets), FN-DSA-512/1024, LMS, HQC-128/192/256.
Classical pairings: X25519 (KEM), Ed25519 (DSA), AES-256-GCM, XChaCha20-Poly1305.
Platforms: Linux x86_64 (glibc 2.35+) and Windows 10/11 x86_64 as of v7.2.37. macOS and Linux aarch64 builds are not yet shipping.
Interfaces: CLI, TUI, GUI (Slint), MCP server (JSON-RPC 2.0 over stdio).
License model: Free (ML-KEM-512 + ML-DSA-44), Pro, Business, Enterprise.
Headquarters: see contact block below.

Press contact

For interviews, quotes, review copies, demo sessions, or custom screenshots, email press@quantumsequrity.com. Replies within 2 business days.

Security inquiries: security@quantumsequrity.com. Sales & partnerships: hello@quantumsequrity.com.

Follow

← Home · Blog · Security