MiniEnv vs
Doppler
Doppler is a secrets platform for machines: services fetch values at boot, CI pulls them at build, and the dashboard is a control plane. MiniEnv shares values between people on a Mac and has no runtime at all. If servers read your secrets, use Doppler. If humans paste them into DMs, that is our job.
| MiniEnv | Doppler | |
|---|---|---|
| Five people | Free | $16/mo (3 free, then $8 each) |
| Ten people | $29.99/mo, flat | $56/mo on Developer, or $210 on Team |
| CI and machine access | Not supported | Service tokens; non-human identities do not take a seat |
| Runtime injection | None. Values land in your .env and stop there. | Yes, across environments and integrations |
| Environments | Free is the one tab a project starts with; Pro adds more | 4 on Developer, 15 on Team |
| Secrets that are not KEY=value | A vault of up to 100 entries per project, alongside the env vars | Secrets live in the same config as the env vars |
Doppler figures are from its own pricing page. The per-person maths is spelled out in the sources below rather than left for you to reproduce.
What MiniEnv does not do. The app runs on macOS 12 or later, on Apple Silicon. There is a CLI, which does the same encryption with the same Keychain identity and covers projects, members, teams, devices and the vault, but it is macOS only as well and it needs Node 20.19. So: no Windows, no Linux, no iOS, no Android, on either. Nothing injects secrets into a running service and nothing fetches values at boot. If any of that is a requirement, stop reading here: the tool on the other side of this page is the right one.
These are not the same category of thing
Doppler sits between your secrets and everything that consumes them. A service starts, authenticates with a service token, and gets its values. That is the product, and the dashboard, the environments and the integrations all exist to serve it.
MiniEnv has none of that and is not planning to. Values are decrypted on a Mac, by a person, into a file. Nothing fetches from us at boot. If you deploy anything that needs a secret at runtime, Doppler is solving a problem we do not touch.
Which means the price rows above are close to meaningless on their own. They compare a platform against an app that does one tenth as much, and a tenth of the work should cost less.
The free tiers, since that is where small teams actually decide
Doppler Developer is free for 3 users and includes 10 projects, 4 environments and 50 service tokens. MiniEnv Free covers five people including the admin, and one environment tab per project.
So at three people Doppler is free and does considerably more than we do. At five, Doppler is $16 per month and we are free. At ten, Doppler is $56 on the Developer tier and we are $29.99. Whether crossing that line is worth it depends entirely on whether you needed the platform half.
One point in Doppler's favour that is easy to miss: it states that non-human identities do not consume a seat on any tier. That is not the industry norm, and it matters a great deal if you have more CI jobs than people.
What we do that Doppler does not
Remove somebody from a project and every value in it is re-encrypted, on the machine of whoever removed them, before the change is accepted. There is no window in which the removed person can still read a new value.
What that does not do, and what no tool can do, is reach backwards. Anything they already pulled, they still have. Rotate it at the source.
Doppler holds your secrets in a form it can read. That is not a flaw, it is required: a platform that injects a value into your service at boot must be able to produce the value. It is a real difference in what a breach of the vendor costs you, and it is the one thing this whole product is arranged around.
When to use Doppler instead
- Anything fetches secrets at runtime. Services, containers, CI. We have no answer here at all.
- Anyone is not on a Mac.
- You have more machines than people. Non-human identities riding free is a genuinely good deal.
- You need more than a couple of environments, or projects numbered in the dozens.
- Somebody is going to ask for SOC 2 evidence. They have that programme; we do not.
Where these numbers came from
Every figure above, including ours. If one of them has gone stale, it is a bug on this page and worth telling us about.
- Doppler Developer is free for 3 users, and includes 10 projects, 4 environments and 50 service tokens.
https://www.doppler.com/pricing · read 30 August 2026 - Doppler Developer charges $8 per month for each user beyond the third.
https://www.doppler.com/pricing · read 30 August 2026 - Doppler Team is $21 per user per month, and allows up to 500 users, 250 projects, 15 environments and 500 service tokens.
https://www.doppler.com/pricing · read 30 August 2026 - Doppler states that non-human identities do not consume a seat on any tier.
https://www.doppler.com/pricing · read 30 August 2026 - Worked out from the vendor price: Doppler at five people: 3 free plus 2 at $8 = $16 per month.
https://www.doppler.com/pricing · read 30 August 2026 - Worked out from the vendor price: Doppler at ten people: 3 free plus 7 at $8 = $56 per month on Developer, or $21 x 10 = $210 per month on Team.
https://www.doppler.com/pricing · read 30 August 2026 - MiniEnv Free is $0 and covers five people, including the admin.
https://minienv.dev/ · read 30 August 2026 - MiniEnv Pro is $29.99 per month, flat, with no per-seat charge, and one subscription covers up to 3 teams you run.
https://minienv.dev/ · read 30 August 2026 - The MiniEnv app runs on macOS 12 or later, on Apple Silicon. There is no Windows, Linux, iOS or Android client.
https://minienv.dev/ · read 30 August 2026 - There is a MiniEnv CLI. It does the same encryption on your machine, with the same Keychain identity as the app, and covers projects, members, teams, devices and the vault. It ships inside the app and is installed from Settings in the app, so it is the same release as the app; it needs Node 20.19 or later, and is macOS only, because private keys live in the macOS Keychain.
https://minienv.dev/ · read 30 August 2026 - A MiniEnv project has a vault: a separate collection for secrets that are not KEY=value, such as a service-account JSON, an Apple .p8, a PEM or SSH deploy key, recovery codes or a note. A project holds up to 100 entries, each at most 65,536 bytes once encrypted.
https://minienv.dev/ · read 30 August 2026 - The vault is a different collection from a project's env vars, so a pull cannot write a vault entry into a .env file and a Vercel push cannot send one. Removing a member re-encrypts the vault and the env vars in the same write, and a client that submits one without the other is refused.
https://minienv.dev/ · read 30 August 2026
The other comparisons
They are already in the building, and Environments is included in the plan you pay for. The case for looking anyway is narrow, and it is about what happens when somebody leaves.
Encrypt the .env file and commit it, versus keep the values out of the repo. Both are defensible. They differ most on the day somebody leaves.
The real competitor. It costs nothing, needs no account, and works today. Here is what it actually costs you, and when it is still the right call.
Open source, self-hostable, and free for five identities. The catch is what an identity is, and it is worth understanding before you plan around the free tier.
Encrypt it and commit it. Free, portable, and used heavily. The manual part is key management, and that is the part we automate.
If your workloads are in AWS, this is not really a competitor, and the free Parameter Store option is the one that deserves your attention first.