Dev tools · alternatives · 2026
24 alternatives to EnvDrop
Stop sharing secrets in plaintext
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1E2
Hey HN, I'm so happy to finally show you all this release after years of hard work. I posted the first version of EnvKey to HN back in 2017 (https://news.ycombinator.com/item?id=15330757), then went through YC in W18 (https://news.ycombinator.com/item?id=16569534). EnvKey is an end-to-end encrypted configuration and secrets manager. It protects your organization's API keys, encryption keys, credentials, and other secrets, and makes it easy to run servers, scripts, tests, and everything else with the latest config. It also helps you avoid duplication in your…
2022 · v2.envkey.com · its alternatives →
- 2
enject: Hide .env secrets from prAIng eyes: secrets live in local encrypted stores (per project) and are injected directly into apps at runtime, never touching disk as plaintext. - GreatScott/enject
Feb 2026 · github.com · its alternatives →
- 3
- 4
- 5
- 6
Hey everyone, English is not my native language. This post was polished with AI, but the content is mine. I run a small dev agency in Germany. Every week someone shares database credentials, API keys, or a .env file via Slack or email. Not because they don’t care: because there’s no frictionless alternative. Vault setups are heavy. Enterprise tools are expensive. I just needed: upload → share link → done. But encrypted before leaving the browser. So I built SecretDrop.dev. What it does Files encrypted client-side (AES-256-GCM, PBKDF2 600k iterations) Built entirely on WebCrypto No…
Feb 2026 · secretdrop.dev · its alternatives →
- 7
Share files from your terminal with end-to-end encryption
2024 · rstream.io · its alternatives →
- 8
- 9
- 10
🔐 Share end-to-end encrypted secrets with others via a one-time URL - sniptt-official/ots
2021 · github.com · its alternatives →
- 11
- 12
Secure zero-knowledge link sharing for developer credentials
Jun 2026 · secrettly.space · its alternatives →
- 13
2016 · zemanta.github.io · its alternatives →
- 14
- 15
Self-destructing encrypted messages, files & screenshots
Jul 2026 · secretnote.eu · its alternatives →
- 16
- 17
Secret▲4Encrypted text and file sharing, self-host ready
Jun 2026 · secret.witt.im · its alternatives →
- 18
EnvDrop▲5Share env's securely with autodestruction feature
Feb 2026 · envdrop.vercel.app · its alternatives →
- 19
Share-Env ▲3Share .env files without sharing them in Slack
Jul 2026 · share-env.site · its alternatives →
- 20
AxKeyStore▲31Hi HN, I built AxKeyStore, an open-source CLI tool for managing secrets that uses your own private GitHub repository as encrypted storage. The idea is simple: → All encryption happens locally. → Secrets are stored as encrypted blobs in your private repo. → GitHub is treated as untrusted storage. → No plaintext secrets ever leave your machine. → No plaintext secrets are stored on disk. Most secret managers either require a hosted backend, a self-hosted server, or trusting a SaaS provider. I wanted something that: → Requires zero infrastructure → Uses tooling developers already have → Keeps…
Feb 2026 · github.com · its alternatives →
- 21
2016 · github.com · its alternatives →
- 22
- 23
- 24HS
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 · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →