Overview

Projects use devenv configuration to define the tools and services contributors need, rather than relying on each person to assemble an environment independently. Dependency locking and configuration as code help keep that setup consistent. The payoff is strongest when a team wants its development environment to cover both daily work and CI; adopting devenv is a less natural choice if the team does not want to use Nix.

The tool can also build OCI containers from a development environment and run integration tests with its processes active. GitHub Actions can use devenv for checks, builds, and tests. Cached shell startup is under 100 ms after the first build, which benefits repeat use but does not describe initial setup time.

Key features

Languages and services: devenv lists 58 supported languages, with version pinning and language server support, alongside 42 preconfigured services. Examples include PostgreSQL, Redis, MySQL, RabbitMQ, MinIO, Caddy, and Elasticsearch. That range suits projects whose setup includes supporting services as well as language runtimes.
Environment configuration: A project can declare packages, variables, files, and scripts for bash, zsh, fish, or nushell. This gives teams a way to keep shell setup and project tooling in the same configuration.
Processes and tasks: Supervised processes can declare dependencies and restart, while tasks can run in parallel and integrate with shells or commits. This is useful when a project needs repeatable task workflows alongside its service setup.
Secrets: SecretSpec can read declared secrets from sources including Keychain, 1Password, LastPass, dotenv, and environment variables. Projects must be explicitly trusted before auto-activation, a safeguard against an untrusted project changing the shell.
Integrations: Documentation covers direnv, SecretSpec, GitHub CI, an MCP server for AI assistants, and editor integrations including IntelliJ, VS Code, and Zed. This helps connect devenv to existing workflows, though the Nix requirement remains.

Pricing

Free (MIT-licensed open source): 0.00 USD per free. The plan is free and includes the open-source tool. It requires Nix and works on Linux, macOS, and WSL. For teams comfortable with those requirements, the free plan is the main offering; there is no paid tier described for the core project.

devenv Cloud is in private beta, with early access sign-up. The Cloud service is therefore not a generally available plan to rely on for a current rollout.

Platforms

Install instructions support Linux, macOS, and WSL after Nix is installed. Intel Mac support has ended: as of version 2.4, devenv no longer builds, tests, or releases for Intel Macs. Teams with Intel Mac users should account for that limitation before standardizing on it.

The entry also includes web and Windows among its platforms, but the installation guidance specifies Linux, macOS, and WSL. The practical requirement remains Nix, so platform selection alone does not make devenv a standalone environment manager.

Who it's for

devenv is a strong fit for teams already willing to adopt Nix and looking to describe packages, languages, services, secrets, and tasks in a shared project setup. Its CI, container, and integration-test workflows are especially relevant when teams want development and build environments to use the same configuration.

It is a weaker fit for teams seeking an environment manager without Nix, or for organizations that need supported Intel Mac builds. Its MIT license, GitHub source and issues, and Discord community provide open-source access and community help.

Pros and cons

Pro: Configuration spans packages, languages, services, secrets, shell tooling, and tasks, so teams can manage more than runtime versions in one project setup.
Pro: OCI container builds, active-process integration tests, and GitHub Actions support extend the same environment into CI workflows.
Pro: The core tool is free and MIT-licensed, with no paid plan required to use it.
Con: Nix is required, which rules out teams unwilling to add that prerequisite to their development setup.
Con: Intel Mac builds, tests, and releases have ended as of version 2.4, limiting suitability for teams relying on that hardware.
Con: devenv Cloud remains in private beta, so teams cannot treat it as a generally available service.

Alternatives

ActiveState Platform is worth comparing for teams considering a freemium option with a free organization plan limited to public projects.
Flox offers a free Personal plan with CLI and catalog access, unlimited public FloxHub environments, and three private environments; consider it if those environment-sharing terms better fit your needs.
Nix is the free, open-source package manager to choose if you want Nix itself rather than devenv's project environment tooling.
vfox is a free, Apache 2.0-licensed alternative.
asdf is a free, open-source tool version manager for Linux and macOS.
DDEV is a free, open-source option under the Apache 2.0 license.
FlyEnv has a free plan with caps including three local sites and three custom projects per runtime.
GNU Guix is free software for GNU/Linux or a complete GNU system.
Browse Development Environment Management Tools and Development Environment Managers for more options.

Verdict

Choose devenv if your team wants a free, Nix-based project configuration that can carry languages, services, tasks, secrets, and CI workflows together. Its strongest reason to choose it is that breadth across local development and CI; its clearest reasons to look elsewhere are the Nix prerequisite and lack of Intel Mac support.

	devenv	PortBay
Free plan	Yes	Yes
Free trial	No	Yes
Paid from	Free	$4.92/mo
Open source	No	No
Platforms	Linux, macOS, Web, Windows	Linux, macOS
Free plan	Yes	Yes
Shell integration	Yes	—
Paid from	—	10 /mo

devenv vs PortBay

devenv

PortBay