How do you manage your .env files today?

A quick 3-minute survey about how developers handle secrets and environment variables. No right or wrong answers — just honest takes. Results will shape a tool we're building.

How do you currently manage environment variables across your projects?

How many active projects do you manage with distinct environment variables?

A

1

B

2-3

C

4-6

D

7-10

E

More than 10

What's your primary tech stack?

Where do you host your projects?

Do you use multiple environments (dev, staging, production)? How do you keep them in sync?

A

Yes, manually

B

Yes, with a dedicated tool

C

I don't use multiple environments

D

I don't — it's chaotic —

What would make you distrust a new tool for storing your production credentials?

Have you ever used Doppler, Infisical, EnvKey, or a similar tool? Why did you stop — or why haven't you started?

A

Yes, I currently use one

B

Yes, but I stopped

C

I tried but didn't adopt it

D

Never tried

Have you ever leaked a credential or feared you might have? What happened?

What's your preferred way to interact with a secrets management tool?

1

CLI in the terminal

1

Web dashboard

1

VS Code extension

1

GitHub Action / CI integration

1

SDK inside the application code

If you could fix only one thing about secrets management right now, what would it be?

A

Share secrets with my team without using Slack

B

Never leak credentials into a repository

C

Keep all environments in sync without missing anything

D

Know who changed what and when

E

Stop depending on .env files on local machines