Compare
Last reviewed November 2026. This describes how each tool is designed to work. Check the vendor's own docs for current details.
8 points
| StoreEnv | Doppler | |
|---|---|---|
| Where values are decrypted | On your devices only | On the provider's servers, which then deliver them to you |
| Set up | storeenv init in any folder: folders become services, file suffixes become environments | Projects and configs are created in the product |
| Without Git | Yes. A committed .storeenv.json names the project; remotes on any host are optional | Yes. Projects aren't tied to a repository |
| Source code | Open-source client (CLI and encryption library), Apache-2.0. The server is hosted | The CLI is open source; the service is hosted |
| Reuse across projects | Imports from library projects: filters, pins, access checked at the source | References between projects and configs |
| Sharing unit | Down to a single secret | Projects and configs, with role-based access |
| Works from | CLI first, dashboard for history and access | Dashboard and CLI |
| Integrations | Run the CLI in your own pipeline. Native syncs are planned | A large catalogue of native syncs |
Fair play
- 01You want values synced into many deploy platforms without running anything yourself.
- 02You're comfortable with the provider being able to process your secrets.
- 03You need a mature product with support contracts today.
Try StoreEnv
Spot an error? Tell us.