nowfound

Alternatives

Products that do what Shelve does

Effortless & secure secrets management

  1. 1
    Shelve100

    "The simple way to share environment variables"

    2024

  2. 2
    Deposure185

    Launch your APIs live effortlessly

    2025

  3. 3CP
  4. 4QC
  5. 5
    EnvKey79

    Protect api keys and credentials. Keep config in sync.

    2017

  6. 6
    Phase159

    Open-source secrets management for developers

    2023

  7. 7AC
  8. 8

    Develop faster, eliminate complexity, protect your secrets

    2022

  9. 9AP
  10. 10S2
  11. 11TC
  12. 12
    Secrets 3100

    Simple and secure password manager for Mac and iOS

    2019

  13. 13EY
  14. 14
    Secli85

    A CLI to store secrets locally

    2022

  15. 15AL
  16. 16CA
  17. 17

    Manage secrets in your terminal with biometric unlock.

    2022

  18. 18SA

    2015 · github.com

  19. 19CA
  20. 20LH

    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

  21. 21CU
  22. 22IJ

    .env files have always felt archaic, insecure, clunky and honestly just not fun to work with. I see my friends (and myself) accidentally committing them all the time. Managing secrets across projects becomes a mess of copy-pasting keys into scattered env files with no real way to sync anything. So I built better-env: a secure, developer-friendly alternative to .env. Store your secrets once in a global encrypted store, and load them per-project at runtime. I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for teams or CI setups. Fully open source:…

    Nov 2025 · better-env.dev

  23. 23SR

    Hi Guys, I built SecretEnv to help solve one common thing that I have seen at every org, that I have worked at. We always had more than one password/credential manager. Service tokens maybe in Vault, AWS SSM etc and some team specific service account or temp account credentials being store in another password store such as 1Password or Keeper, there was never one single credential store. This is where SecretEnv comes in play, it runs any command with secrets injected as env vars, sourced from whatever combination of backend your team already uses. I am sure there are other tools as well…

    May 2026 · github.com

  24. 24SH

    I have written a passwords/secrets manager for my personal needs. Maybe it solves some of your problems too. It is written in Go and is a self-contained executable for a small web-app: https://github.com/jarmo/secrets-web There is also a CLI version if that is your taste: https://github.com/jarmo/secrets-cli To read about more technical details, look into the core repository at https://github.com/jarmo/secrets Any questions/comments/suggestions are welcome in here or via GitHub pull requests.

    2020

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