Flox

Overview

Flox is a tool for defining and sharing reproducible software environments across development workflows. It suits developers and teams that want project setup managed as code, with a free individual tier and paid collaboration options.

Its strongest case is the combination of a large Nixpkgs-based catalog, environment sharing, and integrations for editors and CI. The trade-off is that private resources are capped on the free plan, and teams pay per seat for expanded collaboration.

Key features

Environments managed as code

Each environment can specify project packages, variables, and shell hooks, so setup can be treated as part of the project rather than recreated manually. Flox also supports runtime management, dependency locking, shell integration, and containers. That breadth makes it relevant to teams seeking repeatable development setups, though it is more than a simple package installer.

Catalog and sharing

The Flox Catalog is powered by Nixpkgs and contains more than 190,000 packages. FloxHub lets users sync, share, and manage environments, with package lists, earlier versions, and change logs. Those history and sharing features help collaborators understand how an environment has changed; the free Personal plan, however, allows only three private environments and five private packages.

Workflow integrations

GitHub Actions can install Flox and activate environments in CI workflows. The VS Code extension supports package management, environment activation, and running services, and is also compatible with Cursor. Flox Skills are designed to help Claude Code, Codex, and skills.sh agents create environments, services, and builds, as well as onboard repositories. These integrations make Flox a stronger fit for teams that want environment setup to reach beyond the local shell.

Security and enterprise controls

Flox says its environments include a signed, hash-pinned software bill of materials and build provenance. The company states that it holds SOC 2 Type II and ISO/IEC 27001:2022 certifications, with related documentation available to prospects on request. Enterprise capabilities include SSO, role-based access controls, private distribution including air-gapped use, audit lineage, and SLA-backed support. That makes the enterprise tier relevant to organizations with governance or deployment constraints, but its custom pricing requires a sales conversation.

Pricing

Personal is a capable starting point for an individual or public project, but its private-environment and package caps matter as soon as work needs to remain private. Team removes those stated FloxHub and publishing limits and adds platform support, at $20/seat/month; the per-seat term makes the total rise with team size. Enterprise is for organizations that need tailored deployment, catalog, or policy controls, and its price is custom.

Platforms

Flox lists extension, Linux, macOS, self-hosted, web, and Windows platforms. Its environments are presented as working across macOS, Linux, and WSL2.

Who it's for

Flox is best suited to developers who want a project environment described in code and reused across machines, and to teams that need shared environments, package publishing, and CI or editor integration. Enterprise controls may suit organizations with identity, audit, or air-gapped deployment requirements. It is less compelling for an individual whose needs fit a basic free environment manager, or for a team unwilling to pay per seat for private collaboration.

Pros and cons

• Pro: Environments capture packages, variables, and shell hooks as code, supporting repeatable project setup.
• Pro: FloxHub provides sharing and change history, while Team adds unlimited team environments and package publishing.
• Pro: GitHub Actions, VS Code, Cursor, and AI coding tool integrations extend environment workflows beyond the CLI.
• Con: Personal limits private FloxHub use to three environments and five packages, which can constrain private projects.
• Con: Team is priced per seat at $20/seat/month, so collaboration has a recurring cost that scales with team size.
• Con: Enterprise requires custom pricing, making it less straightforward to budget.

Alternatives

For a focused comparison, see Development Environment Management Tools and Development Environment Managers.

• devenv is a free option for Linux, macOS, and WSL, but requires Nix; choose it if those platforms and that requirement suit your setup.
• DevPod is a free, 100% open-source and extensible client-only option; choose it if open-source client tooling is the priority.
• Nix is a free, open-source package manager with no paid plan; choose it if you want the package manager itself rather than Flox's paid team features.
• mise is a free, MIT-licensed open-source CLI for macOS, Linux, and Windows; choose it if a free CLI is the fit.
• FlyEnv offers a free tier with limits including three local sites, three custom projects per runtime, and one Cloudflare Tunnel; its AI, Screenshot, and Image Optimization features have three-day trials.
• ActiveState Platform has a free organization plan for public projects and a paid enterprise organization plan with contact-sales pricing; choose it if public-project use fits its free tier.
• DDEV is free and open source under Apache 2.0; choose it if that is the environment manager you want.
• Devbox is an open-source project with a free first month on its $5 a month Solo plan; consider it if that plan and its listed platforms suit your needs.

Verdict

Choose Flox if you want project environments managed as code and need sharing, history, CI, and editor integrations in the same workflow. Its free Personal tier is useful for trying the approach, but private-resource caps are a real boundary; teams should choose it when unlimited shared environments and platform support justify $20/seat/month. Look elsewhere if you need only a free, open-source tool or do not need Flox's collaboration layer.