nixfredFLOXFIELD GUIDE · BY NIX UNOFFICIAL
ObjectionsSecurityFAQGlossaryBlog digestWhat is FloxNix 101ArchitectureAgentsEnterpriseUnofficial. Not affiliated with Flox.
HOW TO EXPLAIN, COMPARE AND WIN WITH FLOX · UNOFFICIAL FIELD GUIDE · BY NIX

One manifest. One lockfile.
The same environment on every laptop, runner and cluster.
Know how to make it succeed.

An independent guide to Flox, the environment manager built on Nix: the pitch, objection handling, a competitor question-and-answer bank, a support playbook, security and login-gate notes, head-to-head comparisons with Docker, Dev Containers, Nix, Devbox, devenv, mise, conda, Homebrew and Bazel, economics, whiteboards, scenarios, a POC playbook, a CLI cheat sheet, a digest of every flox.dev blog post, a quiz, an MCP server and a help chat. Flox facts come from its own docs, blog and pages and competitor facts from each project's public page, with a source on every claim.

Sources for this headline: an environment is declared in a manifest and resolved to a lockfile (environments); the same environment can be activated locally, containerized, or referenced from Kubernetes (flox.dev/llms.txt).

Start with the pitch →Competitor Q&ACompetitiveObjectionsSupport playbookSecurityWhiteboardsCalculatorPOC scriptsCLI cheat sheet
$20Team per seat / month
110docs pages indexed
92blog posts digested
2026-11-04sources checked

WHITEBOARDS

BOARD

new hire to first commit

A laptop, a repo, one command, an identical environment

BOARD

laptop, CI and container

One manifest feeding a laptop, a CI runner and an OCI image

BOARD

imageless Kubernetes

A pod that references an environment instead of an image

BOARD

agent sandbox

An agent that gets the same toolchain as the team

EXECUTE

EXECUTE

The pitch

One-liner, 30-second and 2-minute versions, discovery, value by persona

EXECUTE

Objection handling

Nix is hard, we use Docker, price, lock-in, login, each with a source

EXECUTE

Support playbook

Triage, the first five questions, common failures and the docs that fix them

EXECUTE

Security, login gate and reliability

SBOMs, CVE response, supply chain, the Oct 2026 login requirement, what to say about gaps

EXECUTE

Economics

What Flox charges, worked examples, a seat-cost versus drift-cost calculator

EXECUTE

Competitive positioning

Docker, Dev Containers, Nix, Devbox, devenv, mise, conda, pixi, uv, Homebrew, Bazel and more

EXECUTE

Competitor questions and answers

The questions customers actually ask about the alternatives, answered with sources

EXECUTE

Scenarios and reference architectures

Six customer situations, what to ask, the Flox answer, the honest risk

EXECUTE

POC and demo scripts

Five demos, success criteria, close-out

LEARN

LEARN

What Flox is

30-second and 2-minute versions, who it is for, vocabulary

LEARN

Nix 101 for Flox people

Store paths, closures, derivations, flakes, and what Flox adds on top

LEARN

The architecture

Manifest, lockfile, catalog, activation, FloxHub, the CLI itself

LEARN

Environments and the manifest

Path, managed and remote environments, every manifest section, layering and composition

LEARN

The Catalog, builds and publishing

Search, versions, package groups, CUDA, flox build and flox publish

LEARN

CLI, services, CI and tokens

Everyday commands, services, auto-activation, CI, FloxHub tokens, generations

LEARN

Languages and tools

Python, Node, Go, Rust, Ruby, editors, direnv, secrets, cloud, GPU and ML

LEARN

Containers and Kubernetes

flox containerize, Flox versus containers, imageless Kubernetes

LEARN

Agents and skills

The flox, floxify and flox-debug skills, sandboxes, deterministic agents

LEARN

FloxHub, orgs, plans, compliance

FloxHub, organizations, SSO, pricing tiers, SOC 2 and ISO 27001

LEARN

The company and the Nix world

Where Flox came from, funding, customers, how it sits in the Nix community

REFERENCE

REFERENCE

CLI cheat sheet

Every flox command grouped like --help, with flags, examples and safe forms for scripts and agents

REFERENCE

FAQ quickfire

One-line answers with sources

REFERENCE

Glossary

Terms to use correctly

REFERENCE

Sources

Every Flox and competitor URL, date checked

REFERENCE

Flox blog digest

Every flox.dev/blog post with the one fact worth repeating and when to use it with a customer

REFERENCE

Quiz and flashcards

Check yourself before the call

MCP SERVER

Use this guide in your agent

Read-only tools over Flox docs and this guide

MODEL CONTEXT PROTOCOL

Put Flox's docs in your own agent.

A read-only MCP server that fetches Flox's docs live from llms.txt, plus this guide's pages.

claude mcp add --transport http flox-field-guide https://flox.nixfred.com/mcp

All clients and tools →

Index

This is an unofficial field guide to Flox, the developer environment manager built on Nix. An environment is declared in a manifest, resolved to a lockfile, and then activated on a laptop, a CI runner, a container or a Kubernetes pod (https://flox.dev/llms.txt). Start with what Flox is, then Nix 101, the architecture, environments and the manifest, the Catalog, containers and Kubernetes, agents, economics, competitive positioning, the competitor Q and A, the POC playbook, the quiz and the blog digest.

Flox facts come first from its documentation (https://flox.dev/docs/), its blog (https://flox.dev/blog/) and its live product pages (https://flox.dev/pricing/, https://flox.dev/compliance/). Competitor facts come from each project’s own public pages. Everything was checked 2026-11-04 and is listed on Sources. Where a claim could not be settled, the page marks it with a [verify] badge. This guide is not written, reviewed or endorsed by Flox.

Use the help chat at the bottom right of any page, or the MCP server, to search the guide, the Flox docs and the Flox blog from your own tools.