The pitch

How to open, what to ask, and what each person in the room cares about, for Flox. Sales framing on this page is advice, marked “Say:” or “Ask:”, and the fact underneath each line is cited to a Flox page checked 2026-11-04. Flox’s published proof is two named customer stories and a set of scenarios, all qualitative, so the pitch leans on mechanism and on the customer’s own numbers. Where a source stops short, the line says [verify].

This page is drawn from https://flox.dev/docs/flox-5-minutes, https://flox.dev/docs/concepts/flox-vs-containers, https://flox.dev/control-your-sdlc/, https://flox.dev/pricing/, https://flox.dev/case-studies/how-fellow-ai-ships-faster-with-flox/, https://flox.dev/case-studies/how-resolve-ai-eliminated-works-on-my-machine/, https://flox.dev/kubernetes/, https://flox.dev/cve-remediation/, https://flox.dev/deterministic-agents/, https://flox.dev/blog/flox-catalog-login-requirement-what-you-need-to-know/ and https://flox.dev/compliance/ (all checked 2026-11-04).

The one-liner

Flox makes the whole environment a file in the repo, so the same pinned toolchain runs on every laptop, in CI and in production, without anyone learning Nix.

• Flox is “a language agnostic package and environment manager that lets you create reproducible environments that work across machines, architectures, and operating systems” (https://flox.dev/docs/flox-5-minutes).
• Flox pins “the whole environment, down to the transitive dependency, identically on every laptop, in CI, and in production” (https://flox.dev/control-your-sdlc/).
• Users define environments in human-readable TOML, and commands like flox init, flox install, flox search and flox activate are meant to feel familiar to anyone who knows git, npm or pip (https://flox.dev/case-studies/how-resolve-ai-eliminated-works-on-my-machine/).

The 30-second version

Say: “Your team loses time because everyone’s machine is slightly different. Flox puts the packages, variables, services and setup steps in one manifest that lives in the repo. A new engineer clones and runs flox activate. CI runs the same environment, and you can export it as a container image or run it on Kubernetes without building images. It is free to start, and a team plan is $20 per seat per month.”

Backing for each claim:

• “To get started on any project with Flox, all you need is git clone and flox activate” (https://flox.dev/docs/flox-5-minutes).
• An environment can hold packages, environment variables, setup scripts and services (https://flox.dev/docs/imageless-kubernetes/tech).
• Flox can export an environment as a container image with flox containerize (https://flox.dev/docs/man/flox-containerize).
• The Free plan includes the CLI, Catalog access and unlimited public FloxHub envs, and Team is $20/seat/month (https://flox.dev/pricing/).

The two-minute version

1. Packaging is separate from isolation. The docs say Flox “believes that software packaging should be distinct from the chosen type of isolation”, and that Flox environments work on bare metal, in VMs, in containers and in agent sandboxes (https://flox.dev/docs/concepts/flox-vs-containers).
2. No walled-off laptop. Flox environments run as subshells, not containers, so developers work directly on their local systems (https://flox.dev/kubernetes/). Resolve AI cites this as a reason it chose Flox over dev containers and cloud dev shells (https://flox.dev/case-studies/how-resolve-ai-eliminated-works-on-my-machine/).
3. The environment travels with the code. Fellow.ai co-locates environments with its GitHub repositories so “each project’s runtime dependencies lived (and traveled) with its code” (https://flox.dev/case-studies/how-fellow-ai-ships-faster-with-flox/).
4. Same environment, three stages. Local dev, CI and production share one hash-pinned baseline (https://flox.dev/control-your-sdlc/). In Kubernetes, pods name a FloxHub environment instead of an image (https://flox.dev/docs/imageless-kubernetes/intro).
5. Security and audit as a side effect. Every Flox environment is described as hash-pinned with a deterministic SBOM (https://flox.dev/cve-remediation/). Flox itself reports SOC 2 Type II and ISO/IEC 27001:2022 certifications (https://flox.dev/compliance/).
6. Agents get a stable floor. Flox’s agent page pins one manifest under any harness and shows flox activate -- claude (https://flox.dev/deterministic-agents/).

Be upfront about one change: since 2026-10-20, install, upgrade and resolve need a free FloxHub account, while flox search, flox show and activating an environment with a valid lockfile stay public (https://flox.dev/blog/flox-catalog-login-requirement-what-you-need-to-know/).

Discovery questions

Ask these before you pitch.

Value by person in the room

Developer. Lead with no new mental model. Fellow.ai’s CTO says Flox “was transparent for our team”, with no new tools or language to learn (https://flox.dev/case-studies/how-fellow-ai-ships-faster-with-flox/). flox services start runs the databases and workers an environment defines, and services stop when the environment exits (https://flox.dev/docs/flox-5-minutes).

Platform or DevEx lead. Lead with the contract. Flox’s platform post says a README “can describe setup, but it cannot enforce setup” (https://flox.dev/blog/works-on-my-machine-a-platform-problem/). Ask for the hours they lose today; do not quote a figure, because Flox publishes none (https://flox.dev/control-your-sdlc/). Team adds a team catalog, unlimited team FloxHub envs and platform support (https://flox.dev/pricing/).

Security lead. Lead with deterministic SBOMs and rebuild-and-ship CVE response: “Detect what is affected, rebuild from a pinned manifest, and roll forward or back in one step” (https://flox.dev/cve-remediation/). Enterprise lists a software policy engine and a custom base catalog, with no price shown (https://flox.dev/pricing/). Do not promise audit outcomes; the compliance page describes Flox’s own certifications, not the customer’s (https://flox.dev/compliance/).

ML or AI engineer. Lead with CUDA time. A prebuilt CUDA PyTorch wheel “takes 1m and 11s” to download versus more than 65 minutes to build on a 32-core machine (https://flox.dev/blog/deploying-hardened-flox-nvidia-cuda-stacks-in-minutes-not-hours/). The CUDA page also says several CUDA versions can sit side by side and be switched by activating different environments (https://flox.dev/cuda/). Note the open conflict on whether that service needs authentication [verify] (https://flox.dev/cuda/).

Agent builder. Lead with the claim “The harness is probabilistic by design. The environment under it should not be.” (https://flox.dev/deterministic-agents/). Agents can be given the flox, floxify and flox-debug skills so they can find and install their own dependencies (https://flox.dev/blog/a-turnkey-toolkit-for-agentic-development-with-flox/). Offline sandboxes need the packages present locally, because “Authentication tokens cannot substitute for network connectivity” (https://flox.dev/blog/flox-catalog-login-requirement-what-you-need-to-know/).

Proof points from case studies

• Fellow.ai (11 May 2026): replaced a patchwork of developer-specific setups, and the case study says Flox “did essentially eliminate drift in local development” while not completely solving the problem (https://flox.dev/case-studies/how-fellow-ai-ships-faster-with-flox/). It is exploring OCI images and imageless Kubernetes next (https://flox.dev/case-studies/how-fellow-ai-ships-faster-with-flox/).
• Resolve AI (1 June 2026): adoption was phased, starting with engineers open to trying it, and works-on-my-machine issues turned into “are you using Flox?” (https://flox.dev/case-studies/how-resolve-ai-eliminated-works-on-my-machine/). It admits some engineers still avoided direnv auto-activation after rebases (https://flox.dev/case-studies/how-resolve-ai-eliminated-works-on-my-machine/).
• Neither study publishes a percentage or hour count. Say so if asked, and ask the customer for their own (https://flox.dev/case-studies/).

Proof-of-value ask

Ask: “Pick one repo that hurts the most to set up. Give us a week. We Floxify it, push the environment to a shared place, and measure two things you choose: time for a new person to run the tests, and the number of environment questions in your team channel.”

• Floxifying a repo is flox init, then installs, then flox activate; the POC page has the exact commands (https://flox.dev/docs/man/flox-init).
• A free FloxHub account is enough to start (https://flox.dev/pricing/). The Free plan lists 3 private FloxHub envs, while Team lists unlimited team FloxHub envs (https://flox.dev/pricing/).
• Agree success criteria and a time-box up front, and name who signs off. Pricing for more than a pilot is a conversation: Team is $20/seat/month, Enterprise is custom (https://flox.dev/pricing/).

When not to push

• If the customer already has a working dev-container or Nix setup that nobody complains about, say so. Resolve AI named dev containers, cloud dev shells and open source Nix as alternatives it weighed (https://flox.dev/case-studies/how-resolve-ai-eliminated-works-on-my-machine/).
• If they only need one language’s version pinning, a language-specific manager may be enough. Flox’s own post says those tools “solve part of the problem within one ecosystem” (https://flox.dev/blog/works-on-my-machine-a-platform-problem/).
• If their CI cannot hold a FloxHub token and resolves packages on every run, resolve the login question first (https://flox.dev/blog/flox-catalog-login-requirement-what-you-need-to-know/).