Quantum-Proof Signatures
for Modern Applications.
Drop-in developer SDKs and lightweight software gateways to protect transactions, APIs, and data integrity against signatures forged with quantum computers. Integrate in a few lines of code, with no cryptography expertise required.
npm install qids-sdk
How It Works in 3 Simple Steps
Add quantum digital signatures to your applications in minutes with simple, developer-friendly primitives.
Install the Client SDK
Signing clients for npm, PyPI, Go and Java (JitPack). The Rust, C and Julia packages provide the primitives: constant-time comparison, Toeplitz hashing and Wald SPRT.
Sign Any Payload
Send any payload, byte for byte. The gateway draws a fresh one-time key, from your QKD system or the OS random generator, signs, and keeps a receipt. The response says which key source was used.
Verify Through the Gateway
Designated recipients verify through the gateway, which reconstructs the one-time key, recomputes the hash and flags forgery, replay and impersonation.
Quantum Security Without the Complexity
Built for engineers who need quantum-resistant integrity without managing physical quantum hardware or complex cryptography.
Idiomatic SDKs in Your Favorite Language
First-class libraries for TypeScript, Python, Go, and Rust. Simple async methods with automatic session key rotation, connection pooling, and built-in tamper verification.
Try the Signing Math in Your Browser
Real arithmetic, running on this page: a polynomial universal hash over GF(264) under a fresh one-time key, one-time-padded. That is the construction the gateway uses at 128 bits, where it also secret-shares the key across the verifiers. Sign a payload, then flip one bit of it and watch verification recompute and reject. Nothing is sent anywhere.
Enterprise Security Guarantees
Built for zero-trust production environments with zero operational friction.
One-Time Keys, Hashed API Keys
Every signature uses a fresh key that is never reused. Its shares are stored so the signature can be verified later, so the gateway's database must be protected like a key vault. API keys are stored only as hashes.
Tamper-Evident Receipts
Every signature gets a tenant-scoped audit receipt with a Merkle root. Verification recomputes the hash from the exact bytes, and each verdict is logged with its evidence.
Self-Hosted or Air-Gapped
Deploy the containerized gateway in your VPC, a Kubernetes cluster or on-premises, with an egress guard for air-gapped networks. A hosted gateway is coming soon.
What QIDS Is Built For
Protecting high-stakes transactions and critical data pipelines across industries.
High-Value Interbank Wires
Sign SWIFT payments, Fedwire settlements, and treasury transfers with signatures that stay unforgeable when quantum computers break RSA and ECDSA.
Microservice Token Integrity
Sign high-privilege service-to-service tokens and API dispatches, with a forgery bound that does not depend on computational hardness.
Immutable Audit Logs
Give healthcare records, regulatory filings, and contracts receipts whose security does not erode as computers get faster.
Simple, Transparent Developer Pricing
Start free for testing and proofs of concept. Scale seamlessly as your transaction volume grows.
Frequently Asked Questions
Everything you need to know about integrating QIDS into your software stack.
What makes quantum digital signatures different from standard signatures?
Standard digital signatures (like RSA and ECDSA) rely on computational hardness assumptions that will be broken by quantum computers running Shor's algorithm. QIDS signs with one-time universal hashing, whose forgery bound (about 10-37 per signature, returned with every signature) does not depend on computational hardness, so Shor's algorithm does not apply. The bound assumes a uniformly random one-time key: with keys from a QKD system it holds end to end; with the default OS random generator, it is as strong as that generator.
Do I need special hardware to use QIDS?
No. Install a client (Python, TypeScript, Go or Java) and point it at a QIDS gateway you run with Docker or Kubernetes; a hosted gateway is coming soon. QKD hardware is optional: without it, keys come from the OS random generator, and every signature says which source it used.
Can we self-host QIDS in our own private cloud or VPC?
Yes. The QIDS Enterprise tier includes containerized gateway images ready to deploy via Docker or Helm onto Kubernetes in your own cloud account or on-premises, with no external services required. The Helm chart runs one replica with a persistent volume; multi-node high availability is on the roadmap.
How fast is signature generation and verification?
Measured on a developer laptop at full durability: the signing engine sustains about 1,950 signatures per second, and the HTTP API about 570 requests per second with four gateway processes (about 900 with relaxed fsync). Verification runs at about 236 per second per process. That suits interbank settlement, document signing and API authentication. It is not built for high-frequency trading.
What happens if we exceed 250,000 signatures on the Pro plan?
On Commercial Pro, extra signatures are billed at just ₹0.08 per signature. Your API keeps serving past the quota. If you would rather have a hard stop, we can switch overage off for your tenant, and requests past the quota then get HTTP 402.
Why do enterprises choose the Self-Hosted tier?
The Enterprise tier is designed for banks and regulated organizations that must keep 100% of their data inside their own private VPC or air-gapped network. You provide your own compute, and QIDS provides unlimited signatures, OIDC SSO with role-based access, and syslog to your SIEM. A dedicated TAM with 24/7 support is coming soon.