Devbox

Per project shells with Nix underneath and no Nix language to learn

Devbox gives each project a shell with its own pinned toolchain, declared in a devbox.json you commit next to the code. It is Nix underneath, which is where the reproducibility comes from and also where the surprises come from. The CLI is Apache licensed and, since August 2026, needs no account at all.

FreeApache-2.0GoSelf hostable

What you declare, and what it installs

You list packages in a devbox.json, run devbox shell, and get an environment with those exact versions on the path and nothing else leaking in from the host. It is the same promise a Dockerfile makes for local work, without a container runtime or an image to rebuild, because the shell is assembled from the Nix store rather than from layers.

The part worth reading twice is the first run. If Nix is not already on the machine, Devbox installs it for you, which means a two line config file commits every developer to a system level package manager and a /nix store. That is a reasonable trade for what you get back, but it is a bigger decision than the file size suggests.

The hosted features were removed, which cuts both ways

Release 0.18.0 in August 2026 deleted the Jetify Cloud integration from the CLI: the shared package cache, the secrets commands and the login flow all went, and the release notes say plainly that those features are being sunsetted. Teams that were leaning on the shared cache for speed lost it, and package lookups now go only to the public Nix cache.

The same change is why the tool is easier to recommend now. The CLI no longer talks to a vendor service, needs no token and has no account in the path, so the Apache licence is the whole story rather than the free half of one. It is a rare case of a company backed tool becoming less entangled with the company over time.

Reach for it when

you want a pinned toolchain per project without running Docker for local work
you maintain a polyglot repository currently held together by nvm, pyenv and rbenv
you want the reproducibility of Nix without writing Nix expressions

Watch out for

it installs Nix system wide on first run, so a small config file commits the machine to a package manager nobody chose explicitly
0.18.0 removed the Jetify cache, so lookups now hit only the public Nix cache and teams that relied on the shared one lost that speed
there is no native Windows build and cannot be one while Nix has none, so Windows means working inside WSL2
anything outside nixpkgs pushes you into Flakes, which is the Nix language this tool exists to spare you

NEXT TO IT ON THE SHELF

Devbox

What you declare, and what it installs

The hosted features were removed, which cuts both ways

Reach for it when

Watch out for

Compare with these

Omarchy

NixOS

Distrobox

Building something? Launch it on Machroui