nowfound

Alternatives

Products that do what Secli does

A CLI to store secrets locally

  1. 1

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

    2017

  2. 2

    Secure, orchestrate, and manage infrastructure secrets

    2021

  3. 3

    Detect secrets in source code, public and private!

    2018

  4. 4
    Shelve156

    Effortless & secure secrets management

    2025

  5. 5
    Locki103

    Encrypt/decrypt text directly where you type

    2025

  6. 6AT
  7. 7
    Latchkey122

    Credential layer for local AI agents

    Mar 2026

  8. 8

    Distributed password manager & only you can access

    2023

  9. 9

    Store and share your files securely

    2020

  10. 10
    Secur377

    First decentralized 2FA solution for self-custodial wallets

    2022

  11. 11SH

    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

  12. 12CA
  13. 13

    Stop remembering passwords

    2018

  14. 14KC

    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

  15. 15

    Securely store your secrets in GitHub Private Repo

    Feb 2026

  16. 16RB
  17. 17CH
  18. 18LH

    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

  19. 19SR

    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

  20. 20LS

    Hey HN, Localias is a new tool that you can use to securely manage your local development servers. Use localias to securely proxy a local development server running on http://localhost:3000 and access it at https://frontend.test. Localias is built on top of Caddy, so it's secure and performant. And because it's built on top of Caddy, it will automatically generate and install a custom root certificate, and automatically generate and sign certificates for each of your aliases. This all works by editing your /etc/hosts file and generating a Caddy config, then…

    2023 · github.com

  21. 21HS

    Hi HN! I built hidetext.sh — a way to share text, code, and files through links the server can't read. How it works: your browser generates a random key and encrypts everything locally (NaCl secretbox, XSalsa20-Poly1305). Only ciphertext is uploaded. The key goes into the URL fragment — the part after # — which browsers never send to servers. The link carries the key, my server stores the locked box, and the two only meet in a browser. A design detail I'm fairly happy with: burn-after-read doesn't destroy the paste on the first HTTP request. The naive version means a Slack or iMessage link…

    Jul 2026 · hidetext.sh

  22. 22AO

    I’ve lost count of how many times a junior engineer accidentally pushed something into a dev branch that either contained secrets/credentials etc. or that leaked those into logs/std. out. Secure-log prevent logging for apps on production, scan for Secrets and remove them from logging. No more console.log().

    2024 · github.com

  23. 23OA

    This is a tool I started working on whenever pypi decided to make 2FA mandatory. I've already been using it to login to pypi for a while, but only finished the remote capabilities recently. It can be installed by simply running: `pip install open2fa` Any secrets that are stored remotely are encrypted, so the person running the api (me) provably cannot use any remotely stored secrets. It's possible to use pushed TOTP secrets from any device with the open2fa CLI installed, as long as the original UUID is known. It's also possible to use any pushed secrets to generate 2FA codes from any device…

    2024 · github.com

  24. 24JA

    Hi all! It's been a while since I posted something. Wrote this back in November to scratch an itch regarding tailing logs locally for multiple services. I know we all love jq...but I'm quite comfortable with SQLite and SQL so just wanted to use that instead. Published my first Rust crate today! My first public Rust project so be gentle :) . Hope you enjoy it! https://crates.io/crates/jlq https://github.com/hamin/jlq

    2023 · github.com

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