nowfound

Alternatives

Products that do what EnvManager does

Stop sharing secrets in Slack

  1. 1
    EnvKey79

    Protect api keys and credentials. Keep config in sync.

    2017

  2. 2E2

    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

  3. 3

    Simple, secure, with an Env Vault for your .env files

    Feb 2026

  4. 4ES
  5. 5
    Shelve156

    Effortless & secure secrets management

    2025

  6. 6

    Zero-knowledge secret manager for small dev teams

    May 2026 · getvaultlite.com

  7. 7EH
  8. 8LH

    I got tired of: - .env files committed to Git (seen it happen 100+ times) - API keys shared in Slack - Wondering who has access to what secrets So I built Liberty - a CLI tool that replaces .env files with hardware-bound encryption. How it works: $ pip install liberty-secrets $ liberty add DATABASE_URL postgresql://... $ liberty add STRIPE_KEY sk-... $ liberty exec npm start Secrets are encrypted with a key derived from your machine's hardware (CPU ID + machine ID + disk serial). If someone steals your .liberty vault file, it's useless on their machine. Features: - Hardware-bound…

    Jan 2026

  9. 9IO

    Last month, we open-sourced Infisical (https://github.com/Infisical/infisical) - a simple, end-to-end encrypted tool to sync environment variables across your team and infrastructure. You can use it to store environment variables and inject them into your applications locally or into CI/CD and production infrastructure. It can be used with any language/framework and is platform independent with a super easy setup. We know secret managers exist but, in our experience, they’re too complicated, not comprehensive, not user-friendly, or a mix of all three — other…

    2022 · github.com

  10. 10KC

    Hi HN, I built KeyEnv because I was tired of the "can you Slack me the Stripe key?" workflow. The problem: My team's secrets lived in a mix of Slack DMs, shared Google Docs, and .env files that definitely weren't in .gitignore at some point. Enterprise tools like Vault required more DevOps time than we had. Doppler was close but felt heavier than we needed. What KeyEnv does: keyenv init # link project keyenv pull # sync secrets to local .env keyenv run -- npm start # inject secrets, run command That's basically it. Secrets are encrypted client-side (AES-256-GCM) before leaving your machine.…

    Jan 2026 · keyenv.dev

  11. 11KC
  12. 12
    Hush94

    Share secrets safely in Slack

    2020

  13. 13

    The easiest local-first secrets manager for your team

    2023

  14. 14

    Don't share your secrets on Slack. Use Vaultez!

    Jun 2026 · vaultez.app

  15. 15RO

    Finally open sourced an internal tool we've been using for managing secrets. It's similar to SOPS, but more opinionated, easier to configure/use correctly, and produces nicer git diffs. It also supports one-way encryption, so you don't have to know the private key to add secrets.

    2023 · github.com

  16. 16

    A simple, secure and free to use tool for sharing secrets

    2017

  17. 17

    Stop fighting .env files & config hell

    Feb 2026

  18. 18

    Your environment variables, finally in one safe place

    Jun 2026 · justenvs.app

  19. 19LS

    Hi! I got tired of setting up tools I can't explain to a team in a few words like sops or git-crypt, just to store few files with environment variables or secrets, so I built lockenv as a simple alternative. It's basically a password-protected vault file you commit to git. No gpg keys, no cloud, just lockenv init, set a password, and lock/unlock the secrets. This tool integrates with OS keyring, so you're not typing passwords constantly. Should work on Mac/Linux/Windows, but I tested it only on linux so far. I am not trying to replace any mature / robust solution, just…

    Dec 2025 · github.com

  20. 20

    No more "can you send me the .env"

    Jul 2026 · dotsync-site.vercel.app

  21. 21ES
  22. 22EM
  23. 23SB

    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

  24. 24KO

    Hi Hacker News! Shahar and Tal from Keep here. We're thrilled to announce that we're open-sourcing our alerting CLI tool, Keep (https://github.com/keephq/keep). Designed by developers for developers, Keep streamlines and simplifies alerting, making it a first-class citizen within the development process. Think of Keep as Prometheus Alertmanager but for all observability tools, with a simple and intuitive (GitHub actions-like) syntax. We believe that alerting has historically been neglected in existing monitoring platforms, leading to subpar alerting practices. With Keep,…

    2023 · github.com

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