We built Secryn for teams that are tired of secrets scattered across Slack/docs/.env files.
Self-hosted vault, simple team workflows, audit-friendly.
Try the public demo: https://t.co/3r9voHUmDV
Docs/Install: https://t.co/MjZZvSe6rK
Devs who've offboarded someone: what was the hardest thing to revoke?
CI tokens, a shared cloud login, SSH keys on an old server, something in a SaaS nobody remembered?
Collecting real war stories.
Cert expiry is the most boring outage there is.
Cheap fixes: keep every cert's expiry date in one list, alert at 30 and 7 days, and include internal tools and mTLS certs, not just the public site.
The one that breaks is the one nobody remembered.
@hackrowd Split by blast radius: .env holds only dev values that are harmless if leaked (local DB, sandbox keys). Anything shared or staging-grade comes from a vault at run time, so offboarding and rotation are one change. We make Secryn, a self-hosted vault for that half.
@munawwarfiroz Good swap for static secrets. Two things to watch: standard params share a ~40 TPS GetParameter limit per region, so cache at startup or a cold-start burst gets throttled. And you lose Secrets Manager's rotation hooks, so tag each one with its last-rotated date.
@PeterOmogo2 Classic single-file bind mount trap: Docker pins the inode, so mv, sed -i and most editors (write temp, then rename) swap in a file the container never sees. Mount the parent dir instead, or overwrite in place: cat new.env > .env. Restart if the app reads env only at boot.
Small build detail: we had to rename our CLI's test fixtures because secret scanners kept flagging our own fake test secrets.
Shipped in secryn-cli v1.0.3, along with `secryn run`. A secrets tool tripping secret scanners. Fair.
@raunakhajela@doppler Ouch. The token that unlocks everything else is the one credential your secrets manager can't remind you about. Worth putting its expiry in the same alerting as your TLS certs, and having the app fail loudly on a 401 at boot instead of starting with empty config.
@sysadafterdark@Nagistakee Your failover point is the real constraint, whichever vault you pick. DR pipelines need a path to secrets that doesn't route through the primary site: a replica or cache at the DR site, or a sealed break-glass bundle with the unseal key kept offline. Which way are you leaning?
If a Laravel .env ever leaks, rotating the DB and API keys isn't enough. APP_KEY signs cookies and encrypts data, so rotate it too.
Laravel 11+ has APP_PREVIOUS_KEYS for reading old data, but don't leave a leaked key in there forever.
@sattyyouneed Private helps a lot: exposure is everyone with repo access plus any app or CI integration that can read it. It's in history now, so deleting the file won't undo it. Rotate anything touching prod or billing; the rest depends on who's on the repo. Solo repo or team?
@emlasd Yeah, that's the classic trap: the S3 key for the tofu state can't live in a vault that only exists after apply. Keep bootstrap creds outside (a passphrase file or the cloud's own secret store for the host), and only move app secrets into Infisical once the box is up.
Run a command with secrets from a vault, no .env file:
secryn run -- php artisan queue:work
Secrets go into that one process's environment and are never printed. If the vault can't be read, the command doesn't start.
Question for teams with 5-30 devs: where does the production DB password live today?
A) a .env on the server
B) CI secrets
C) a password manager
D) a secrets vault
E) honestly, not sure
Curious which one wins.
Cheap secrets drill: pick one dev, list every secret their laptop could read, then time how long it takes to revoke and rotate them all.
Most teams find the list is the hard part, not the rotation. Write the list down before the day you need it.
@Surendar__05 Most replies say "secret manager", and the useful part is that nobody gets a .env file at all: each dev and environment gets its own access, the app or CLI pulls values at runtime, and offboarding is one revoke. We make one, Secryn, a self-hosted vault for team secrets.
@justdevopsguy One vault with per-environment access, pipelines pulling at deploy time with short-lived tokens (nothing in repo or CI config), every read logged, and cert expiry tracked in the same place. We make one for that, Secryn, a self-hosted vault for team secrets, keys and certs.
@kaza_ooo Two clean ways: give it its own git dir, e.g. git --git-dir=.envgit --work-tree=. add -f .env (and add .envgit to .gitignore), or keep .env in a private dotfiles repo and symlink it in. Either way the main repo never sees it.
@ratishtwts Private only means private today. Every clone, CI runner, fork and ex-employee laptop keeps a copy, and git history keeps it forever. Keep .env out of the repo and pull values from a vault at deploy. We make one, Secryn, a self-hosted vault for a team's app secrets and keys.
@Worshipperfx Two halves: getting the new value in, and keeping the old one valid until every pod has it. External Secrets Operator syncs on a refreshInterval; mount as a volume (env vars never update) or use Reloader for a rolling restart. Rotate with two live creds, revoke the old last.