Help
FAQ
Short answers to common questions.
Is it end to end encrypted?
Yes for values: they are encrypted on your device before upload and decrypted only on devices of people who were given the keys. The server stores ciphertext and can't read it, and signatures stop it from changing values unnoticed. Names of projects, environments, files and keys, and who changed what and when, are visible to the server so it can show history and enforce access. StoreEnv is in beta and the cryptography hasn't been independently reviewed yet; the client is an open-source client (storeenv-cli and @storeenv/core, Apache-2.0), so you can read exactly what it does.
Do I need Git?
No. A plain folder works the same. Git adds a committed .storeenv.json that teammates get when they clone, optional linked repositories and branch rules.
Do I need GitHub?
No. Sign in with email and password. GitHub, GitLab and Google sign in are optional, and linked repositories can be on any host.
Can I use it in CI?
Not directly yet: there are no machine tokens. See Using StoreEnv in CI for the safest current setup.
What does it cost?
StoreEnv is free during the beta. No plan limits are enforced today.
Can I self host?
The CLI and @storeenv/core are open source (Apache-2.0); the hosted server is not. The CLI accepts --api and STOREENV_API for a server you run, but no server is published for self hosting today.
What happens if StoreEnv goes away?
storeenv pull --all writes every environment you can read to files on your machine. Do that and keep the files somewhere safe if you ever need to leave.