'Works on my machine' is framed as a platform problem, not just a local dev annoyance. Platform teams own the shared runtime contract that engineers depend on across local dev, CI, and production. Flox addresses this by letting teams define declarative, reproducible environments that travel with repos — specifying language runtimes, system packages, services, env vars, and setup hooks. Unlike dev containers or cloud workspaces, Flox runs in subshells so developers keep their local tools and workflows. FloxHub enables teams to share and reuse portable environments. The post uses Fellow.ai as a case study and includes an extensive FAQ covering how Flox compares to READMEs, language version managers, dev containers, and cloud dev environments.
