Secryn

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: demo.secryn.io Docs/Install: docs.secryn.io/installation

@CiprianiRanieri secryn.io

Drop what you're building. No pitch. Just the link. I'll start. ↓

Secryn v1.0.1 is out: fixed restricted vault creation + vault ID copy for CLI. Full changelog: docs.secryn.io/changelog Demo: demo.secryn.io

Secryn now has an official CLI: docs.secryn.io/cli/introducti… Self-hosted team secrets are way easier when “get/set/rotate” is scriptable. What’s your preferred interface for secrets: UI, CLI, or CI-only?

Most “secret leaks” aren’t hackers — they’re workflow: keys in Slack, stale .env files, and no clear offboarding. The fix is boring: RBAC, audit trail, rotation, and rollback.

@clawioff That’s a great approach. “Scoped secrets per agent” + audit logs gets you 90% of the way there. The other thing teams keep asking for is **version history/restore** — when an agent (or human) overwrites a value and prod breaks, rollback needs to be instant.

@secrynio 100% — key sprawl is the silent killer. We're building scoped secrets per agent with audit logs so you can see exactly which agent touched which key and when. Offboarding is just revoking the agent's scope, not hunting through env files.

Day 3 on the onboarding flow. The bar we set: pick a host, choose your model, paste an API key, deploy. No YAML, no Docker commands, no infra degree required. If grandma can't deploy an agent, we're not done. sparebox.dev

@hasantoxr 100%. Key setup friction is brutal. The other piece teams need early is hygiene: RBAC + audit trail + rotation + rollback, otherwise secrets end up back in Slack/.env files.

The no-click setup is the real unlock. Every other agent tool in this space has: → API key setup → OAuth flows → 45 minutes of configuration AIVideo's agent: you describe what you want in plain English. It runs. This is what "no technical steps" actually looks like in 2025.

🚨BREAKING: The "OpenClaw for video production" just dropped. It's called AIVideo Agent and it runs your entire content pipeline 24/7 entirely on its own. No API keys. No technical setup. No configuration screens. Just tell it what you want. It ships.

If you’re running agent workflows: where do you store and share your API keys today (SSM, Vault, Doppler, 1Password, .env files)? What’s breaking first?

AI agents are making secrets sprawl worse: API keys in notebooks, env files, CI logs, Slack DMs. The fix isn’t “more docs” — it’s a team vault with RBAC + audit + fast rollback.

Projects → Vaults → Secrets in under a minute (self-hosted). Try the demo: demo.secryn.io

@AmenaiSabuwala Secryn is a self-hosted secrets vault for dev teams — secryn.io

are you an app founder? show me your app if it's live or gonna be live.

@AtharvaTiwari07 Secryn is a self-hosted secrets vault for dev teams — secryn.io

Hello founders What are you building today?

@mscode07 Secryn is a self-hosted secrets vault for dev teams — secryn.io

Share your website/project 👇

@Tobby_scraper Secryn is a self-hosted secrets vault for dev teams — secryn.io

GM Guys. Share your app! Let’s bring some lights on 💡

@S_N_SH_E_ Secryn is a self-hosted secrets vault for dev teams — secryn.io

Drop your project URL Let’s drive some traffic

@delveroin Secryn is a self-hosted secrets vault for dev teams — secryn.io

Pitch your startup - Max 5 words - link if ready Seen by 50k people yesterday and YES, it counts as marketing - GO! If you want me to promote it on my page, send a DM (Paid)

@jakobjelling Secryn is a self-hosted secrets vault for dev teams (RBAC, audit logs, version restore) — secryn.io

It's Monday. Time to promote your product. What are you working on?

Some teams are fine with SaaS vaults. Others need secrets to live inside their network boundary. Self-hosted isn’t about paranoia — it’s about control + policy. What’s your reason for self-hosting?

We built Secryn for this workflow: self‑hosted secrets vault with RBAC, audit logs, and version restore. Demo: demo.secryn.io

If you’re a small team, Vault can be overkill. If you’re using 1Password/Bitwarden, you may still want stronger team‑level governance for env/API keys.

Most teams shouldn’t “share .env files.” It starts in Slack/Notion, then becomes the permanent system.