devenv

devenv is a free, open-source environment manager for developers who want a project’s setup shared as configuration across local work and CI. It is strongest for teams already willing to use Nix; anyone seeking a standalone tool should look elsewhere.

Overview

A project can define its packages, languages, services, tasks, secrets, and tooling in devenv configuration, giving contributors a common setup rather than a collection of manual steps. Dependency locking and configuration as code help keep that setup consistent. The trade-off is fundamental: Nix must be installed before devenv can be used.

devenv also supports environment variables, files, and scripts for bash, zsh, fish, and nushell. Cached shell startup is under 100 ms after the first build, which benefits repeat use but says nothing about initial setup time. The project is MIT licensed, with GitHub issues and Discord as routes for help and community discussion.

Key features

Languages and services: The project supports 58 languages, including version pinning and language server support, and provides 42 preconfigured services. PostgreSQL, Redis, MySQL, RabbitMQ, MinIO, Caddy, and Elasticsearch are among the examples. That breadth suits projects whose development setup needs more than a runtime alone.

Processes and tasks: Supervised processes can declare dependencies and restart; tasks can run in parallel and integrate with shells or commits. This makes devenv useful for coordinating project workflows as well as setting up tools.

Secrets: SecretSpec can read declared secrets from sources including Keychain, 1Password, LastPass, dotenv, and environment variables. Teams can keep secret handling within the environment configuration without relying on a single source.

Containers and tests: devenv can build OCI containers from a development environment and run integration tests while its processes are active. GitHub Actions can use the same environment for checks, builds, and tests, an appealing fit for teams seeking continuity between development and CI.

Integrations and trust: Documentation covers direnv, IntelliJ, VS Code, Zed, GitHub Actions, and an MCP server for AI assistants. Projects must be explicitly trusted before auto-activation, a useful safeguard against an untrusted project changing the shell.

Pricing

The Free (MIT-licensed open source) plan costs nothing. It includes the Nix-based tool without a paid tier or seat cap in the stated plan, making it a practical choice for individuals and teams prepared to manage their own environments. It requires Nix and works on Linux, macOS, and WSL.

devenv Cloud is in private beta with early access sign-up. It is not a generally available alternative to the open-source workflow.

Platforms

devenv works on Linux, macOS, and WSL once Nix is installed; WSL provides a route for Windows users through Linux. The project no longer builds, tests, or releases devenv for Intel Macs as of version 2.4. Mac users on Intel hardware should therefore choose another tool if ongoing project support is essential.

Who it's for

devenv is a strong fit for development teams that want reproducible, code-defined environments shared across contributor machines and CI, especially when they need language runtimes, services, processes, and integration tests in one setup. It is less suitable for developers who do not want Nix as a prerequisite, or Intel Mac users who need supported builds and releases.

Pros and cons

Pro: Configuration, dependency locking, runtime management, and shell integration provide a structured way to keep project environments consistent.

Pro: A broad catalogue of languages and services, alongside supervised processes and parallel tasks, covers more than basic package setup.

Pro: OCI container builds and GitHub Actions support extend the environment into testing and CI workflows.

Con: Nix is required, adding a prerequisite that rules out users seeking a standalone manager.

Con: Intel Mac builds, tests, and releases have ended as of version 2.4, leaving that platform without current project support.

Alternatives

ActiveState Platform offers a free organization plan limited to public projects and a paid organization option with custom pricing; consider it if that public-project model fits better.

PortBay has a free Community plan capped at six projects, or three without an account, plus two sandboxed runs, 10 MB of task attachments, and one Mac. Choose it when those explicit project and run limits suit the work.

Flox has a free Personal plan with its CLI and Catalog access, unlimited public FloxHub environments, and three private environments. It is an option for readers who want those hosted environment allowances.

FlyEnv offers a free plan with three local sites, three custom projects per runtime, one Cloudflare Tunnel, and three-day trials for some AI, screenshot, and image-optimization features. Consider it if that local-site model matches your needs.

ServBay has a free plan covering five websites, five DNS records, several language runtimes, and databases including MySQL, MariaDB, PostgreSQL, and MongoDB. It may suit readers whose needs center on that website and service setup.

Devbox is an open-source project built by Jetify with community support, with a Solo plan at $5 a month. It is a nearby option for readers comparing another open-source environment manager.

vfox is a free, Apache 2.0-licensed option for Linux, macOS, and Windows.

mise is a free, MIT-licensed CLI for macOS, Linux, and Windows.

Browse Development Environment Management Tools or Development Environment Managers for more options.

Verdict

Choose devenv if your team wants a free, MIT-licensed way to define project environments, services, processes, and CI workflows together and is comfortable with Nix. Its range and reproducibility are the case for it; the Nix requirement and end of Intel Mac support are the reasons to look elsewhere.