Signing

Core cryptographic signing capability.

FeatureStatusNotes
ML-DSA-65 signing (NIST Level 3, default)LiveFIPS 204, finalized August 2024. 1,952-byte public key, 3,309-byte signature.
ML-DSA-44 & ML-DSA-87LiveSelectable per keypair for a different security/size trade-off (Level 2 and Level 5 respectively).
Hybrid mode (ECDSA P-256 + ML-DSA)LiveDual signature over the same document hash, for backward compatibility with classical verifiers.
Single Sign (batch self-sign)LiveUpload and sign multiple PDFs in one pass with your own key.
Multi Signer (invite co-signers)LiveEmail invitations plus a shareable co-sign link; each signer uses their own key.
Visible proof stampLiveHuman-readable stamp on the signed PDF: signer, algorithm, hash, timestamp.
Incremental CMS signature embeddingLiveStandard Adobe-compatible PKCS#7 detached signature via pyHanko, added incrementally so prior signatures in a chain are preserved.A formal PAdES profile upgrade is planned alongside independent timestamp-authority support — see the Regulated / Archival tier below. Separately: mainstream PDF readers, including Adobe Acrobat, don't yet natively validate post-quantum signatures — verify with Qausal's tools or the open-source snippet instead; this is an industry-wide gap, not specific to Qausal.
Attestation Certificate fallbackLiveFor permission-locked PDFs that reject embedded signatures — the original stays unmodified; a companion certificate carries the cryptographic proof.
FN-DSA (Falcon) supportComing NextBlocked on NIST finalizing FIPS 206 (expected late 2026/early 2027) — the provider seam already supports adding it without a rewrite.
↑ Back to top
Multi-Party Workflow & Document Lifecycle

What happens after upload — the part most often assumed to be "coming soon" on a PQC-focused product, but is fully live here today.

FeatureStatusNotes
Multi-party signing with rolesLiveOwner, signer, verifier — enforced server-side, not just in the UI.
Decline to sign, with reasonLiveReason visible to the document owner.
Owner cancelLiveAvailable while a document isn't yet fully signed; all remaining signers are notified.
Visual document journeyLiveTimeline view: uploaded → signers assigned → signed/declined/pending → result.
Status auto-recomputeLiveAdding a signer to a fully-signed document reopens it to "In Progress" — enforced identically front and back end.
Participant managementLiveAdd/remove signers and verifiers after upload (owner only).
Single-Sign lockoutLiveDocuments signed via Single Sign can only gain verifiers afterward, never additional signers.
↑ Back to top
Verification & Proof

What you can check today, and what's being added for long-term, independently-witnessed validity.

FeatureStatusNotes
Offline / independent verificationLiveNo account, no API key, no internet connection required — ~5 lines of Python + liboqs.
Downloadable JSON proof bundleLiveAlgorithm OID, public key, signature bytes, document hash, verification code.
Public / private verification modesLivePublic: anyone with the link. Private: assigned signers and verifiers only.
Verify by hash, document ID, or uploadLiveIndexed hash lookup — no full-disk scan.
Full signing-chain re-verificationLiveEvery signer's signature is independently re-checked against its own stored digest, not just the first in the chain.
Cryptographically signature-bound timestampLiveThe claimed signing time is part of the CMS signed attributes the ML-DSA signature is computed over — tamper with it and the signature breaks. Reinforced by an immutable, DB-trigger-enforced audit trail.A real, tamper-evident timestamp — strong evidence for the large majority of disputes. It's asserted by the system that produced it; for protection against a future compromise of the signing algorithm itself, see the independently-witnessed timestamp below.
Independently witnessed timestamp (dual anchor: TSA + public blockchain)Coming NextPeriodic timestamps from an accredited external Time-Stamping Authority, plus an anchor on a public blockchain (Bitcoin via OpenTimestamps). Protects against a future compromise of a signer's key or ML-DSA itself, which today's signature-bound timestamp can't.
↑ Back to top
Access Control & Roles
FeatureStatusNotes
Document roles: owner / signer / verifierLiveAccess and action rights differ by role, enforced at the API level.
Org roles: owner / admin / memberLiveControls who can manage members, change roles, and invite others.
SSO (OIDC)BetaPer-org connections (Entra ID, Okta, Google Workspace, any standard OIDC IdP) with domain-based sign-in, just-in-time provisioning, and an org-level "require SSO" policy.Built; pending production rollout.
SAMLComing NextSAML-only identity providers aren't yet supported directly.If your IdP is SAML-only, let's talk about timeline.
↑ Back to top
Notifications
FeatureStatusNotes
Signer invited / signed / declined / cancelled emailsLiveBranded HTML templates, sent async via background task.
Password reset emailLiveTime-limited (15 min), purpose-scoped JWT token; no account-existence leakage.
Graceful degradation without SMTPLiveEmails silently no-op if SMTP isn't configured — never blocks the underlying action.
↑ Back to top
Organisations & Multi-Tenancy
FeatureStatusNotes
Multi-tenant orgs with join codesLive8-character join code for self-service member onboarding.
Org self-service admin panelBetaMember management, join code, subscription usage card.Built; pending production rollout.
↑ Back to top
Commercial & Subscriptions
FeatureStatusNotes
Multi plan tiersLiveFree trial · Starter · Professional · Enterprise · API/SDK
Self-serve billing / payment checkoutComing NextPlans are admin-provisioned today; no Stripe-style self-serve checkout yet.
↑ Back to top
Platform Administration & Crypto-Agility

