nowfound

Dev tools · alternatives · 2026

24 alternatives to Secli

A CLI to store secrets locally

Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Secli launched in 2022; newer entries below may have overtaken it.

  1. 1

    Contribute to fmeringdal/covert development by creating an account on GitHub.

    2023 · github.com · its alternatives →

  2. 2

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

    2017 · saltify.io · its alternatives →

  3. 3
    layer▲88

    I built a small CLI called layer. It manages .git/info/exclude so you can keep local-only files in a repo without adding them to the shared .gitignore. This came from a normal team repo problem. People keep their own local files in a repo: API_SPEC.md, BACKEND_GUIDE.md, ARCHITECTURE_NOTES.md, CLAUDE.md, prompt files, scratch notes, temporary investigation docs, and other markdown files with custom names that are useful for one developer but should not be committed. The usual answer is “just put it in .gitignore”, but that gets messy fast because these files are different for each…

    Mar 2026 · crates.io · its alternatives →

  4. 4

    We built OneCLI because AI agents are being given raw API keys. And it's going about as well as you'd expect. We figured the answer isn't "don't give agents access," it's "give them access without giving them secrets." OneCLI is an open-source gateway that sits between your AI agents and the services they call. You store your real credentials once in OneCLI's encrypted vault, and give your agents placeholder keys. When an agent makes an HTTP call through the proxy, OneCLI matches the request by host/path, verifies the agent should have access, swaps the placeholder for the real…

    Mar 2026 · github.com · its alternatives →

  5. 5CS

    Crypt : Store and retrieve encrypted configuration parameters from etcd or consul

    2014 · xordataexchange.github.io · its alternatives →

  6. 6

    crates.io serves as a central registry for sharing crates, which are packages or libraries written in Rust that you can use to enhance your projects

    2025 · crates.io · its alternatives →

  7. 7
  8. 8

    CLI first management of your environment secrets

    2023 · envsecrets.com · its alternatives →

  9. 9

    Secure, orchestrate, and manage infrastructure secrets

    2021 · 1password.com · its alternatives →

  10. 10SE
  11. 11

    Detect secrets in source code, public and private!

    2018 · gitguardian.com · its alternatives →

  12. 12

    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 · its alternatives →

  13. 13

    Manage secrets in your terminal with biometric unlock.

    2022 · 1password.dev · its alternatives →

  14. 14

    This is a tool to manage encrypted local backups of secrets. The core idea is that it aims to be usable without depending on it, meaning that even if the software disappeared from the face of Earth tomorrow, your data would still be recoverable. It also integrates nicely with NixOS (which is what I use, though it does not require NixOS to be used). I have summed up a bit of explanation and some answers to reasonable questions in a blog post: https://baldino.dev/blog/secs-man/

    Jun 2026 · github.com · its alternatives →

  15. 15
    Knox▲6

    A Secrets as a Service to manage your secrets and configs.

    2020 · knox-app.com · its alternatives →

  16. 16

    pacli is a secure, local-first secrets manager

    2025 · github.com · its alternatives →

  17. 17

    Hi 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 →

  18. 18

    Use KNOX, dead simple Secrets as a Service to manage all your keys, IDs and secrets for your dev team and your servers.

    2020 · knox-app.com · its alternatives →

  19. 19

    SSH access for developers. Secure, European, done right.

    May 2026 · securssh.com · its alternatives →

  20. 20KA

    Hi HN, I made Keepr, a simple offline CLI password manager for developers who prefer keeping secrets local and working entirely in the terminal. Everything is stored in an encrypted SQLCipher database, protected by a master password. A time-limited session keeps the vault unlocked while you work, so you don’t need to re-enter the password constantly. Keepr never touches the network. It includes commands to add, view, search, update, and delete entries, plus a secure password generator and clipboard support. Technical details: - AES-256 via SQLCipher - PBKDF2-HMAC-SHA256 (1.2M iterations) for…

    Nov 2025 · its alternatives →

  21. 21

    HTTP client/libcurl TUI front end in Rust, with request + key storage - PThorpe92/CuTE

    2023 · github.com · its alternatives →

  22. 22

    Save API keys, .env and secrets locally. Free & Open Source.

    Apr 2026 · passstore.makio.app · its alternatives →

  23. 23SH

    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 · its alternatives →

  24. 24

    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 · 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 →