SlickEnv is designed to fit into how you already work. Install it, connect your project, push your .env, and pull it anywhere.
One command. Works on macOS, Linux, and Windows (via WSL). No runtime dependencies.
$ curl -fsSL https://slickenv.dev/install | shSign in with GitHub or Google. Your credentials are stored securely in your system keychain.
$ slickenv login
→ Opening browser for authentication...
✓ Authenticated as you@example.comLink a directory to a SlickEnv project and environment. This creates a lightweight config file. No lock files, no heavy setup.
$ cd my-project
$ slickenv init
? Project name: my-project
? Environment: development
✓ Initialised — linked to my-project/developmentPush your local .env file to SlickEnv. It is encrypted, versioned, and stored securely.
$ slickenv push
✓ Pushed 14 variables — version 1 created.On a new machine, after cloning, or on a teammate's laptop, just pull. The latest version is written to your local .env file.
$ slickenv pull
✓ Pulled version 1 — .env updated with 14 variables.Once you are set up, the daily workflow is two commands: push when you change something, pull when someone else does.
# You added a new variable locally
$ slickenv push
✓ Pushed 15 variables — version 8 created.
# Your teammate pulls the latest
$ slickenv pull
✓ Pulled version 8 — .env updated with 15 variables.
# Check what changed
$ slickenv diff
+ NEW_API_KEY=sk_live_xyz789If you and a teammate both change the same variable, SlickEnv detects the conflict and asks you how to resolve it. Nothing is ever silently overwritten.
$ slickenv push
⚠ Conflict detected in 1 variable:
API_URL
Local: https://staging.api.example.com
Remote: https://api.example.com
? How would you like to resolve?
› Keep local values
Keep remote values
Review one by one
AbortInstall SlickEnv in under 30 seconds. Free for individual developers.