nowfound

Alternatives

Products that do what Keynv does

Secure secret management built for AI agents & developers

  1. 1

    Give AI access to 6754+ APIs with zero credentials exposed

    Feb 2026 · keychains.dev

  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. 3EH
  4. 4LS

    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

  5. 5ES
  6. 6
    DCP104

    Give your AI agents encrypted permission and keys

    May 2026 · dcpagent.com

  7. 7
    AgentKey417

    One-stop live data marketplace for your agent

    Jul 2026 · agentkey.app

  8. 8
    EnvKey79

    Protect api keys and credentials. Keep config in sync.

    2017

  9. 9KC

    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

  10. 10
    Keygen252

    A dead-simple software licensing API built for developers

    2016

  11. 11IB
  12. 12SR

    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

  13. 13

    Secure, orchestrate, and manage infrastructure secrets

    2021

  14. 14
    Latchkey122

    Credential layer for local AI agents

    Mar 2026 · github.com

  15. 15

    Your environment variables, finally in one safe place

    Jun 2026 · justenvs.app

  16. 16
    Cred97

    OAuth credential delegation for AI agents

    Apr 2026 · cred.ninja

  17. 17

    Encrypted secrets vault that blinds AI agents toyour APIkeys

    Jun 2026 · keyblind.dev

  18. 18KD

    I built this after seeing multiple teams accidentally ship API keys in their frontend code. The problem: Modern web development moves fast. You're vibe-coding, shipping features, and suddenly your AWS keys are sitting in a tag visible to anyone who opens DevTools. I've personally witnessed this happen to at least 3-4 production apps in the past year alone. KeyLeak Detector runs through your site (headless browser + network interception) and checks for 50+ types of leaked secrets: AWS/Google keys, Stripe tokens, database connection strings, LLM API keys (OpenAI, Claude, etc.), JWT…

    Nov 2025 · github.com

  19. 19SA
  20. 20KC

    We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The problem isn't just secret sprawl. It's that there's no lineage of access. You don't know which developer launched which agent, what it accessed, or whether it should have been allowed to. The moment you hand raw credentials to a process, you've lost the ability to enforce policy, audit access, or rotate without pain. The…

    Apr 2026 · github.com

  21. 21

    Secure zero-knowledge link sharing for developer credentials

    Jun 2026 · secrettly.space

  22. 22IB

    over this weekend myself and two of my friends took part in a hackathon and built this side-project. we have been diving into computer-use recently and developed an sdk to make it easy to implement for devs like us. one feature we were missing though, was the agent being able to log into services. anthropic understandably blocks this capability with their guardrails, and you wouldn't want your credentials to end up in any model context anyways. so we added a keychain service to the vm that the agent is using. it was built using the pass cli (https://www.passwordstore.org/).…

    2025 · github.com

  23. 23
    Keyva3

    A native env var manager with Keychain and iCloud sync

    Feb 2026 · apps.apple.com

  24. 24
    Prienv8

    Share secrets securely. Control access. Erase on your terms.

    Oct 2025

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