Alternatives
Products that do what Secret does
Encrypted text and file sharing, self-host ready
- 1PS
2022 · mprimi.github.io
- 2

- 3

- 4

- 5

- 6EA
2022 · github.com
- 7

- 8

- 9

- 10

- 11

- 12

- 13

- 14

- 15

- 16

- 17

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
- 18

- 19OS
2021 · github.com
- 20EA
Hi HN, I'm building ThirdCloud with the goal to replace Google Drive for everyone: more private, cheaper & maybe better UI/UX. So far, I've successfully implemented the main feature, which involves uploading and downloading files. Files are encrypted before being sent to IPFS network. Would like to hear your thoughts on this proof of concept.
2023 · thirdcloud.org
- 21SI
2021 · pastenow.me
- 22CI
2018 · cryptsend.io
- 23HS
Hi HN! I built hidetext.sh — a way to share text, code, and files through links the server can't read. How it works: your browser generates a random key and encrypts everything locally (NaCl secretbox, XSalsa20-Poly1305). Only ciphertext is uploaded. The key goes into the URL fragment — the part after # — which browsers never send to servers. The link carries the key, my server stores the locked box, and the two only meet in a browser. A design detail I'm fairly happy with: burn-after-read doesn't destroy the paste on the first HTTP request. The naive version means a Slack or iMessage link…
Jul 2026 · hidetext.sh
- 24

Ranked by how close each launch is in meaning, then by votes. Refine with a description →