The part of "quantum-safe" most competitors haven't built — see the differentiator spotlight on the main page.

FeatureStatusNotes
Full admin consoleLiveOrgs, users, subscriptions, plans, promos, keypairs, algorithms, audit — all in one panel.
Keypair lifecycle managementLiveRotate, revoke, expire, and reset — full rotation chain, old key never invalidates prior signatures.
Algorithm deprecation registryBetaMark an algorithm deprecated from the admin UI — blocks new signing/keygen instantly, no deploy. Verification of existing signatures is never affected.Built; pending production rollout.
Staged bulk algorithm migrationBetaImmediate or throttled (N users/hour), live progress, cancel, per-user failure log.Built; pending production rollout.
KEK rotation (rewrap-all)BetaRe-wrap every stored private key onto a new wrapping secret without touching the signing keys themselves.Built; pending production rollout.
Immutable audit trailLiveBlocks any UPDATE/DELETE on audit events, regardless of which DB role connects.
Quantum posture reportingBetaClassical vs hybrid vs PQC-only breakdown, per org.Built and tested end-to-end, pending production rollout; a customer-facing, per-document view is the Compliance Dashboard item below.
Per-document compliance dashboardComing NextMaps each signed document to the regulatory framework driving your requirement — EO 14412, CNSA 2.0, ASD 2030, or sector-specific rules.
↑ Back to top
Regulated / Archival Tier

The upgrade layer for decades-long retention and independently-witnessed validity — see Enterprise pricing.

FeatureStatusNotes
Archival Vault (quantum-safe encrypted storage)Coming NextBuilt on the same crypto-agility engine (deprecation registry + migration) that's already built and tested (Beta) today.
Dual-anchor timestamping (external TSA + public blockchain)Coming NextSee the Verification & Proof section above — this is the mechanism that delivers it.
Configurable retention policiesComing Next7 years for tax, 30+ for property, lifetime for medical — configurable per org.
Standards-compliant export (PDF/A, PAdES)Coming NextSo archives outlive any single vendor, including UbQbit.
HSM-backed key storageComing NextToday, private keys are AES-256-GCM encrypted at rest in the database, not hardware-isolated. Positioned as an enterprise add-on once available.
FIPS 140-3 module validationNot PlannedYet to be started / scheduled.A specialised, 6–12 month certification process once initiated.
↑ Back to top
Integrations
FeatureStatusNotes
REST APILiveAlready powers the full Qausal web app.
Public API / SDK productEarly AccessAvailable today by direct arrangement, ahead of a general developer release with published docs and self-serve keys.
White-label configurationComing NextFor B2B2C partners embedding Qausal's signing engine under their own brand.
Partner certification badgeComing Next"Quantum-Safe Ready" program for integration partners.
Native mobile appNot PlannedWeb is fully responsive; no evidence of demand distinct from that yet. Revisit if a specific deal requires it.
↑ Back to top
Don't see what you need, or need one of the Coming Next items sooner? Talk to us — several of these are prioritised against active pipeline, not a fixed date.

Ready to see it live?

Everything marked Live above is running in production today — including the full multi-party signing workflow and offline-verifiable proof bundles. Crypto-agility tooling (algorithm deprecation, migration, KEK rotation) is built and tested, marked Beta pending production rollout.