devenv

devenv is a Nix-based way to define project development environments and the processes around them. It is best suited to teams that want the same code-defined setup in local work and CI. The main caveat is practical: Nix is required, and Intel Mac support has ended.

Overview

A project configuration can bring packages, languages, services, tasks, secrets, and tooling together, with dependency locking and configuration as code. That gives teams a shared description of what a project needs rather than a setup each contributor must assemble independently. Cached shell startup is under 100 ms after the first build; the first build is not covered by that speed claim.

devenv extends beyond shell initialization. It can define variables, files, and scripts for bash, zsh, fish, or nushell, build OCI containers from an environment, and run integration tests while its processes are active. GitHub Actions can use the same environment for checks, builds, and tests, which makes devenv a strong fit where local and CI setup should align.

Key features

• Languages and services: devenv lists 58 languages with version pinning and language server support, and 42 preconfigured services. PostgreSQL, Redis, MySQL, RabbitMQ, MinIO, Caddy, and Elasticsearch are among them. That breadth suits projects with several runtime or service dependencies, though the project still needs Nix.
• 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 development depends on a set of coordinated services or repeatable project tasks.
• Secrets: SecretSpec can retrieve declared secrets from sources including Keychain, 1Password, LastPass, dotenv, and environment variables. Teams can keep secret handling within the environment configuration without being restricted to a single source.
• Integrations and security: Integrations include direnv, GitHub CI, IntelliJ, VS Code, Zed, and an MCP server for AI assistants. Projects must be explicitly trusted before auto-activation, a safeguard against an untrusted project changing the shell.

Pricing

Free (MIT-licensed open source): free. The plan provides the open-source devenv tool and its environment, process, and CI capabilities. It requires Nix and works on Linux, macOS, and WSL. There are no seat counts, usage quotas, trial periods, or renewal terms attached to this plan.

devenv Cloud is in private beta with early-access sign-up. It is not a generally available paid plan, so teams choosing devenv today should assess the free local and CI workflow on its own merits rather than depend on Cloud access.

Platforms

devenv works on Linux, macOS, and WSL after Nix is installed. The broader platform listing includes web and Windows, but the installation requirements specify Linux, macOS, and WSL; Windows users should therefore expect to use WSL. The project no longer builds, tests, or releases devenv for Intel Macs as of version 2.4, a significant constraint for teams with that hardware. Cached shell startup under 100 ms applies after the first build.

Who it's for

devenv is a good choice for development teams that want reproducible environments, pinned dependencies, coordinated processes, and a route from local work to GitHub Actions and container-based integration tests. Its free MIT license and broad language and service coverage make it viable across varied project stacks. It is a poor fit for users unwilling to install or work with Nix, and not a sensible choice for teams that require current Intel Mac builds.

Pros and cons

• Pro: A project can define languages, packages, services, tasks, secrets, and shell tooling together, giving teams one configuration for substantial parts of their development setup.
• Pro: CI support, OCI container builds, and integration tests with active processes extend the environment beyond an individual developer's shell.
• Pro: The MIT-licensed tool is free, with no listed seat or usage caps.
• Con: Nix is a prerequisite, adding a required tool and workflow to adoption.
• Con: Intel Macs no longer receive builds, tests, or releases as of devenv 2.4.
• Con: Cloud remains in private beta, so it is not a broadly available hosted option.

Alternatives

Choose ActiveState Platform if its freemium model and free organization plan for public projects better suit the project; its paid organization option is custom pricing. Flox is another freemium option: its free Personal plan includes CLI and catalog access, unlimited public environments, and three private environments, making it worth considering when those hosted environment limits fit better.

Nix is the more direct choice for someone seeking the underlying open-source package manager rather than devenv's project environment layer. vfox is a free, Apache 2.0-licensed alternative for readers considering a different free tool. FlyEnv may suit local site and runtime workflows: its free plan includes three local sites and three custom projects per runtime, with a one-tunnel cap and three-day trials for some AI and media features.

mise is a free MIT-licensed CLI alternative for readers comparing environment-management tools. DDEV is a free, Apache 2.0-licensed option. DevPod is a free, open-source, extensible client-only alternative. Browse Development Environment Management Tools or Development Environment Managers for more options.

Verdict

Choose devenv if your team wants a free, code-defined environment that can coordinate languages, services, tasks, and CI around Nix. Its breadth and ability to carry the same setup into tests and builds are compelling; the decisive reasons to look elsewhere are the Nix requirement and the end of Intel Mac support.