Alternatives
Products that do what SecLink does
Share secrets once. The server never sees them.
- 1
- 2AR
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
- 3
- 4
- 5
- 6RS
Retriever (https://retriever.corgea.io/), an open-source research project to help users receive secrets and sensitive information without needing a server in the middle. It works by using Public-key cryptography to coordinate the message sharing between the two devices. Read more on why we built it here: https://retriever.corgea.io/why.html
2024 · retriever.corgea.io
- 7
- 8
- 9
- 10
Turn any password into a self-destructing link in seconds
Mar 2026 · pass2link.com
- 11CI
2018 · cryptsend.io
- 12IP
Hey HN! I made a service to share passwords easy and secure but never promoted it. It's called instapass.io I noticed that people besides my friends and clients actually started to use, so maybe it will be helpful for you too! You share one-time self-destruct message using one time links and I won't even be able to see what you wrote. How does it work? When you generate a message the client-side makes a random password and use that to encrypt the message. The password is appended as an anchor tag which all modern browsers never send to the server. This way, I don't even know what you shared.…
2019
- 13
- 14OS
2021 · github.com
- 15
- 16
- 17HS
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
- 18
- 19
- 20
- 21
- 22
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →