Flox

Flox

@flox.dev

https://flox.dev https://github.com/flox/flox flox init flox install <package> flox activate git add .flox/ git commit -m 'add repeatable dev environment' git push

286 followers17 following456 posts

Welcome to Julian Dunn, who joins Flox's product team! Julian brings years of developer tools product leadership from GitHub and Chainguard. Excited to have him here!

Please welcome Chris Hawkins to the Flox team! 👋 Chris joins us in NYC after enterprise sales roles at CodeRabbit, Coralogix, Elastic and Chef Software. Excited to have him helping teams bring reproducible environments (and Nix) to work. 🚀

Please welcome Chris Van Wesep, our new VP of Marketing! 👋 Chris most recently led marketing at Nutrient and was VP of Revenue Marketing at HashiCorp. Excited to have him on board as we bring reproducible environments to every developer and every agent!

Last week our co-founder and CEO @refroni.bsky.social joined “The Case for Open Source Models” panel at Leverage Israel during SF Tech Week. Thanks to Leverage, Onyx Security and a16z speedrun for bringing the room together! #opensource #techweek

New York, see you next week! We’ll be at the AI Engineer conference, October 12–14, joining engineers and technical leaders bringing AI into production across financial services. Come find the Flox crew at booth 46! More about the event: buff.ly/uUROEDA

What happens when you point a coding agent at a real, messy codebase and ask it to sort out the dev environment? Justin wrote up the whole experiment, including what worked, what broke, and what the skills did about it 👇 buff.ly/XCNqiur

We’re at #NixCon2026 ❄️ The booth is up, the Flox team is here, and we’re very happy to be spending the next few days with the #Nix community in Kraków. Come say hi, talk Nix, grab some swag, and hang out with us. See you around! 😎

We’re coming to NixCon 2026! Come say hi, grab some swag, and catch the Flox team on stage: 🟣 Ron Efroni: Nix State of the Union 2026 and Nixing Artificial Intelligence 🟣 Yannik Sander: Adding to the Pile, or How to Extend nixpkgs 🟣 Rok Garbas: Flox lightning talk Full schedule: buff.ly/UR2zBC4

Flox v1.16 is out. Run a package on demand, without creating an environment or installing anything. Plus: new plugins for 1Password, Vault, OpenBao, and Infisical. Secrets stay with the provider and become available when you activate. More: buff.ly/XAEDEq8

“Skills are software” There’s a great discussion about agents in this Fallthrough episode with Ron and James. Thanks to Matthew and Kris for having us! Watch here: buff.ly/ClOSMPu

The faster agents build, the less tolerance there is for inconsistency in the environments where they work. Reproducibility is what ensures that AI agents always build, test, and debug in exactly the same environment. Captured at PlanetNix 2026.

Join us for the AI in Production meetup next Tuesday! Our CPO, James Bayer, will be joining Mitchell Anderson from @inngest.com and Sujee Maniyam from Nebius for an evening of talks, demos, and conversations about what’s actually working when AI moves past the prototype stage. buff.ly/B6c3WKi

luma.com{AI} in Production with Inngest, Nebius Token Factory, Flox, & Minimax · LumaJoin us for the August edition of {AI} in Production, a gathering focused exclusively on AI engineering. Whether you're a seasoned machine learning engineer or…

Flox is growing! Welcome to the team, Justin, Alan, and David 👋 We’re excited to have you all on board. Let’s go! 🚀

Signing a person in and authenticating a pipeline are two different jobs. FloxHub now treats them that way. Today, we are announcing two new credential types for FloxHub: Service Account Tokens for automation, Personal Access Tokens for people. Full writeup: buff.ly/Qdhjrk9

Auto-activation is here for Flox environments. Walk into a directory with a .flox folder and the environment turns itself on. Nested environments and services come along too. Your environments become one less thing to think about. Read the full post here: buff.ly/8CYRuSbhttps...

One tool. Every language. Declare Python, Node, Go, Rust, or whatever your project needs in a single Flox environment. Flox activate, and the exact versions you pinned land first on PATH. Same on macOS and Linux, no containers. Change a version? That's a reviewable diff. buff.ly/de8Wb25

People keep asking how to set up their AI stack as code. So here's the pattern: one Flox file — packages, versions, services — that your whole team activates. Same stack on macOS, Linux, WSL2, CUDA or Metal. Link here: buff.ly/PVaRl8m

Getting the same environment twice was never easy. Now a coding agent installs dependencies and changes your system while you're not looking causing your laptop to drift further from prod. Flox CPO James Bayer gets into it on Temporal's Vibe Check: buff.ly/HWaXb38

Shai-Hulud doesn't break in. It gets installed, then reads whatever credentials are lying around and ships them off. A hermetic build keeps nothing lying around: no ambient creds, no network. It can't steal what it can't see. Link to full blog: buff.ly/Xw2Jie6

Couldn't make Planet Nix 2026? Or made it, but spent the whole time in the hallway track? Either way, the talk recordings are all on YouTube now. buff.ly/sG5nlLg

It trains on your MacBook then it hits Slurm and dies: wrong CUDA, missing libs, broken paths. Not another container. One Nix-pinned environment, identical from laptop to cluster to prod. We trained nanoGPT on Slurm to prove it: buff.ly/JJJd5yP

We're going live with Temporal on June 24. James Bayer shows how a reproducible Temporal + AI dev environment goes from a stack of manual setup steps to one command: `flox activate`. Then more on sandboxing, security & observability. 📆 Jun 24 · 11am PT · buff.ly/8xH3pQu

Planet Nix is back. April 1-2, 2027 in Pasadena. Two days of Nix in production — the talks, the workshops, and the people building with it. The CFP is open. If you've shipped something real with Nix, get on stage: buff.ly/sJ1qFRe

Dev containers or Nix-style environments? False choice. Declare your runtime — language, libraries, build tools, CLIs — natively on the host with Flox, Nix, or Guix. Keep backing services in containers. The same split runs local → CI → prod. buff.ly/Y27BWgA

Flox is powering Resolve AI’s dev environments. Resolve triages production incidents for the world’s biggest companies. Their team now builds on reproducible Flox environments: one shared setup that can run locally, in CI, and in prod. Learn more here: buff.ly/m7m9TDo

New tools like DeepSeek TUI show why local AI tooling is heating up: Users want fast, terminal-native harnesses for local and cloud models on NVIDIA CUDA and Apple Silicon. We show how Flox and Nix make the stack—models, servers, CLIs, envs—easier to run, build, and share. buff.ly/RcQlnml

Flox reposted

Replying to @alilleybrinker.com

Happy to say that I've been using Flox for a couple of weeks and so far (after some initial networking weirdness that wasn't Flox's fault) it's Just Worked. The rest of my team is still getting used to it, so it's possible we'll encounter new pain points in the future, but so far it's been great!

Fellow.ai hit a familiar scaling problem: “works on my machine” in local dev, CI/prod bugs, costly rework. With Flox, Fellow.ai got reproducible dev environments that work across laptops, CI, and prod—reducing onboarding friction, environment drift, and downstream risk. Full blog in the comments!

In financial services, today’s cutting-edge ML model becomes tomorrow’s baseline. Flox gives platform teams pinned, declarative GPU runtimes that travel from MacBooks to Slurm, CI, and Kubernetes—cutting runtime drift, image rebuild loops, and audit friction. Read the full article in the comments!

“Works on my machine” isn’t a joke. It means local dev has become shared infrastructure without being managed that way. Strict isolation is one path to reproducibility. Declared, locked environments are another: portable, verifiable, and better suited to local autonomy. full blog in the comments!

flox.devFlox | Standardized Development Environments ExplainedWorks-on-my-machine is symptomatic of an ongoing failure to treat the local development environment itself as shared project infrastructure. Standardized development environments are a compelling…

#PlanetNix 2026 throwback! Kelsey Hightower on discovering #Nix and realizing there was a fundamentally different way to think about software. buff.ly/9pzlu5c

RustWeek is almost here! Flox's Yannik Sander will be in Utrecht to learn, connect, and enjoy the program. Want to chat about Nix, reproducible dev environments, Rust workflows, or easier team setups? Ping him via yannik at flox dot dev; meetup time is limited b/c of talks.

fellow.ai used Flox to standardize reproducible environments across dev → CI → prod. The impact: ✔️ Faster engineer onboarding ✔️ Higher developer velocity ✔️ Fewer fire drills ✔️ Less rework ✔️ Reduced release risk Case study in comments.

Flox reposted

Found a new use for @flox.dev today - was able to reproduce a bug involving communication between Ceph clients of two different versions. Before flox I probably would have set up 2 VMs with different versions of the packages installed but instead I was able to just run my tests from 2 flox envs

Security teams are often asked to certify where they can only infer. Scans, SBOMs, attestations, tickets, approvals; no confident answer to: do we know what’s running and how it got there? Secure software by construction starts with versioned, auditable runtimes. buff.ly/YxdymBY

buff.lyFlox | Secure Software by ConstructionFlox provides deterministic foundations for probabilistic workflows, so AI-driven velocity doesn’t come at the cost of stability, security, or compliance.