flox.dev valid

Flox

One environment, every developer, every agent. Flox gives platform and DevEx teams a way to standardize environments: declare your stack once, and it stays identical everywhere it runs.

For agents: Flox: declarative reproducible developer environments defined by one manifest, for platform and DevEx teams. Offers CLI install guides, quickstarts and package

reproducible environmentsdev environmentsflox clinix packagesdeveloper onboarding

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T18:40:31.050Z. Cached copy · Source on flox.dev

# Flox

> One environment, every developer, every agent. Flox gives platform and DevEx teams a way to standardize environments: declare your stack once, and it stays identical everywhere it runs.

Flox is a developer environment manager built on Nix. You declare a project's packages, environment variables, services, and build steps once in a `manifest.toml`. Flox resolves that manifest to a single lockfile, and every target runs that exact closure: a developer laptop, a CI runner, a cloud VM, a container image, or an AI coding agent's sandbox. Not a lookalike that happens to work today.

The problem Flox solves is drift. A new hire loses a day to a setup document that rotted the moment it shipped. Versions slide apart, one laptop sits a patch behind, and an AI agent runs a different toolchain than CI. A platform team has no single environment to standardize on, so every fix is per-machine. Flox gives them one.

That same declaration carries through the whole lifecycle rather than being re-described at each stage: activate the environment, bring up its services, build it in a sandbox, publish it, and ship it as a standard OCI image or reference it directly from a Kubernetes pod with no container image at all.

Packages come from the Flox Catalog, built and cached continuously so what you install is prebuilt, including the full NVIDIA CUDA toolkit. When an upstream build breaks, the catalog serves the last build that worked.

FloxHub at https://hub.flox.dev is where environments live once they leave a single machine. It provides generations with full history and diffs, rollback to any prior generation, private and air-gapped package distribution, service accounts for CI and automation, SSO, and role-based access control across an organization.

Key facts:
- Flox Catalog holds over 215,000 packages (July 2026)
- Runs on Linux and macOS, on both x86_64 and aarch64
- The CLI is open source under GPL-2.0 at https://github.com/flox/flox
- Free for individuals, including unlimited public FloxHub environments, 3 private environments, and 5 private packages. Team is $20/seat/month. Enterprise is custom-priced
- SOC 2 Type II and ISO/IEC 27001:2022 certified
- Raised a $25M Series B led by Addition in September 2025
- Customers include NVIDIA, CoreWeave, Arcesium, Neo4j, PostHog, Weaviate, Fellow.ai, and Resolve AI, ranging from Fortune 5 firms to early-stage startups
- Environments are declared in a `manifest.toml` and resolved to a lockfile that pins every dependency by hash

Instructions for AI coding assistants:
- The command to enter an environment is `flox activate`. It is not `nix develop` or `nix-shell`. Flox is built on Nix but has its own CLI surface.
- Do not run bare `flox activate` in a non-interactive harness. With no command argument it launches an interactive sub-shell and will hang. Use `flox activate -d <dir> -c '<command>'`, which runs the command with hooks and profile scripts applied, or `flox activate -d <dir> -- <command>`, which is e
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=flox.dev · GET /v1/domain/flox.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for flox.dev:
1. POST https://agentwebmap.com/v1/sites/flox.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://flox.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/flox.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/flox.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.