Reactive Nix: Enabling Functional Reactive Configuration with mgmt#

Jannik Höfler, DevOps Engineer at Dev Specialists GmbH

• Why: A genuinely novel configuration-management idea: Nix evaluates to a static snapshot of desired state, and this work asks what happens if configuration is a function over time instead. It's a new point in the declarative/reactive design space, from the mgmt (functional reactive configuration management) ecosystem.
• What: The rx.nix (Reactive Nix) project — combining Nix's purely functional configuration model with mgmt's FRP runtime so systems stay declarative and reproducible yet react continuously to environmental change, instead of being frozen between builds (from abstract only).
• How: Nix models system = f(configuration) — a fixed value per build. FRP generalizes to system(t) = f(configuration, environment(t)): the config stays pure but depends on signals that evolve continuously; mgmt's runtime observes, reacts, and converges to declared state without re-evaluation.
• Where applicable: Research/frontier territory rather than production tooling — an exploration of what continuous convergence would mean for NixOS-style systems. Most interesting as a conceptual reframing of drift: instead of re-running to correct drift, the configuration itself is time-aware.