mise

mise (short for “mise-en-place”) is a single Rust-built CLI that manages your dev tool versions, project environment variables, and tasks from one mise.toml file. We rate it 92/100 — if you have ever fought with asdf, nvm, pyenv, rbenv, direnv, and Make all at once, mise is the cleanest way out in 2026.

What is mise?

mise was created in 2022 by Jeff Dickey (originally under the name rtx) and is shipped as a single static Rust binary under the MIT License. The repository at github.com/jdx/mise has crossed 27,600 stars with 1,100+ forks, and the latest stable release v2026.5.0 shipped on May 3, 2026, graduating Conda support, smarter prerelease handling, and POSIX tasks on Windows.

The specific problem mise solves: every modern repo demands a different version of Node, Python, Go, Terraform, jq, kubectl, and a stack of .env files — and most teams stitch this together with asdf, nvm, pyenv, direnv, Make, and a brittle setup.sh. mise replaces all of that with one config (mise.toml), a Rust-compiled binary that runs without per-command bash shims, and a registry of nearly 950 tools as of 2026. It is a true drop-in replacement for asdf — it reads .tool-versions files unchanged and supports asdf plugins — while also bundling environment management and a task runner.

Key Features of mise

• Three jobs in one binary: install and switch dev tool versions, load per-project environment variables (including .env files and 1Password/AWS Secrets Manager directives), and run project tasks — all from a single mise.toml.
• PATH instead of shims: mise modifies PATH on shell activation rather than wrapping every command in a bash shim. asdf shims add roughly 120 ms of startup overhead per command; mise's activate hook removes it entirely.
• Drop-in asdf compatibility: mise reads existing .tool-versions files and can use asdf plugins. The migration path is two commands and your CI keeps working.
• Registry of ~950 tools: Node, Python, Ruby, Go, Rust, Java, Terraform, kubectl, jq, deno, bun, uv, awscli, gcloud, and 120+ tools added throughout 2025 alone.
• Tasks with depends and monorepo support: Define tasks in TOML or as standalone files in mise-tasks/. The October 2025 release added the :task namespace syntax and ... pattern matching for running tasks across packages in a monorepo.
• Lockfiles: mise.lock pins exact tool versions across machines and CI — the same idea Cargo and pnpm popularized, applied to every dev tool.
• Cross-platform, including Windows: Native support for macOS, Linux, and Windows. The 2026.5.0 release made POSIX tasks work cleanly on Windows, closing a long-standing gap.
• Editor integrations: Official VS Code extension, IntelliJ plugin, and shell completions for bash, zsh, fish, and PowerShell.

What Users Say About mise

The recurring praise across Hacker News, r/programming, and r/devops is that mise is “the asdf you wish you'd had in 2018.” The most-upvoted HN comment on the original launch thread called it a strict drop-in upgrade, and a 2026 Medium write-up by an engineering team reported that their monorepo's 5-second cd delay disappeared after switching, with CI failures dropping by 90% thanks to consistent versions across local and CI. On LibHunt, multiple reviewers say it has become their go-to for “tons of things” and is “just perfect.” The honest criticism is also consistent: mise will not reuse existing asdf install directories, so the migration costs you a re-download of every tool; the mise.toml format is opinionated and differs slightly from .tool-versions; and a few users on Reddit note that the registry, while huge, occasionally pins to a slightly stale upstream — usually fixed within a release. Production users include parts of Cloudflare, Shopify, Netflix teams, and a long tail of mid-sized startups standardizing onboarding on a single config file.

mise Pricing

mise is 100% free under the MIT License. There is no paid tier, no telemetry, and no signup required. Your only cost is the disk space for the tools you install.

Plan	Price	Key Limits
Open Source (everything)	$0	MIT license, unlimited use, full feature set
Self-hosted CI usage	$0	Single binary install, no license server
Commercial support	Not officially offered	Use GitHub Discussions for community help

Who Should Use mise?

Best for: polyglot teams who want one onboarding command instead of a wiki page; engineers tired of asdf's shim overhead; monorepo maintainers who need consistent tool versions plus a real task runner; and anyone who is currently combining asdf + direnv + Make and wants to delete two of those three.

Not ideal for: single-language shops perfectly happy with nvm alone (you don't need this); enterprises that require vendor-backed commercial support contracts; or teams locked into Nix or Devbox for hermetic, reproducible-by-hash environments — mise pins versions but is not bit-for-bit reproducible.

Pros and Cons

Pros:

• Single static Rust binary, no Bash dependency, install completes in seconds via curl https://mise.run | sh.
• Drop-in asdf replacement — reads .tool-versions, supports asdf plugins, no daily-workflow surprises.
• Combines version manager, environment loader, and task runner so you can delete direnv and most of your Makefile.
• Active maintenance — releases ship roughly every 1–2 weeks, latest is v2026.5.0 from May 2026.
• Excellent documentation at mise.jdx.dev with a full cookbook of recipes.

Cons:

• No reuse of existing asdf install dirs — first migration re-downloads every tool.
• No official commercial support; bug reports go through GitHub Discussions.
• Not hermetic like Nix or Devbox — reproducibility is by version, not by hash.
• The opinionated mise.toml format diverges slightly from asdf's .tool-versions; teams sometimes argue over which to commit.

Alternatives to mise

The closest direct competitor is asdf, the Bash-based original mise was inspired by; it has the largest plugin ecosystem but is meaningfully slower due to shims. proto by moonrepo is a newer Rust competitor with WASM-based plugins — cleaner sandboxing, smaller registry. Devbox and Nix chase a different goal: hermetic, fully reproducible environments at the cost of a steeper learning curve.

Verdict: Is mise Worth It?

Yes — for almost every developer who manages more than one language or more than one project. mise replaces asdf, direnv, and a chunk of your Makefile with a single fast Rust binary, and the migration takes about an afternoon. The only teams that should skip it are single-language shops happy with their existing language-specific manager, and organizations that strictly require hermetic builds. We rate mise 92/100 — the universal version manager to use in 2026.

Frequently Asked Questions

Is mise free?

Yes. mise is 100% free and open source under the MIT License. There is no paid tier and no telemetry.

What platforms does mise support?

macOS, Linux, and Windows. It ships as a single static Rust binary; the standard installer is curl https://mise.run | sh.

How does mise compare to asdf?

mise is a drop-in replacement: it reads the same .tool-versions files and supports asdf plugins, but it is written in Rust, modifies PATH instead of using shims (eliminating ~120 ms per command), and adds environment variables and a task runner that asdf does not have.

Is mise open source?

Yes — MIT-licensed on GitHub at jdx/mise.

Does mise replace direnv and Make?

For most projects, yes. mise loads .env files and per-project environment variables natively, and the task runner handles common build/test/deploy commands. Teams that need direnv's complex shell hooks or Make's pattern rules sometimes keep one alongside mise.