MiniEnv vs
1Password Environments
If you already pay for 1Password Teams or Business, Environments is included and it is good. Use it. MiniEnv is worth your time in one case: you want removing a person to re-encrypt every value on the spot, and you do not want the people sharing keys to need a password manager account at all.
| MiniEnv | 1Password | |
|---|---|---|
| Five people | Free | $24.95/mo on Teams Starter Pack, or $44.95 on Business |
| Ten people | $29.99/mo, flat | $24.95/mo on Teams Starter Pack, or $89.90 on Business |
| Platforms | App: macOS 12+, Apple Silicon. CLI: comes with the app, needs Node 20.19 | Mac, Windows and Linux desktop apps; not iOS or Android |
| When somebody leaves | Every value re-encrypted before the removal is accepted | Access is revoked through group and vault permissions |
| Also gets you | A vault for secrets that are not KEY=value, and nothing beyond that | A password manager, SSH agent, commit signing, SSO, mobile apps |
| Secrets that are not KEY=value | A vault of up to 100 entries per project, alongside the env vars | Documents, secure notes and SSH keys, which it has stored for years |
1Password prices are from its own business pricing page and are the yearly-billing figures it quotes. The Teams Starter Pack covers up to ten members for one price, which is why the five and ten person rows are the same.
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.
At ten people, 1Password is cheaper than we are
Worth saying before anything else, because it is the first thing a table like the one above hides. The Teams Starter Pack is $24.95 per month billed yearly and covers up to ten members. Ten people on MiniEnv Pro is $29.99 per month. They win that row.
They also win a row we cannot compete on at all: that $24.95 buys a password manager for the whole team. If you were going to pay for one anyway, Environments is not an extra line on the invoice. And they are already installed: the 1password-cli Homebrew cask recorded 23,529 installs in 30 days and 368,809 in 365 days, which is a lot of developers who have the tool on their machine before they read a word of this.
The number that would make MiniEnv look better here is the Business tier at $8.99 per user per month, which is $89.90 at ten people. Quoting that one and not the Starter Pack would be the ordinary way to build this table. It would also be dishonest, so both are in it.
The actual difference is what a removal does
1Password revokes access the way a password manager does, which is the correct design for a password manager: permissions on a vault or a group change, and the person can no longer fetch the item.
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.
Whether that difference matters to you is a real question rather than a rhetorical one. It matters most when the value is one you cannot cheaply rotate at the source, and least when everything you share is a key you can regenerate in a provider dashboard in ten seconds.
One thing to check before you decide
The part of Environments that most resembles MiniEnv, mounting a local
.env file, is a public beta at the time of writing, on Mac and
Linux. 1Password says it is exploring options to bring it to Windows. The AWS
Secrets Manager integration is marked beta in their documentation too.
That is not a criticism. It is a thing worth knowing before you plan a team's workflow around it, and it is the kind of detail that gets quietly left out of comparison pages written by the other side.
When to use 1Password instead
- You already pay for it. Environments is included in the tiers above. Adding a second tool to do one job is worse than using the one you have.
- Anybody on the team is not on a Mac. This is not close. They cover Mac, Windows and Linux; we are macOS only, the app and the CLI alike.
- You want one place for everything. Passwords, SSH keys, commit signing, recovery codes, and the env vars next to them.
- You need mobile. Environments is desktop only, but the rest of 1Password is not, and MiniEnv has no phone story whatsoever.
- You need SSO, SCIM or an audit trail your auditor has heard of.
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.
- 1Password Teams Starter Pack is $24.95 per month billed yearly and covers up to 10 members, with further seats at $4.99 per seat per month.
https://1password.com/business-pricing · read 30 August 2026 - 1Password Business is $8.99 per user per month, billed yearly.
https://1password.com/business-pricing · read 30 August 2026 - 1Password lists developer tools, including the CLI and SDKs, as included in both the Teams Starter Pack and Business tiers.
https://1password.com/business-pricing · read 30 August 2026 - Worked out from the vendor price: 1Password at five people: $24.95 per month on the Teams Starter Pack, or $8.99 x 5 = $44.95 on Business.
https://1password.com/business-pricing · read 30 August 2026 - Worked out from the vendor price: 1Password at ten people: $24.95 per month on the Teams Starter Pack, which covers ten, or $8.99 x 10 = $89.90 on Business.
https://1password.com/business-pricing · read 30 August 2026 - 1Password Environments runs in the Mac, Windows and Linux desktop apps, and is not available in 1Password for iOS or Android. An Owner or Administrator has to turn the Environments policy on from the admin console.
https://www.1password.dev/environments/ · read 30 August 2026 - Local .env file mounting in 1Password Environments is a public beta, available on Mac and Linux; 1Password says it is exploring options to bring it to Windows.
https://1password.com/blog/1password-environments-env-files-public-beta · read 30 August 2026 - The AWS Secrets Manager integration in 1Password Environments is marked beta in 1Password's own documentation.
https://www.1password.dev/environments/ · read 30 August 2026 - The 1password-cli Homebrew cask recorded 23,529 installs in 30 days and 368,809 in 365 days.
https://formulae.brew.sh/api/ · read 30 August 2026 - Creating a vault entry is a Pro feature. Existing entries stay readable, editable and deletable on Free.
https://minienv.dev/ · 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
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.
Built for machines fetching secrets at runtime. We do not do that at all, which makes most of this comparison a question of which problem you have.
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.