Flox @floxdevelopment

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!

Raleigh, see you next week! We're heading to @AllThingsOpen October 19–20, to talk with the #opensource community about bringing #Nix to work (and more) Come find the Flox crew at booth #9 and say hi 👋 More about the event: buff.ly/7bf8IHg

Last week our co-founder and CEO @ronefroni joined “The Case for Open Source Models” panel at Leverage Israel during SF Tech Week. Big thanks to his fellow panelists and moderator for a great conversation on why open models matter, and what it takes to run them in a way teams can actually trust and reproduce. Thanks to Leverage, Onyx Security and @speedrun for bringing the room together!

keyboard_arrow_left Previous keyboard_arrow_right Next

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, tell us what you’re building, and say hi! More about the event: buff.ly/uUROEDA

In today's video, we'll check out @floxdevelopment which lets you automate build environments for all your coding sessions. Full getting started guide! youtu.be/QGZTJX_Gjk4 #Flox #DevOps #FloxEnvironments

Check out @CastillaCodes latest blog 🔥

What happens when you point a coding agent at a real, messy codebase and ask it to sort out the dev environment? Justin (Our DevRel Lead <3) put our `floxify` skill to the test on Mastodon, a challenging repo (with Ruby, Node, PostgreSQL, Redis, native dependencies, multiple services) to build from source. The skill went through the repo, figured out what it needed, built the Flox environment, checked it, hit a few problems, fixed them, and kept going until `flox activate` worked. All in just a couple of minutes. The result: a declarative, reproducible Mastodon environment without using containers, and without Justin (or an agent) having to reverse-engineer the setup from scratch. He also tried the `flox` skill for a new project, starting from what he wanted to build rather than an existing codebase. Two different starting points, same idea: Give the agent what it needs to quickly set up the runtime environment. This way it spends tokens running and testing code instead of debugging setup. Justin wrote up the whole experiment, including what worked, what broke, and what the skills did about it 👇 buff.ly/VBYNYQc

What's the case for open source models? One of our panels on the main stages will be with Dr. Roy Nissim, AI Inference Lead @RedHat @ronefroni (CEO @floxdevelopment) @eyalniv (MD @Pitango VC, $3B AUM) Dr @YairAdato (CEO @bria_ai_ ) We've 50 seats left, link to apply in the first comment

Comming soon: 1. Was interviewed by @mightyiam (Full Time Nix Podcast) 2. Was interviewed by @ronefroni (Pres. @nixos_org + (CEO @floxdevelopment) 3. Interviewed @oppili (for @tangled_org) 4. Interviewed @GaetanLepage_ (for nix-cuda) 5. Interviewed @vaxryy (CEO hyprland + anime)

keyboard_arrow_left Previous keyboard_arrow_right Next

𝗠𝗮𝗹𝗶𝘅 @Malix_Labs

3 weeks ago

NixCon Epilogue 1. Highest autism/m² ratio conf (in a good way) 2. Met many old and new friends 3. Everyone was polite and can have respectful disagreements 4. Thus Nix needs more such events to make us touch grass together 5. Extremely well organized + good food See y'all soon

keyboard_arrow_left Previous keyboard_arrow_right Next

4 3 81 4K 7

@ronefroni on stage at #NixCon2026 talking about Nixing AI ❄️

We’re at #NixCon2026 ❄️ The booth is up, the Flox team is here, and we’re super 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! 😎

keyboard_arrow_left Previous keyboard_arrow_right Next

Just wrapped up an amazing day at @WeAreDevs with a Lego Salon collab event with @floxdevelopment @apify and @runpod . So many people came out to have fun after the conference building Legos, chatting up what they saw, and cheering on our 3 winning groups. So much fun, everyone!

keyboard_arrow_left Previous keyboard_arrow_right Next

Every NixCon, the same feeling: so excited I can barely sleep. 😄

Flox @floxdevelopment

a month ago

We’re coming to NixCon 2026! We’ll be in Kraków from September 25–28 to catch up with the #Nix community and share what we’ve been working on. Come say hi at our booth, grab some swag, and catch the Flox team on stage: 🟣 @ronefroni Nix State of the Union 2026 and Nixing

0 0 3 491 0

We’re coming to NixCon 2026! We’ll be in Kraków from September 25–28 to catch up with the #Nix community and share what we’ve been working on. Come say hi at our booth, grab some swag, and catch the Flox team on stage: 🟣 @ronefroni Nix State of the Union 2026 and Nixing Artificial Intelligence 🟣 Yannik Sander: Adding to the Pile, or How to Extend nixpkgs 🟣 @garbas Flox lightning talk See you in Kraków! Full schedule: buff.ly/UR2zBC4

Flox v1.16 is out, with two additions: `flox run` and a new plugin system for secrets management. `flox run` lets you run packages from the Flox Catalog without creating an environment or installing anything: `flox run jq` Flox resolves the package that provides the command and runs it on-demand. If multiple packages provide the same command, you can select one and Flox will remember your choice. Or you can specify it explicitly with `--package`. This is especially useful in CI: `flox run --package python312 -- python hello.py` The new secrets plugin system provides pre-built integrations with 1Password, HashiCorp Vault, OpenBao, Infisical, and other providers. Secrets remain with the upstream provider; Flox retrieves + makes them available in the environment at activation. No custom logic required. Learn more about `flox run` and secrets management with Flox plugins 👉 buff.ly/FdFbDLN

Wrapping @DevOpsDaysPDX 2026! TL;DR: the platform work you've already done is what saves you when AI hits your pipeline. Best talk for me: Daniel Sauble's Nix ignite. Containers fix reproducibility yet wreck DX. Nix fixes both, down to glibc. Also got to meet the Flox folx IRL!

Starting to write up the NixOS State of the Union, what do you want to talk about?

@olvrgln Happy to show you what are we cooking at @floxdevelopment ... Would also like to learn what are you current problems to make sure we fix them for you.

“Skills are software” There’s a great discussion about agents in this @fallthroughfm episode with @ronefroni and @jambay. A skill might start as a Markdown file, but it can also rely on scripts, packages, runtimes, MCP servers, and other resources. And those dependencies change. So the same agent can behave differently depending on where or when it runs. James shares an example of a company using Flox to capture the full environment behind its agents. If something goes wrong, they can recreate the exact set of tools, dependencies, and runtime the agent was using, reproduce the failure, and see what happened. We’re still figuring out a lot about how agents will change software development, but making the environment around them reproducible feels like a pretty useful place to start. Lots more in the full episode. Thanks to @sudomateo and @skriptble for having us! Watch here: buff.ly/ClOSMPu

The Go podcast let us hijack an episode to talk about Nix n Flox. 😅 (❤️ @sudomateo & @skriptble) Dug a bit into.. Why Nix can feel hard. Why there's 5+ paths for every goal. Bringing Nix to work. And what we are cooking at @floxdevelopment #NixCon very soon ;) #NixOS

Fallthrough @fallthroughfm

2 months ago

Ever wonder how NixOS works? In this week's episode of Fallthrough @sudomateo and @skriptble are joined by @ronefroni and @jambay to talk about NixOS and Flox. They get into what NixOS exists to solve and how Flox helps with that mission. fallthrough.fm/86

0 2 3 1K 0