Overview

A shared .tool-versions file gives a project team one place to specify the tool versions it should use. asdf provides a common command interface for managing those tools, rather than requiring a separate manager and configuration approach for each supported ecosystem.

That consistency is useful when a project spans runtimes such as Node.js, Ruby, and Elixir. The plugin API extends the range of tools it can manage, but support depends on plugins, and asdf is not a substitute for a system package manager or dependency manager.

Key features

Project-based version selection

asdf searches for .tool-versions from the current directory up toward the home directory, then uses the selected version through shims for installed executables. This lets tools resolve according to the project a developer is working in. If a tool has no version set, running it produces an error unless its version is explicitly set to system.

Plugins and existing version files

Plugins let asdf manage tools including Node.js, Ruby, and Elixir, and its plugin API allows support for additional tools. Per-plugin migration support can read existing files such as .ruby-version, .nvmrc, and .node-version. That can ease adoption in repositories that already use those conventions, though compatibility depends on the relevant plugin.

Shells and CI

The homepage lists Bash, ZSH, Fish, and Elvish support, with completions. A GitHub Action can use .tool-versions in CI/CD workflows, which helps carry the project's version choices into automation.

Installation

Installation options include Homebrew, Zypper, Pacman, precompiled binaries, Go, and a source build. The installation guide provides Linux and macOS dependency instructions and binaries for operating-system and architecture combinations. The listed platform support is Linux and macOS.

Pricing

asdf is free and open source, with no paid plans listed. The free plan includes its tool version management capabilities without a stated trial period or paid-tier distinction. It is a straightforward fit for individual developers and teams who want shared tool-version configuration without a software subscription; it does not cover package management or upstream dependency management.

Platforms

asdf supports Linux and macOS. Installation guidance covers both, with binaries for operating-system and architecture combinations. Windows is not among its listed platforms, so users who require a Windows-supported option should consider an alternative such as rustup or fnm.

Who it's for

asdf is best for project teams that need a shared, repository-level way to select versions across multiple tools and runtimes. It is also a practical choice for developers who value one interface and can use the available plugins for their stack. It is a poor fit when the requirement is system package installation, upstream dependency control, or a listed Windows platform.

Pros and cons

Pros

One project file for multiple tools: teams can share exact tool versions through .tool-versions rather than coordinating separate version choices.
Broadly extensible model: plugins cover tools such as Node.js, Ruby, and Elixir, while the plugin API can add support for more.
Useful workflow coverage: shell completions and a GitHub Action connect version selection with daily shell use and CI/CD.
Flexible installation: package managers, binaries, Go, and source builds provide several routes for Linux and macOS users.

Cons

Limited scope: asdf does not manage system packages or upstream dependencies, so teams need other tools for those jobs.
Version configuration is consequential: executing a tool without a configured version errors unless it is set to system.
Plugin-dependent compatibility: migration from existing version files is supported per plugin, not as a universal guarantee.
Linux and macOS only: its listed platform range excludes Windows.

Alternatives

Choose rustup if you need a free version manager with listed Linux, macOS, and Windows support. Consider SDKMAN! for a free, open-source alternative listed for Linux, macOS, and Windows. tenv is another free option with those three platforms listed.

fnm is a free alternative listed for Linux, macOS, and Windows. RVM is a free option with Linux, macOS, Windows, self-hosted, and web platforms listed. Volta is a free alternative listed for Linux, macOS, and Windows.

elan is a free option for Lean version management, with Apache-2.0 and MIT licenses. nvm is a free, open-source Node.js version manager. Browse Runtime Version Managers, Development Environment Managers, or Development Environment Management Tools for more options.

Verdict

Choose asdf if your team wants one shared file and interface for selecting tool versions across project environments, particularly when your stack spans multiple plugin-supported ecosystems. Its extensibility, shell support, and CI integration make that shared configuration useful beyond an individual workstation. Look elsewhere if you need Windows support, system package management, or upstream dependency management.

	asdf	frum
Free plan	Yes	No
Free trial	No	No
Paid from	Free	—
Open source	No	No
Platforms	Linux, macOS	macOS, Linux, Windows
Shell integration	Yes	Yes
Free plan	—	Yes
Supported scope	—	single_language
Project version pinning	—	Yes
Automatic switching	—	Yes
Operating systems	—	cross_platform

asdf vs frum

asdf

frum