vfox

Overview

vfox is a cross-platform manager for choosing development runtime and SDK versions. It is best suited to developers moving between projects with different version requirements, particularly teams that want to share those choices. Its project-aware switching is useful; the proxy restriction and limited CMD support narrow its fit.

Key features

Versions can be selected globally, for a session, or for an individual project, with automatic switching when you enter a project directory. This keeps a project on its required runtime without changing your machine-wide selection. Project versions can be recorded in .vfox.toml for teammates to share, while users can keep separate configuration and version selections even when they share installed SDK files.

Plugins extend support to runtimes and tools, and the public registry accepts community submissions. Documented examples include Bun, Clang, CMake, Crystal, Dart, Deno, and .NET. Plugins that support legacy files can read formats such as .node-version, .nvmrc, and .sdkmanrc; that compatibility is enabled by default, which helps projects retain existing version-file conventions.

For Docker, CI/CD, scripts, and other non-interactive environments, vfox exec runs commands in a managed SDK environment. This is the recommended route because shell activation hooks are intended for interactive shells. The documentation also demonstrates using the command in a VS Code task.

One constraint matters for network setups: vfox supports only HTTP(S) proxy protocols. Linux and macOS users sharing an SDK directory should use group permissions; broad, world-writable access can allow users to alter or delete other people's SDK files.

Pricing

vfox is free and open source under the Apache 2.0 License. The listed vfox plan costs nothing and includes runtime management, dependency locking, configuration as code, and shell integration. There are no paid tiers or seat and quota limits described in the plan, making it a straightforward choice for individual use or teams willing to manage their own setup.

Platforms

vfox supports Linux, macOS, and Windows. Documented shells include PowerShell, Git Bash, Bash, ZSH, Fish, CMD, Clink, Cmder, and Nushell. CMD is the exception: it supports global scope only and is not recommended, so users who need project or session scopes should choose another supported shell. Installation paths include Scoop, winget, or a setup installer on Windows, and Homebrew, package repositories, or an install script on Unix-like systems.

Who it's for

Choose vfox if your projects require different runtimes or SDK versions and you want automatic per-project selection, shareable configuration, or a plugin-based way to extend tool coverage. It also suits CI and container workflows when commands are run through vfox exec. It is a less suitable fit if your environment requires a proxy protocol beyond HTTP(S), or if CMD is your shell and you need more than global version selection.

Pros and cons

• Pros: Project, session, and global scopes give developers control over where version choices apply.
• Pros: Shared .vfox.toml settings and default legacy-file support can help teams coordinate without abandoning existing project conventions.
• Pros: The free Apache 2.0 license and community plugin registry provide a no-cost foundation that can be extended.
• Cons: CMD supports only global scope, limiting its usefulness for project-specific work.
• Cons: Only HTTP(S) proxies are supported, which can exclude environments using other proxy protocols.
• Cons: Non-interactive use calls for vfox exec rather than interactive shell activation hooks.

Alternatives

devenv is another free option for Linux, macOS, and Windows, but it requires Nix and also works on WSL. Consider it if that dependency fits your environment. Flox has a free Personal plan with CLI and Catalog access, unlimited public FloxHub environments, and three private environments; choose it if those environment limits and services better match your workflow. ActiveState Platform offers a free organization plan for public projects and a paid enterprise option with custom pricing, making it an alternative when that public-project model suits your needs. DDEV, Devilbox, DevPod, FlyEnv, and Lando are also options to compare.

Browse Development Environment Management Tools and Development Environment Managers for more options.

Verdict

Choose vfox for free, cross-platform runtime management when per-project version switching, shareable configuration, and extensible plugin support are the priorities. Its clearest reasons to look elsewhere are the HTTP(S)-only proxy support and CMD's global-only scope.