nowfound

Alternatives

Products that do what CYPHR does

Secure API Key storage for developers

  1. 1ES
  2. 2
    EnvKey79

    Protect api keys and credentials. Keep config in sync.

    2017

  3. 3

    Give AI access to 6754+ APIs with zero credentials exposed

    Feb 2026

  4. 4

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

    Feb 2026

  5. 5KA
  6. 6

    Store and share your files securely

    2020

  7. 7

    Securely store your secrets in GitHub Private Repo

    Feb 2026

  8. 8SI
  9. 9KF
  10. 10SH
  11. 11

    Never worry about crypto seed phrases again

    2022

  12. 12CU
  13. 13

    Private & Encrypted Files, Notes, Passwords, 2FAs app

    2020

  14. 14
    Secli85

    A CLI to store secrets locally

    2022

  15. 15CM
  16. 16KC

    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

  17. 17GM
  18. 18IJ

    .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

  19. 19LO

    Key management for multiple users and multiple cloud LLM/GenAI APIs is difficult to be both safe and convenient. Sharing keys among users risks leaking the key and makes it difficult to curb the leakage without interruptions. But assigning one key per user per cloud API results in too many keys to keep track of. Meet LlaMa(ster)Key, the secure and easy solution for API key management: * For each user, one master key for multiple APIs. * The master key is unique to each user. Granting and revoking a user's access won't impact other users. * The actual API keys to authenticate with cloud…

    2024 · github.com

  20. 20UF
  21. 21KS
  22. 22GA
  23. 23AC
  24. 24NQ

    Hey HN, We're building ncrypt, an open-source encrypted file manager that allows you to store, manage, and privately query your files using fully homomorphic encryption (FHE). This project originally started as a simple SFTP-like CLI for my personal S3 buckets which I used to send and retrieve encrypted files and have more granular control over key rotation. As the number of files that I was storing grew, file discovery started to become a problem, and I found myself frequently having to download and decrypt files to inspect their contents. Rather than leaving them unencrypted in S3 and…

    2025 · github.com

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