Faris Chtatou

How does your team manage environment variables?

We’ve all been there. You onboard a new developer, and suddenly you’re getting a ping:

“Hey, where can I find the latest .env file?”

“Wait… is this API key still valid?”

“Why do we have secrets in a Notion doc?!”

Managing environment variables starts out simple but quickly becomes messy as teams grow, projects multiply, and more people get access.

Some teams:

Use .env files shared via Slack or email (😬)

Store secrets in Notion or Google Sheets (😱)

Have no audit logs, versioning, or access control

We were facing the same issues, so we built an internal tool to fix it. It grew into @Keyrua , a secure, developer-friendly way to manage, share, and version secrets across environments and projects.

I'd love to hear:

How your team handles secrets today?

What’s the most painful part of managing them?

Do you prioritize audit logs, Git syncing, or ease of access?

Let’s share ideas and maybe we can help each other build safer practices!

19 views

Add a comment

Replies

Be the first to comment