UbQbit
Qausal
Upload a document, invite your signers, done — quantum-safe by default, whether it's just you or a deal team of ten.
Every signature uses ML-DSA-65, the NIST-standardised post-quantum algorithm (FIPS 204) — built so what you sign today is still valid evidence decades from now. No cryptography knowledge required on either end.
Sign on UbQbit Qausal. Store anywhere. Verify everywhere.
Qausal — a portmanteau of “quantum” and “causal.” Causality is the chain of events that proves something happened — which is exactly what a signature does.
Multi-Signer Journey
partnership_agreement.pdf
Start Free — 20 Days, No Card Required
Get the full quantum-safe signing experience — solo and multi-party — for 20 days. No credit card, no commitment. Upgrade at any time, or continue on the Starter pay-as-you-go rate when the trial ends.
Whoever is signing, and however many of you there are
The quantum-safe question isn't "am I a government contractor" — it's "does this document need to be trusted for longer than I can predict." That's a much wider group than the compliance conversation usually suggests.
Solo practitioners, small firms & individuals
Conveyancers, family lawyers, accountants, freelancers — anyone signing documents their clients will rely on for years. Pay-as-you-go at $0.50 a signature, no subscription, no procurement process.
Growing teams & firms doing multi-party deals
Upload once, invite every signer by email, and watch the deal move — role-based owner/signer/verifier access, a visual journey showing who's signed and who's pending, decline-with-reason built in. The workflow you already know, running on cryptography that doesn't expire.
Anyone whose signatures must outlive the decade
Property deeds, wills, medical records, long-term financial instruments — a document that must remain verifiable in 2040 cannot rely on a signature scheme expected to fail before then.
Government suppliers in Australia & Canada
Australia's ASD has set 2030 for retiring quantum-vulnerable cryptography; Canada already writes post-quantum clauses into federal contracts.
US federal & defence-adjacent suppliers
EO 14412 makes quantum-safe signing a procurement requirement. Contractors touching high-impact systems will be asked for their PQC story in security reviews well before 2031.
As simple as any e-signature tool. Just quantum-safe underneath.
You don't need a cryptographer, a procurement team, or an IT department. If you can attach a PDF to an email, you can sign quantum-safe — solo, or with a room full of signatories.
Upload
Drop in any PDF — a contract, a deed, an agreement. Qausal generates your quantum-safe keypair automatically; the cryptography stays invisible.
Invite your signers
Single-signer, or multi-party with roles. The right people — and only the right people — can act on the document.
Everyone signs, in order
Each signer adds their own ML-DSA-65 signature over the exact document state they saw. A visual journey shows who's signed, who's pending, and who declined — and why.
Verify — anywhere, forever
Download the signed PDF and its proof bundle. Every signature in the chain is independently verifiable — on Qausal, with open-source tools, or decades from now.
No platform lock-in at any step. Solo practitioners can start with per signature with no subscription as well — the same NIST-standardised cryptography that federal mandates require
↑ Back to page menuThis isn't a 2030 problem. It's a today problem. Adversaries don't need a working quantum computer to start — they can collect signed documents right now and forge or repudiate them the moment classical cryptography falls. That's the "harvest now, forge later" threat, and it's already underway.
A signature can't be upgraded after it's created. It's as strong as the day it was made, forever. Every document you sign today with RSA or ECDSA is exposed the day quantum cryptanalysis catches up — whenever that turns out to be.
If you need one more reason, the deadlines are real too — signed, dated government mandates, verifiable by your own compliance team:
Harvest-now-forge-later
Signed documents are being collected today for future forgery — no deadline required for this to already be true.
Canada
Post-quantum procurement clauses required on federal contracts signed after this date.
US EO 14412
Signed executive order mandating quantum-safe signatures on federal high-impact systems.
Australia's ASD & US contractors
ASD's deadline for retiring quantum-vulnerable cryptography; same year US federal contractors must comply with post-quantum FIPS.
US signature deadline
EO 14412's hard deadline for quantum-safe signing on federal high-impact systems and high-value assets.
Built for the day the algorithm changes
Every PQC vendor can tell you they support ML-DSA today. Almost none of them can tell you what happens the day it's deprecated, weakened, or superseded. UbQbit can.
Flip a flag. Not your platform.
Our algorithm registry lets an administrator mark an algorithm deprecated from a dashboard — no deploy, no downtime — which immediately blocks new signing with it while every signature ever produced with it stays fully verifiable, forever.
A staged migration engine then moves every affected keypair onto the new algorithm in the background, on a schedule you control, with live progress and a full audit trail.
This is the part of "quantum-safe" that you may not see elsewhere yet — and it's already built and working in Qausal, not just on a roadmap.
Deprecation blocks new signing instantly. Existing signatures remain verifiable forever. Migration runs in the background with live progress and a full audit trail.
Your signatures are a promise. Make sure they last.
Every contract, deed, and record you sign carries a commitment that must remain verifiable for years or decades. Qausal ensures that commitment holds — no matter what.
Sign once, trust forever
Classical digital signatures (RSA, ECDSA) will be breakable by quantum computers. Qausal signs with ML-DSA-65, the NIST-standardised algorithm designed to resist quantum attacks, so your signatures remain legally sound for their entire retention lifecycle.
Backward compatible, forward secure
Hybrid mode applies both a classical ECDSA signature and a quantum-safe ML-DSA signature to every document — so current verification tools still work, while quantum-safe protection is already in place.
A record that can't be quietly edited
Every signing event is logged in a tamper-evident, immutable audit trail — enforced at the database level, not just app convention, so even a compromised admin account can't alter history.
The document IS the evidence
Sign on UbQbit Qausal. Store anywhere. Verify everywhere.
Most e-signature platforms create a dependency: the signature is only valid because the vendor says it is. UbQbit takes the opposite approach — every signed document is a self-contained cryptographic proof.
📄 What the signed PDF carries
When a document is signed on Qausal, the PDF itself is modified to embed everything needed for independent verification — forever.
- Standards-based, incrementally-embedded digital signature, cryptographically bound to a signing-time claim
- Visible proof stamp showing signer, algorithm, hash, and timestamp
- Downloadable proof bundle (JSON) with full cryptographic evidence
- In multi-party chains: every signer's proof re-checked independently, not just the first
The signed PDF does not reference UbQbit's servers. It does not phone home. It does not expire.
🔓 Verify without UbQbit
A signed PDF + proof bundle can be verified using only open-source tools. No vendor account, no API key, no subscription, no internet connection required.
| Traditional e-Sign (DocuSign, Adobe Sign) | UbQbit Qausal | |
|---|---|---|
| Signature algorithm | RSA / ECDSA (quantum-vulnerable) | ML-DSA-65 (NIST FIPS 204, quantum-safe) |
| Multi-party signing | Standard | Standard, plus per-signer independent re-verification |
| Independent verification | Vendor lock-in — must use their platform | Open verification with downloadable proof bundles |
| Vendor goes offline | Signatures become unverifiable | Document carries its own proof — still valid |
| When the signing algorithm is deprecated | Re-platform or wait on the vendor | Flip a registry flag — new signing blocked instantly, past signatures stay valid |
This is a highlight reel. For the full row-by-row feature list — including exactly what's live vs. coming next — talk to us
↑ Back to page menuTwo live layers. One named roadmap.
What's built today, and where we're going — clearly labeled, item by item, so you can plan your evaluation against what's real.
Zero-downtime algorithm retirement — flip a flag, not a platform.
Three ML-DSA strengths Live
ML-DSA-44 / 65 / 87 — all FIPS 204 compliant, selectable per keypair.
Deprecation registry + migration Beta
Retire an algorithm with a dashboard flag; migrate every affected key in a controlled background job.
KEK rotation Beta
Re-encrypt every key at rest on demand — no downtime, full audit trail.
Public API & SDK Early Access
The REST API already powers Qausal's own frontend; early-access integration partnerships open now.
Every signer's proof re-checked independently — not just the first signature in the chain.
Multi-party signing with roles Live
Owner, signer, verifier — decline with a reason, cancel with a comment, both fully audited.
Visual document journey Live
See who's signed, who's pending, and who declined — with their stated reason.
Immutable audit trail Live
Tamper-evident and enforced at the database level — even a compromised admin can't alter history.
Compliance dashboard Coming Next
Map each signed document to the framework driving your requirement — EO 14412, CNSA 2.0, ASD 2030.
Independently witnessed timestamps — not just tamper-evident ones.
Dual-anchor timestamping Coming Next
An accredited external Time-Stamping Authority plus a public blockchain anchor — not a self-issued re-sign.
Built on today's crypto-agility engine Beta foundation
Runs on the same deprecation registry and migration infrastructure that's already built and tested — not a from-scratch promise.
Retention policies Coming Next
Configurable to your obligations: 7 years for tax, 30+ for property, lifetime for medical.
Standards-compliant export Coming Next
PDF/A and PAdES output, so archives outlive any one vendor — including us.
If long-term archival is a requirement for your evaluation timeline, talk to us — we prioritise this roadmap against active enterprise pipeline.
Start protecting documents today
From solo practitioners to enterprise — quantum-safe signing at every scale.
Starter
For anyone getting started with quantum-safe signing.
- ML-DSA-65 signatures
- Hybrid mode available
- PDF signing & verification
- Guest & Multi-party signing
- Audit trail
- Public verification URL
Solo / Professional
For solo practitioners, small to large firms and corporate legal teams needing quantum-safe signing.
- Everything in Starter
- Flexible plan options
- Options with generous quotas /month to Unlimited signatures
- Org dashboard & management
Enterprise
For large firms and institutions needing dedicated infrastructure, and compliance.
- Everything in Professional
- Dedicated org structure with custom quotas
- Full keypair lifecycle & staged migration, KEK rotation & advance capabilities
- Priority support
API / SDK
Embed quantum-safe signing into your platform. Our REST API already powers the full Qausal web app today.
- RESTful API access (early access)
- Dedicated integration support
- Custom SLA
Ready to sign quantum-safe —
solo or with your whole team?
See it in action: upload a document, invite a co-signer, and watch the crypto-agility tooling that answers the question every security review eventually asks — what happens when the algorithm changes?