# EnvDesk

> A local-first desktop workspace for managing and comparing environment files across projects.

EnvDesk is a local-first environment-file workspace, not a production secrets manager. It supports Windows, macOS, and Linux. Version 2.0.0 is the current documented release. The product has a 7-day full trial and a $12 one-time license for up to 3 devices.

## Product
- [Product](https://envdesk.app/env-file-manager)
- [Compare .env files](https://envdesk.app/compare-env-files)
- [Local-first workflow](https://envdesk.app/local-env-manager)
- [Pricing](https://envdesk.app/pricing)
- [Security boundary](https://envdesk.app/security)
- [Changelog](https://envdesk.app/changelog)
- [Free browser env diff](https://envdesk.app/tools/env-diff)

## Guides
- [What Is a .env File?](https://envdesk.app/guides/what-is-an-env-file): Learn what a .env file contains, how applications load it, and which security boundaries developers should understand.
- [How to Compare .env Files Safely](https://envdesk.app/guides/how-to-compare-env-files-safely): Compare environment-variable keys without exposing secrets or overwriting intentional differences.
- [.env vs .env.local vs .env.production](https://envdesk.app/guides/env-vs-env-local-vs-env-production): Understand common dotenv filenames and why framework-specific load order matters.
- [How to Detect Missing Environment Variables](https://envdesk.app/guides/detect-missing-environment-variables): Find missing configuration keys before they cause startup or deployment failures.
- [How to Prevent Environment Configuration Drift](https://envdesk.app/guides/how-to-prevent-configuration-drift): Use contracts, comparison, review, CI checks, and ownership to keep environments aligned.
- [Should Production Secrets Be Stored in .env Files?](https://envdesk.app/guides/should-production-secrets-be-stored-in-env-files): Understand when local dotenv files stop being an appropriate production secret-delivery mechanism.
- [How to Create a Safe .env.example File](https://envdesk.app/guides/create-a-safe-env-example): Document required environment keys without publishing live credentials or misleading defaults.
- [How to Manage Environment Files Across Multiple Projects](https://envdesk.app/guides/manage-environment-files-across-projects): Organize many local project configurations without mixing files or creating an unsafe source of truth.
- [Environment Variables in Next.js, Vite, Docker, and Tauri](https://envdesk.app/guides/environment-variables-nextjs-vite-docker-tauri): Compare build-time, runtime, client-exposure, and dotenv behavior across common application tools.
- [Pre-Deployment Environment Configuration Checklist](https://envdesk.app/guides/pre-deployment-configuration-checklist): Review required keys, values, exposure, ownership, and rollback before deploying configuration changes.

## Research
- [Environment configuration drift taxonomy](https://envdesk.app/research/environment-configuration-drift)