For Platform Engineers

Reproducible at Scale

Eliminate environment fragmentation across your organization. Centralized control, complete traceability, and instant developer onboarding.

From Zero to Hero with Flox

Day 1

Foundation

Establish baseline environments and organizational standards.

Week 1-2

Team Adoption

Roll out to pilot teams, integrate with CI/CD, prove the value.

Week 3+

Organization Scale

Scale across the org, handle incidents faster, maintain compliance with confidence.

Day 1

Create Baseline Environments

You define environments for your company's three main stacks: Node/React, Python/Django, and Go microservices. Each baseline environment includes approved tools, scripts, and environment variables. Push to FloxHub. Teams can now start with best practices instead of reinventing the wheel.

Week 1

CI/CD Integration

Your Docker image builds take 8 minutes and break randomly. You replace them with Flox environments: same manifest devs use locally, instant activation in CI. Pipeline time drops to 45 seconds. 'Works on my machine' becomes 'works everywhere.' Developers stop filing tickets about CI flakiness.

Week 2

Scale to Multiple Teams

Frontend team needs a custom Tailwind build. Backend needs specific Postgres extensions. Data science wants CUDA. Each team pulls your baseline environment and layers on what they need. You see everything from FloxHub: which generations are live, full dependency trees. No tool sprawl, no mystery configurations.

Week 3

Respond to a Security Incident

There's a critical vulnerability in a Node package. You upgrade the affected package in your baseline environment and push it to FloxHub. Teams pull the update. Vulnerability patched across the org in 2 hours instead of 2 weeks. Security team asks 'how did you move that fast?'

Month 2

Compliance Audit

Auditor asks: 'Can you prove what's running in production?' You show them: hash-pinned dependencies from dev to prod and SBOMs for every environment. They're impressed. Compliance that doesn't slow down development—finally.

How It Works

1. Create Org Environments

Define the base set of tools for your organization. This becomes the foundation for project development.

# Create an org-wide base environment
flox init -d base-env
flox install -d base-env git awscli vscode

# Push to your organization's FloxHub
flox push -d base-env -o your-org

2. Teams Extend and Customize

Teams activate the base environment and layer on the dependencies for their project. Organizational standards stay enforced, teams get flexibility.

# Activate base environment
flox activate -r your-org/base-env

# Project setup
git clone https://github.com/your-org/project.git
flox activate -d project -- code project

3. Integrate With CI/CD

Use the same Flox environments in CI as developers use locally. Eliminate environment mismatches and speed up pipelines.

# GitHub Actions example
- name: Setup Flox
  uses: flox/activate@v1
  with:
    environment: your-org/base-env

- name: Run tests
  run: |
    flox activate -- npm test

4. Monitor and Update Centrally

Track usage, enforce policies, and roll out updates from FloxHub. Complete visibility into what every team is running.

# View all environments
flox envs

# Update an environment
flox edit -d base-env
flox push -d base-env

# Teams get updates the next time they activate the environment
flox activate -r your-org/base-env