You have 50,000 contracts in iManage or NetDocuments. You’re not moving them. You’re not changing your workflow. A plugin intercepts every save, signs it with post-quantum cryptography, and stores the proof as metadata. The attorney never sees any of it.
Pick the model that matches your firm. Every path produces the same post-quantum signature, the same timestamp, the same 30-year verifiability.
Law firm has iManage, NetDocuments, or SharePoint with tens of thousands of documents. Attorneys won’t change how they work. They will not learn new software. They will not click extra buttons. Any friction means zero adoption.
Plugin intercepts the save event. Document goes to the H33 API. A post-quantum signature, RFC 3161 timestamp, and certificate chain come back. Stored as metadata on the DMS record. The attorney saves the document exactly as before. The signature just happens.
Attorneys do not change a single behavior. IT installs the plugin once. Every document saved from that point forward is post-quantum signed automatically. Adoption rate: 100%, because there is nothing to adopt.
Firm doesn’t have a DMS. Documents are in Dropbox, email, shared drives. No centralized system to hook into. Still need every contract signed with post-quantum cryptography before quantum computing breaks classical signatures.
Web portal at app.h33.ai — drag documents in, get signed versions back. Or forward to sign@h33.ai and receive the signed version by email. Bulk upload a folder, get back the same folder with every document signed.
No DMS required. No IT department required. A solo practitioner can sign every document in their practice in an afternoon. Email-based signing means the barrier to entry is knowing how to forward an email.
Firm has custom practice management software or builds their own tooling. They need programmatic access to post-quantum signing that drops into whatever system they already run.
One curl command. Send the document, get back the PQ-signed version with embedded RFC 3161 timestamp and certificate chain. Drop it back in whatever system they use. JSON response includes the signature, certificate, and verification URL.
# Sign a document with ArchiveSign curl -X POST https://api.h33.ai/v1/archivesign \ -H "Authorization: Bearer $H33_API_KEY" \ -F "document=@contract.pdf" \ -o signed-contract.pdf # Response includes: # - PQ-signed document (SLH-DSA + Dilithium) # - RFC 3161 timestamp token # - Certificate chain # - Verification URL
One endpoint. One API key. Any language, any platform. The response is a signed PDF with embedded proof — no proprietary format, no vendor lock-in. Verify with the open-source verifier or any standards-compliant tool.
New documents are covered by the plugin. But the contracts already in your DMS need protection too. Three strategies, used together or independently.
Feed every existing document through ArchiveSign overnight. The original classical signature is preserved. A new post-quantum signature is added alongside it. The RFC 3161 timestamp proves the PQ signature existed before quantum computing broke the classical one. 50,000 documents. One night. No attorney involvement.
For contracts approaching renewal, generate an amendment: “The parties agree to re-execute using post-quantum cryptographic signatures.” Both parties sign. Clean legal basis. The amendment itself is PQ-signed, creating an unbroken chain of quantum-safe custody from the amendment date forward.
Firm policy: all new signatures use ArchiveSign. All existing documents bulk re-signed on schedule. No individual attorney action required. The combination of bulk re-signing and standing policy means the entire document corpus converges to full PQ coverage without any per-document decision-making.
Every capability maps to a specific H33 component. No black boxes. Every piece is independently verifiable.
| Capability | H33 Component |
|---|---|
| Zero workflow disruption | DMS plugin auto-signs |
| 50-year signature validity | SLH-DSA + RFC 3161 TSA |
| Clause-level amendments | Document Lifecycle Engine |
| Auto-renewal signing | Signing Scheduler |
| Version chain (tamper-proof) | SHA3-256 chain hashing |
| Multi-party authorization | Threshold approval (2-of-3 partners) |
| Redline any two versions | LCS diff engine |
| Independent verification | Open-source verifier |
Your attorneys save documents exactly the way they do today. Every document gets a post-quantum signature that will hold up for decades. The migration happens while everyone is asleep.