Why Sharing .env Files Does Not Scale
The personal annoyance that started EnvBox, why existing options did not fit a small workflow, and what we wanted instead.
Last updated 2026-09-25T08:47:45.067Z
It started at home
I work across more than one computer at home. Sometimes the family uses the laptop, so I switch machines. For code that is easy: the project lives in Git, and one git pull brings everything up to date.
Environment variables were different. The first real friction showed up when a project needed a database connection and a few API keys. Each machine needed the same values. The practical “solution” was to send them to myself through a chat app and paste them again — fine once, annoying every time something changed.
I am mostly a frontend developer, so I was not juggling dozens of environments. I still needed real values for databases, email providers and other APIs. That was enough for the workflow to feel broken.
When values change often
The pain was sharpest when a key changed several times in a few days. While wiring Resend for email, the API key was updated more than once. Each change meant updating every machine I touched that week. Sending and re-pasting the same secret over and over is exactly the kind of busywork Git already solved for source code.
On a tiny solo project you can live with a note-to-self. The same habit gets worse as soon as:
- more than one environment exists (dev, staging, prod)
- more than one person needs access
- someone leaves and you no longer know who still has the latest file
What already existed
I looked for tools that already solved “share env vars without pasting into chat.” Names that came up included Doppler, Infisical and dotenvx.
They are capable products. In broad terms:
Direction | What you get | Why it was not our fit then |
|---|---|---|
Doppler | Polished hosted secrets manager, strong CLI, free tier for a very small team | Aimed at managed secrets workflows; more product surface than we needed for “pull env like git” |
Infisical | Open-source option, cloud or self-hosted, full secrets platform features | Powerful, but heavier to adopt when the goal was a minimal join-and-pull loop |
dotenvx | Encryption and sync ideas closer to the .env file itself | Useful path, but not the simple team invite + dashboard + CLI shape we had in mind |
The point was not that those tools are bad. It was that for a two-person workflow we wanted something small, free, open source, and biased toward “two commands in the terminal” rather than adopting a full secrets platform on day one.
What we wanted
- Simple: sign up and use it in minutes.
- Free and open source.
- Git-like in daily use: after joining once, pull environments from the project folder without opening the site every time.
- Suitable for small teams moving settings between machines quickly, with basic control over who can see which environment.
That gap is what EnvBox was built to fill. Continue with how EnvBox works.
Was this page helpful?