Open source, open standards, open ledger.
Nothing here is ours to lock up. Let's Seal keeps working even if we don't, because the proof lives in public standards and a public ledger.
Open source
Every part, CLI, SDKs, web app, signing service, is Apache-2.0 licensed on GitHub. Read it, fork it, run it.
Open standards
PAdES signatures, X.509 certificates, SHA-256, OpenTimestamps, established, audited, and yours to verify against.
Open ledger
Anchors live on the public blockchain, and every seal is recorded in a public, append-only transparency log. Verification stands on its own, anywhere, forever.
Run it yourself, keep your keys
Self-host the whole stack and hold your own keys. Your seals stay verifiable forever, by anyone.
Run the whole thing yourself
Clone, configure, deploy. You get your own signing keys and full control. Issue seals no one can revoke or paywall.
git clone https://github.com/letsseal/letsseal cd letsseal cp .env.example .env # add your CA + config ./deploy.sh # up on your own domain
By the numbers, live
Live counts from the network’s own public proof records, the same ones anyone can pull from a /d/<hash> proof page. No telemetry, no phone-home. Every number is real, and it climbs as the network grows.
- Every public proof record: sealed files and standalone timestamps
- The latest block anchor on the public ledger
- No document contents or filenames, only the count
- No names, emails, accounts, or IP addresses
- Not aggregated from anyone else’s server
These counts come from this network’s own public proof records. Nothing is collected from you to produce them. A self-hosted instance counts its own records locally and reports nothing back to us; there is no telemetry to disable because there is none to begin with.