Alternatives
Products that do what SealedPacket does
Encrypt files locally. Share secure packets anywhere.
- 1EA
2022 · github.com
- 2PS
2022 · mprimi.github.io
- 3
- 4
- 5
- 6
Send any file, any size, straight from browser to browser
Jun 2026 · jfsendit.com
- 7
- 8
- 9
- 10
- 11HS
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
- 12
- 13
- 14SB
Stasher is a tiny CLI tool that lets you share encrypted secrets that burn after reading — no accounts, no logins, no servers to trust. I built it because I just wanted to share a password. Not spin up infra. Not register for some "secure" web app. Not trust Slack threads. Just send a secret. Secrets are encrypted client-side with AES-256-GCM. You get a `uuid:key` token to share. Once someone reads it, it's gone. If they don't read it in 10 minutes, it expires and deleted. Everything is verifiable. Every release is signed, SLSA-attested, SBOM-included, and logged in the Rekor transparency…
2025 · github.com
- 15
- 16
- 17AL
2015 · github.com
- 18CI
2018 · cryptsend.io
- 19LS
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
- 20
- 21PE
Hi HN! I wrote a tool that partially encrypts files based on the presence of a HEREDOC. Check it out: https://github.com/higgins/privatize When added to a git repo, it will automatically transparently encrypt/decrypt files you want privatized. For example if you configured your repo to privatize the file `example.txt`, you could write: ``` Today I a burrito. <<PRIVATE I was on the toilet for hours. PRIVATE I got a lot of reading done. ``` but when git-commit'ed would become: ``` Today I a burrito. <<PRIVATE xuJ0fld2vmNWaVLogTIufmWsiFso PRIVATE I got a lot of reading…
2022
- 22
- 23EE
2013 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →