Flox @flox.dev · 26/09/2026@refroni.bsky.social on stage at #NixCon2026 talking about Nixing AI ❄️ 010
Flox @flox.dev · 25/09/2026We’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! 😎 020
Flox @flox.dev · 17/09/2026We’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 021
Flox @flox.dev · 11/09/2026Flox 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 011
Flox @flox.dev · 08/09/2026In Tel Aviv for AWS Summit? Join us tonight for the Pre-AWS Summit Community Blitz, where Flox CEO @refroni.bsky.social will share why agentic workflows need a deterministic foundation, alongside great speakers from Cast AI and Datadog. See you there? buff.ly/QpIC3t8buff.lyin10t — Great events start with intentCommunity, ticketing, CFP, sponsors, and discovery — all in a single place. 000
Flox @flox.dev · 04/09/2026“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 000
Flox @flox.dev · 02/09/2026glad you found us and we agree! Feel free to give us a shout anytime here or on our community slack :) 010
Flox @flox.dev · 28/08/2026The 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. 000
Flox @flox.dev · 21/08/2026Join 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/B6c3WKiluma.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… 020
Flox @flox.dev · 13/08/2026Flox is growing! Welcome to the team, Justin, Alan, and David 👋 We’re excited to have you all on board. Let’s go! 🚀 020
Flox @flox.dev · 04/08/2026Signing 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 000
Flox @flox.dev · 30/07/2026Auto-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... 010
Flox @flox.dev · 22/07/2026One 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 000
Flox @flox.dev · 16/07/2026People 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 000
Flox @flox.dev · 09/07/2026Getting 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 000
Flox @flox.dev · 30/06/2026Shai-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 000
Flox @flox.dev · 25/06/2026Couldn'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 000
Flox @flox.dev · 23/06/2026It 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 000
Flox @flox.dev · 18/06/2026We'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 130
Flox @flox.dev · 15/06/2026Planet 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 000
Flox @flox.dev · 11/06/2026Resolve runs their developer environments on Flox: reproducible, the same on every machine. Read the story: buff.ly/vsoFqpL 000
Flox @flox.dev · 04/06/2026Dev 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 000
Flox @flox.dev · 02/06/2026Flox 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 021
Reposted by FloxNixVegas @nixvegas.bsky.social · 29/05/2026We 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 011
Flox @flox.dev · 27/05/2026Today we're publishing a new playbook for platform teams: how to standardize project environments without forcing every team into the same stack. buff.ly/USXS8Ngbuff.lyFlox | Platform Teams and the Challenge of Works-on-My-MachineA practical guide to creating and working with Flox standardized local development environments, including playbooks for defining, reproducing, and managing project environments at scale. 020
Flox @flox.dev · 21/05/2026New 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 010
Reposted by FloxAndrew Lilley Brinker @alilleybrinker.com · 20/05/2026Happy 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! 252
Flox @flox.dev · 20/05/2026Fellow.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! 120
Flox @flox.dev · 18/05/2026buff.ly/8N2NwpJflox.devFlox | Reproducible, Auditable ML/AI for Capital Markets with FloxLearn how firms in capital markets use Flox to deliver ML/AI workloads faster and more reliably, with deterministic SBOMs, controlled rollbacks, and the ability to run conflicting dependency stacks… 000
Flox @flox.dev · 18/05/2026In 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! 100
Flox @flox.dev · 15/05/2026“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… 120
Flox @flox.dev · 14/05/2026#PlanetNix 2026 throwback! Kelsey Hightower on discovering #Nix and realizing there was a fundamentally different way to think about software. buff.ly/9pzlu5c 010
Flox @flox.dev · 13/05/2026RustWeek 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. 010
Flox @flox.dev · 12/05/2026fellow.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. 120
Reposted by FloxWill Gorman @willgorman.net · 18/03/2026Found 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 021
Flox @flox.dev · 11/05/2026Security 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/YxdymBYbuff.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. 000
Flox @flox.dev · 08/05/2026Package 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:buff.lyFlox | Package Managers and Package Management: A Guide for the PerplexedThe most important problem in packaging is how to efficiently, reliably, and securely packaging and distributing software so builds are deterministic and runs are portable and reproducible 100
Flox @flox.dev · 07/05/2026CVE 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!flox.devFlox | Achieving CVE Remediation in an Era of Escalating VulnerabilitiesAI is accelerating the rate of CVE discovery. Learn how Flox and Nix transform package vulnerability triage from repeated artifact scans into quick, queryable dependency-graph analysis. 110
Flox @flox.dev · 06/05/2026buff.ly/wUjBYDvyoutube.comFlox + ContainersContainers and Flox.You already know how to build them but here are a few things worth knowing when you build them with Flox. In this short video, Rok Garbas, Flox engineer and Nix contributor,… 000
Flox @flox.dev · 06/05/2026It’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!buff.lyFlox | Flox and Containers: A Perfect Pattern for Local DevelopmentLearn how to pair Flox with containers for local development: Flox provides the project runtime on the host, while containers run supporting services like PostgreSQL. 110
Flox @flox.dev · 05/05/2026We 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 👇 000
Flox @flox.dev · 04/05/2026Security 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 000
Flox @flox.dev · 01/05/2026Your #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.buff.lyQuick Walkthrough on using Flox with Codex, Cursor, and agent-driven package installsWorking with AI tools in your dev workflow? There’s more than one way to integrate them with your environment. In this quick Flox tutorial, we show a few approaches: → Activate your environment… 110