Flox

“Flox helps bring simplicity to this space, making it approachable, while not hiding the opportunities and power in the tools.”

“Flox gives us a dependable foundation so we can move fast with tight feedback loops.”

“Before, our local dev guide comprised 16 steps with 14 caveats. Now, it’s just a universal flox activate.”

“Flox gives us a reproducible foundation we can trust, which matters more and more as our team grows. It also gives us a much more controlled path for shipping software fast and reliably.”

““Plus, if something does go wrong, you don’t wonder whether it’s something real ... or an artifact of the machine it was built on. Teams spend less time chasing noise and more time working on actual issues.””

““Flox gives you this declarative reference, the Flox manifest, so you don’t have to rediscover what [dependencies] software needs for it to run,””

““The Flox environment is declared up front, so shipping downstream gets easier, too: Teams don't guess about what the code needs to build and run. It's defined in the environment."”

““Standardization means people focus on building the things we actually need to ship,””

““Flox takes a lot of the guesswork out of day-to-day engineering, because you aren't constantly wondering: ‘Is this a real bug in the code or … is it just that something's different on somebody machine?’””

““That changed the repo from ‘here’s the code, figure out how to run it’ into something self-contained. You could hand it to someone and be confident they're going to get the same behavior you got,””

““People are comfortable using it and ‘works on my machine’ disappears. Flox stops being a thing people have to think about, except to do useful things.””

““We weren't spending the same amount of time thinking about the environment anymore, which is exactly what you want,””

““You get strong reproducibility on your local machine. When you share what you’ve built, it just works.””

““Flox doesn’t make us choose between strong reproducibility and a normal local workflow,””

““What I liked about Flox was its simplicity. It allows us to define and work with environments in a way people can read, understand, and use. I didn’t worry about adoption becoming its own project,””

““Flox also gives us a much more controlled path for shipping software fast and reliably.””

““Flox gives us a reproducible foundation we can trust, which matters more and more as our team grows,””

“Honestly, Flox mostly sold itself. A person started using it, other people saw they were using it, so they switched to it too. Nobody had any real trouble understanding it,”

“For most people, after it was set up, Flox just faded into the background. They know it's there, but they don't have to think about it when they're working. It doesn't get in the way. In fact, it's become part of how things work for us.”

“I liked that Flox would give us Nix-like guarantees under the hood, but in a way that let us get those benefits without the learning curve. Flox was transparent for our team. They didn't have to learn new tools or a new language, or change anything, to work with it.”

“Flox gives you this declarative reference, the Flox manifest, so you don’t have to rediscover what [dependencies] software needs for it to run,” Amin explains. “Plus, if something does go wrong, you don’t wonder whether it’s something real ... or an artifact of the machine it was built on. Teams spend less time chasing noise and more time working on actual issues.”

“Standardization means people focus on building the things we actually need to ship,” he explains. “The Flox environment is declared up front, so shipping downstream gets easier, too: Teams don't guess about what the code needs to build and run. It's defined in the environment.”

“That's what I mean by ‘producing,’” Amin says. “People are comfortable using it and ‘works on my machine’ disappears. Flox stops being a thing people have to think about, except to do useful things.”

“Flox doesn’t make us choose between strong reproducibility and a normal local workflow,” Amin points out. “You get strong reproducibility on your local machine. When you share what you’ve built, it just works.”

“Flox gives us a reproducible foundation we can trust, which matters more and more as our team grows,” says Amin Karbas, a member of the technical staff with Resolve AI. “Flox also gives us a much more controlled path for shipping software fast and reliably.”