July 27, 2026
Signed, sealed, debated
Show HN: Let's Seal – Let's Encrypt for document signing, free and self-hosted
Free document signing drops, and the comments immediately ask: can anyone trust this
TLDR: Let's Seal launched as a free, self-hosted way to prove a document is real and unchanged, aiming to do for document signing what Let’s Encrypt did for website security. Commenters liked the idea but immediately argued over trust, legal usefulness, and whether this is a real standard or just a very confident new label.
A new project called Let's Seal is pitching itself as the free, open-source answer to paid document proof services — basically, a way to show a file is real, hasn’t been changed, and existed by a certain date. The big promise is simple enough for non-lawyers and non-cryptography nerds: seal a PDF, image, email, or other file, and anyone should be able to check it later for free. The vibe from the launch? Curious excitement with a heavy side of side-eye.
Some commenters were genuinely into it, with one early explorer saying they were “excited to see where this goes” — before instantly finding a broken discussions link. That tiny 404 became the perfect Hacker News mood setter: cool idea, but the internet never misses a loose screw. Then came the sharper reactions. One commenter threw the biggest grenade by calling it an “invented standard,” which is basically catnip for tech people who distrust anything that sounds too new, too neat, or too self-defined. Another zoomed in on the real make-or-break issue: trust. If this service says a document is authentic, why should a company, judge, or anyone else believe the people behind it?
And then there’s the legal reality check, which may be the thread’s most deliciously deflating twist: one commenter noted that courts still often accept paper-signed, scanned PDFs anyway, making all this extra proof feel a bit like bringing a spaceship to a bicycle race. So while Let's Seal wants to be “Let’s Encrypt for document signing,” the crowd is split between “finally, useful public infrastructure” and “nice pitch, but will this matter in the real world?”
Key Points
- •Let's Seal introduces SEAL as an open standard for proving that a file is unaltered, tied to a certificate, and existed by a certain date.
- •The project offers free sealing through a hosted web app, a command-line tool and API, and a self-hosted deployment option under a user's own certificate authority.
- •Verification is described as free, accountless, and possible through a public portal or offline on a local machine.
- •SEAL proofs combine file integrity checks, Bitcoin-anchored timestamps via OpenTimestamps, and an append-only transparency log based on RFC 6962.
- •The system supports multiple native formats including PDFs, media, XML, email, arbitrary files, and software artifacts using standards such as PAdES, C2PA, XML-DSig, S/MIME, CAdES/CMS, and in-toto/DSSE.