Documents that hold their shape forever.
A sealed engineering document carries legal weight. We treat it that way at every layer — from the bytes to the storage to the revision history. Three commitments that turn a PDF into evidence.
SHA-256 hash
per byte sequence
X.509 PKI
RSA-PSS signing
RFC 3161
trusted timestamps
PDF/A-2b
ISO 19005 archival
The three commitments
Three rules that turn a PDF into evidence
Each links to the deep technical breakdown — implementation, control mappings, and the architectural choices we made and rejected.
Sealing
The seal is a property of the bytes
SHA-256 content hash, X.509 PKI digital signature, RFC 3161 trusted timestamp, PDF/A-2b archival. Tampering is mathematically detectable; the seal is verifiable offline by any X.509-aware tool.
Versioning
Every revision is preserved, every seal is immutable
Working drafts stay editable. Sealed versions are locked, hashed, and indexed by sequence. The version that was sealed is the version that exists — forever and unambiguously.
Storage
Sync to the storage you already trust
11+ provider integrations: S3, Azure Blob, Google Drive, SharePoint, Box, Dropbox, Procore, Autodesk ACC, SFTP, WebDAV, Egnyte. Sealed documents land in your existing workflow automatically.
Documents you can stake your license on
Every property a sealed document needs to be evidence is a published-standard cryptographic primitive.