Built for Developers Who Care About Their Workflow.

SlickEnv is not a secrets vault with a CLI bolted on. It is a developer tool designed CLI-first, focused on environment variables, and ruthlessly simple to use.

The CLI is the product.

There is no web dashboard you have to click through. No browser tab you forgot was open. SlickEnv lives in your terminal, right next to your code. Every action is a single command. Every output is designed to be read at a glance.

$ slickenv init          # Link your project
$ slickenv push         # Push local .env to the cloud
$ slickenv pull         # Pull latest .env from the cloud
$ slickenv status       # See what's changed
$ slickenv versions     # List all versions
$ slickenv diff         # Compare local vs remote
$ slickenv rollback     # Restore a previous version
$ slickenv share        # Share with a teammate
$ slickenv export       # Export to .env, JSON, or YAML
$ slickenv login        # Authenticate
$ slickenv logout       # Sign out

Your .env files, but smarter.

SlickEnv reads and writes standard .env files, but it also understands metadata annotations. Add a comment above any variable and SlickEnv will track it, validate it, and display it in context.

# @description Stripe secret key for payment processing
# @required true
# @sensitive true
# @format stripe_secret_key
STRIPE_SECRET_KEY=sk_live_abc123

Field	Purpose
@description	Human-readable explanation of the variable
@required	Whether the variable must be set
@sensitive	Masks value in CLI output and logs
@format	Expected format or pattern
@default	Default value if not set
@example	Example value for documentation

Push and pull with confidence.

SlickEnv detects conflicts before they become problems. If your local .env has diverged from the remote version, you will know before anything is overwritten.

$ slickenv push
⚠ Conflict detected in 2 variables:

  DATABASE_URL
    Local:  postgres://localhost:5432/myapp_dev
    Remote: postgres://prod-db:5432/myapp

  REDIS_URL
    Local:  redis://localhost:6379
    Remote: redis://prod-cache:6379

? How would you like to resolve?
  › Keep local values
    Keep remote values
    Review one by one
    Abort

Every change, safely stored.

Every push creates a new version. You can list versions, compare them, and roll back to any previous state, instantly.

$ slickenv versions
  v7  2 minutes ago    14 variables  "Added Stripe keys"
  v6  3 hours ago      12 variables  "Updated DB config"
  v5  yesterday        12 variables  "Initial production setup"

$ slickenv rollback v5
✓ Rolled back to v5 — .env updated with 12 variables.

Share environments. Not secrets.

SlickEnv gives you four ways to share environment configurations with your team, each designed for a different level of trust and access.

Team sync

Everyone on the team pulls the same environment. Changes are versioned and attributed.

One-time share link

Generate a single-use, time-limited link that expires after one pull or after a set duration.

Export to file

Export your environment to .env, JSON, or YAML and share it however you like.

Role-based access

Control who can read, write, or admin each environment. Fine-grained permissions per project.

Secure by design, not by configuration.

Security is not an add-on. Every part of SlickEnv is built with encryption, access control, and auditability from the ground up.

AES-256-GCM encryption at rest for all stored variables
TLS 1.3 encryption in transit for every API call
No secrets are ever logged, cached, or written to disk in plaintext
Sensitive values are masked in all CLI output by default
OAuth 2.0 authentication via GitHub or Google
Per-project, per-environment role-based access control
Full audit trail of every push, pull, share, and rollback

Ready to simplify your env workflow?

Get started in under a minute. Free for individual developers.