Alternatives
Products that do what Trust badges for your Let's Encrypt certificate does
- 1GE
2016 · github.com
- 2EA
2013 · github.com
- 3LA
2017 · keychest.net
- 4AT
2015 · github.com
- 5KC
2016 · github.com
- 6AL
2019 · github.com
- 7AD
2017 · keychest.net
- 8AL
2016 · blog.jetstack.io
- 9CA
2019 · docs.certera.io
- 10

TLDR, Let's Seal gives the finger to Adobe and every doc signing tool (docusign, google, etc) who pay to play with the Adobe Approved Trust List and then charge you for something that should be free. Currently even the person checking if a document/contract is sealed or code is authentic has to also be inside the same Adobe walled garden too. Verification, the part that should be free is the part everyone charges for. Thats the shape Let's Encrypt fixed for TLS, and I wanted the same thing for documents and files. The core idea therefore needed to go a bit beyond e signatures and i…
Jul 2026 · github.com
- 11LA
2015 · github.com
- 12FM
2016 · github.com
- 13IM
2018 · github.com
- 14PA
2015 · pastebin.com
- 15AL
2015 · github.com
- 16MS
2013 · getssl.me
- 17CS
2014 · xordataexchange.github.io
- 18S2
2016 · outercorner.com
- 19SK
2016 · zemanta.github.io
- 20AR
From the cryptic terminal commands to the innumerable ways to shoot yourself in the foot, I always struggled to use TLS certificates. I love how much easier (and cheaper) Let's Encrypt made it to get certificates, but there are still plenty of things to struggle with. That's why we built Relay: a free, browser-based tool that streamlines the ACME workflow, especially for tricky setups like homelabs. Relay acts as a secure intermediary between your ACME client and public certificate authorities like Let's Encrypt. Some ways Relay provides a better experience: - really fast, streamlined…
2025 · anchor.dev
- 21FS
2015 · sslforfree.com
- 22CI
2018 · cryptsend.io
- 23TC
2014 · tinycert.org
- 24LS
2016 · clearalias.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →