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

We are proud to announce @flox.dev as a Closure tier sponsor for #NixVegas at DEF CON 34! Their help will allow us to provide DEF CON badges for our speakers CFP still open until 2026-06-15 ➡️ cfp.nix.vegas/2026/ Sponsor us ➡️ nix.vegas/2026/sponsor

Software should be simple. buff.ly/kX09PWU

Today we're publishing a new playbook for platform teams: how to standardize project environments without forcing every team into the same stack. buff.ly/USXS8Ng

FloxHub login just got two new doors! buff.ly/cLmyeyF

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

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!

#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.

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

Package managers, containers, environments… these often get conflated. We published a guide unpacking where package managers help, where they fall short, and why reproducibility across the SDLC is still unsolved for many teams. Learn more on the blog:

CVE remediation is a dependency-graph problem. Scanning attempts to infer from built artifacts. Flox/Nix derive artifacts + runtimes from the causal dependency graph. Remediation = dbms lookup + declarative edit: identify artifacts/envs, pin a replacement ref, promote. Read more in the comments!

It’s not containers vs Flox. It can be Flox for languages and dev environments, containers for services, and the same environment reused in CI. New guide on the blog: buff.ly/et5t5eJ @rok-garbas.bsky.social at Flox cut a video that walks through this - link in the comments!

We talk a lot about #AI right now, but this keeps coming up in conversations: determinism and reproducibility. If code is being generated by agents, and systems are getting more complex, you need to be able to answer a pretty simple question: what actually ran? Ron on this at PlanetNix 2026 👇

Security teams don’t need more heroic CVE triage. They need a better source of truth. Learn more about how reproducibility, traceability, and atomic response can reduce firefighting. buff.ly/a75igyP

Your #AI coding tools are only as reliable as the environment behind them. Quick walkthrough on using Flox with Codex, Cursor, and agent-driven package installs and environment activation.

“Feels like everyone just wants to solve problems together.” One of the best parts of #PlanetNix this year? The community. Captured a bit of that vibe along with a few favorite moments and talks from the event. And a little throwback to our after party, good times! 💜

New guide! A practical look at: - PyTorch runtimes that work across platforms - modular CUDA environments - build toolchains for R&D and MLOps - reproducible deployment patterns for AI teams buff.ly/M2OgkYX

A lot of people talk about frontier models. Less about how to run them reliably. New guide on running Gemma 4 and GLM 4.7 Flash locally with Flox using turnkey environments for Ollama and LM Studio. Reproducible local AI workflows across Mac, Linux, and Windows. buff.ly/0NeDdvS

In capital markets, speed matters. So do control and reproducibility. Learn how companies use Flox + Nix to reduce rebuild overhead, improve traceability, and promote or roll back by pinned reference. A practical look at reproducible AI infrastructure for regulated environments. buff.ly/h6wveJG

Flox tip: activation modes let you control what actually shows up in your PATH By default, Flox activates in dev mode, which exposes the full dependency closure: interpreters, compilers, runtimes, everything. That’s exactly what you want when you’re building or debugging.

#AI increases the speed and volume of change across your entire software lifecycle. But your accountability stays the same. Flox provides deterministic foundations for probabilistic workloads, so velocity doesn't come at the cost of reliability, security, or compliance. buff.ly/VL4BuvB

We spoke with Farzan Karimi (Deputy CISO @ Moderna, SunsetCon) about what’s changing in #security right now: - Automated attack simulation is becoming standard - AI agents are taking over low-level pentesting + recon But the real shift? Agentic offense + agentic defense. buff.ly/t2fgYw7

Dependency resolution, version drift, conflicting toolchains, “works on my machine” → all of that burns tokens and breaks workflows. This is where Flox fits. 🟣 Cross-language package manager 🟣 Works across OS + CPU/GPU architectures 🟣 Deterministic, declarative environments buff.ly/RZtOBET

Tom Bereknyei, a long-time contributor and steering committee member, breaks down where #Nix really shines and where it doesn’t. If you’re working across: 🟣 multiple languages 🟣 different systems or architectures 🟣 constantly changing environments Nix lets you glue everything together.

The real shift isn’t just “build faster with AI.” It’s zooming out and asking: how does all of this fit together? That’s where having a solid, reproducible foundation starts to make a big difference. Check out the full webinar here 👉 buff.ly/GWafnp6

