frum

frum is a focused Ruby version manager for developers who need different interpreters across projects and a dependable machine-wide default. It is best suited to Ruby-only workflows that value lightweight shell integration and configurable builds over a broader environment platform. Its free, MIT-licensed distribution removes purchasing friction, but Windows users should confirm that the project’s current support fits their setup.

Overview

frum handles the practical version-management cycle: installing and uninstalling Ruby versions, listing available or installed versions, and selecting either a local or global version. A .ruby-version file pins a repository to its required interpreter, while a global setting supplies the default elsewhere. Automatic switching is valuable when moving between repositories because the project choice can change with the directory rather than requiring repeated manual commands.

The implementation is pure Rust and does not use ruby-build. That gives frum a narrow, Ruby-specific remit instead of the wider package and environment responsibilities of a general development platform. The project reports that evaluating frum init runs about six times faster than evaluating rbenv init - in its benchmark. That points to potentially lighter shell initialization, not a guarantee that Ruby compilation or application execution will be six times faster.

Key features

Project and global version control

Local pinning and a separate global choice cover the two settings most Ruby developers need. Automatic switching reduces context changes between repositories, and the same command set supports installing, removing, listing, and selecting versions. This is a coherent workflow for teams that standardize on .ruby-version files; it is less compelling if you need one manager to coordinate several programming languages.

Build configuration

frum install accepts Ruby build options including an OpenSSL directory and jemalloc selection. Those controls matter when a system’s OpenSSL location or allocator choice affects a build, giving experienced users a way to adapt compilation rather than accepting one fixed configuration. They also make installations more involved for readers who simply want a default Ruby with no build decisions.

Shell integration and completion

The README provides initialization instructions for Bash, Zsh, and Fish, and lists auto-completion as a feature. Support for these common shells makes the manager practical in interactive terminals and reduces command-entry friction. The reported initialization benchmark further favors users who pay attention to shell startup overhead, although it remains a project benchmark rather than a universal performance result.

Installation and distribution

Installation paths include Homebrew or Linuxbrew, Arch Linux packages, Cargo, and release binaries. Release binaries are linked for Linux and macOS, which can be convenient when you do not want to build from source. The range of methods suits both package-managed machines and Rust-oriented users, though choosing among them adds an initial setup decision.

Pricing

Plan	Price	Includes
frum	free	Ruby version manager; MIT licensed

There is no paid tier or free trial. The single free plan is the right fit for individual developers, teams adopting an open-source utility, and anyone who needs project pinning without a subscription. It provides no separate commercial service tier or paid support option in the stated plan structure, so organizations wanting contractual service terms should look elsewhere.

Platforms

frum targets Linux, macOS, and Windows. The README documents macOS and Linux as supported platforms and mentions Windows in its goals, so the Unix-like platforms have the clearest documented path. Bash, Zsh, and Fish setup instructions make shell integration strongest for users in those environments; Windows adopters should validate the current workflow before standardizing on it.

Who it's for

Choose frum if you work primarily in Ruby, switch between repositories with different interpreter requirements, and want both automatic project selection and a global fallback. It also suits users who prefer a Rust implementation, MIT licensing, and several installation routes, or who need OpenSSL and jemalloc controls during Ruby installation.

It is not the natural choice for a multi-language toolchain, a hosted development environment, or a buyer seeking paid plans and formal service terms. Windows teams should be especially deliberate because documented support is clearer for macOS and Linux.

Pros and cons

Pros

• Clear Ruby focus: local and global selection, automatic switching, and .ruby-version support address everyday Ruby project workflows.
• Configurable installations: OpenSSL-directory and jemalloc options help accommodate non-default build environments.
• Flexible setup: Homebrew, Arch packages, Cargo, and release binaries provide multiple installation routes.
• Shell-friendly: Bash, Zsh, Fish, and auto-completion support reduce terminal setup friction.
• No licensing cost: the only plan is free and MIT licensed.

Cons

• Narrow scope: frum manages Ruby rather than serving as a general multi-language environment manager.
• Windows uncertainty: Windows appears in the project goals, while the documented supported platforms emphasize macOS and Linux.
• Build complexity for newcomers: configurable compilation is useful but can require decisions about system libraries and allocators.
• No paid service tier: organizations needing commercial support or contractual terms have no stated plan to select.

Alternatives

GHCup is the better pick for free Haskell toolchain installation and management across Linux, macOS, Windows, self-hosted, and web environments. Choose ActiveState Platform when you need a freemium platform with public projects on its free organization plan and a paid enterprise option. devenv fits users wanting MIT-licensed, multi-platform environment management who can work with Nix. Pick FVM for open-source Flutter SDK version management instead of Ruby. Flox is a broader freemium environment choice with a free CLI, catalog access, public environments, and limited private environments. Jabba is the focused alternative for Java version management. Nix suits users seeking an open-source package manager rather than a Ruby-only manager. Choose nvm when your version-management need is Node.js.

Verdict

frum is a strong choice for Ruby developers who want project-file pinning, automatic switching, shell integration, and configurable installations at no cost. Its main reason to choose it is a compact, Rust-based workflow that stays centered on Ruby. Look elsewhere if you need a multi-language environment platform, clearer documented Windows support, or paid organizational service.