mise

Name: mise
Brand: mise

Polyglot dev tool version manager, environment variable loader, and task runner in one CLI.

softwarePackage Managersversion-managerclidevtools

Our Verdict

Best for

Developers who want one tool to manage runtime versions, env vars, and project tasks instead of stitching together nvm, pyenv, and direnv.

Skip if

Your team has a stable, working asdf/nvm/direnv setup with no pain points worth migrating away from.

What is mise?

mise (formerly known as rtx) is an open-source command-line tool that manages development tool versions, project environment variables, and task running from a single mise.toml configuration file checked into a repository. It supports over 1000 tools including Node.js, Python, Ruby, Go, Rust, Java, Terraform, and kubectl, automatically switching versions as you move between project directories. Beyond version management, mise loads project-specific environment variables from its config, .env files, or shell commands, and lets teams define build, test, lint, and deploy tasks alongside their dependencies. It can activate via shims or by updating PATH directly, acting as a drop-in replacement for tools like asdf, nvm, pyenv, and direnv.

SpecificationsAI-estimated

deploymentSelf-hosted

open source✅ Yes

api available❌ No

support optionsCommunity support (GitHub, Discord)

key integrationsnpm, PyPI, GitHub releases, asdf plugins

Key Features of mise

Installs and pins exact versions of development tools per project, automatically switching versions when you change directories.

Supports a registry of 1000+ tools including Node.js, Python, Ruby, Go, Rust, Java, Terraform, and kubectl.

Loads project-specific environment variables from mise.toml, .env files, or shell command output.

Lets teams define build, test, lint, and deploy tasks with dependencies directly in configuration.

Offers two activation modes: shims that intercept commands, or mise activate which updates PATH in the shell session.

Provides mise exec to run a tool at a specific version one-off without permanently installing or activating it.

Uses a single mise.toml file checked into the repo so tool versions and environment setup stay consistent across machines.

Installs via a simple shell script with no separate runtime dependency required.

Use Cases for mise

Multi-language project onboarding

New contributors run one tool to get the exact pinned versions of Node, Python, Go, etc. that a project requires.

Replacing nvm/pyenv/rbenv

Consolidate separate per-language version managers into a single CLI and config file.

Project-scoped environment variables

Automatically load API keys, paths, or config values scoped to a project directory without manual shell exports.

Task automation with pinned tools

Define build/test/deploy tasks in mise.toml that always run with the correct tool versions and env vars loaded.

Pros & Cons of mise

Pros

Replaces multiple single-purpose version managers (nvm, pyenv, rbenv, etc.) with one consistent tool
Combines tool version management, environment variables, and task running in a single configuration file
Large registry of 1000+ supported tools across many language ecosystems
Free and open source with an active GitHub community

Cons

Teams already invested in asdf/nvm/direnv workflows must migrate configuration and habits to switch
Shim-based activation can add a small amount of shell startup overhead depending on setup
As a newer, fast-moving project (renamed from rtx), some plugins or docs across the ecosystem may lag behind the latest version

Frequently Asked Questions

Is mise free to use?

Yes, mise is free and open source under the MIT license.

What was mise previously called?

mise was previously named rtx before being renamed to mise (mise-en-place).

How is mise different from asdf?

mise is designed as a faster, more feature-complete alternative to asdf, adding built-in environment variable management and task running alongside tool version management.