Open source only works because people can share work, build on it, and trust that what’s being handed off is something they can actually reproduce. Great conversation from James Bayer and Stormy Peters at PlanetNix 2026 ↓ Watch it here 👉 buff.ly/9q5p19j

Instead of chasing drift, debugging inconsistencies, or relying on post-hoc fixes, you get deterministic environments that behave the same from dev → CI → production—every time. Velocity without control isn’t a strategy. See how leading teams are building with both → buff.ly/PyyPsmb

At PlanetNix, Jacek Galowicz pointed out that a lot of teams are focused on moving fast, scaling things, and figuring things out as they go, rather than over-planning everything upfront. And Nix actually supports that way of working in a very practical sense. More 👉 buff.ly/WrhzbMV

If you’re doing platform engineering, you’ve probably spent more time than you’d like dealing with environment drift. Flox helps you eliminate “works on my machine” issues across the org, while giving you centralized visibility and control across the software lifecycle. buff.ly/geucIkZ

Ron shares one of the most common reasons teams are bringing Nix into their organizations: security. With Nix, the entire software supply chain is reproducible. That means you know exactly what’s running, where it came from, and how it’s connected.

Kubernetes gives us a declarative model for creating and managing clusters, but the way we build the OCI images our workloads run on is still largely imperative.. Our latest article in the "Kubernetes, Uncontained" series looks at how Flox closes that gap. buff.ly/721c10I

At PlanetNix 2026, Farid talked about how far you can really take #Nix: Going all the way down to kernel-level changes, building things exactly how you want, and trying ideas that would normally feel way too risky. That’s kind of where the magic is!

Claude Code, OpenAI Codex, GitHub Copilot, and other AI agents/AI coding assistants can use Flox’s MCP server to discover, find specific versions of, and install just the right dependencies, searching among *millions* of historical packages. Read on 👉 buff.ly/3d0IYJe

See how financial services teams use Flox and #Nix to ship #CUDA ML stacks with reproducible environments, atomic rollbacks, and provable software supply chains. buff.ly/gIbNZrH

Nix isn’t niche anymore. It’s already being used by teams and companies that care about #reproducibility, control, and getting their environments right. Ron breaks it down here: buff.ly/kneJ0xX

Most teams adopt Flox in local development first, usually to fix broken dev environments or to get out of the dev container loop. What’s interesting is the pattern that tends to emerge after that. Dive in! buff.ly/kaGAIqR

We talk a lot about AI right now, but this keeps coming up in conversations: determinism and reproducibility. If code is being generated by agents, and systems are getting more complex, you need to be able to answer a pretty simple question: what actually ran? buff.ly/Gs2wdkZ

#PlanetNix 2026 throwback! @stahnma.us caught up with @jacquie.bsky.social at PlanetNix for a quick chat on what’s actually happening in the #Nix world right now ❄️

Still thinking about #PlanetNix 2026! Huge thank you to everyone who showed up: from teams to individual builders, contributors, speakers, and the whole #Nix community. That’s really what made it special 💜 buff.ly/L3LWmQT

Red Hat published a great piece recently on “Bring Your Own Agent”. In this new blogpost Jeremy Hogan builds on that idea with a simple observation: All of that governance assumes something underneath: the security and stability of the environment the agent actually runs in 👉 buff.ly/OXWQoHr

We’re at All Things AI this week 👋 Talking to teams building real AI systems, seeing how workflows are changing, and where things are heading! If you’re here too, come find us. Always up for a good convo!

It’s our last day at NVIDIA GTC and the booth is buzzing ⚡ Come find us at booth #4046 before 2pm to meet the team and chat about building deterministic environments. Show us a Floxhub environment you pushed to get a prize 🎁 See you soon!

👀 Who’s ready for happy hour ✨ If you’re at NVIDIA GTC, come say hello 👋 No talks, no agenda — just good drinks, light bites, great people, and easygoing chats about Nix (or whatever you’re working on!). buff.ly/KEHTbYX

A great night during NVIDIA GTC 🚀 We hosted an evening with ICC and NVIDIA, bringing together a fantastic group across financial services, AI, and HPC. Really strong conversations on where AI infrastructure is heading, and what teams are dealing with day to day. Thanks to everyone who came out!