The name
Dexaflow started in Brazil, every line of it, from the first commit.
It was born as Leoflow. The flow part orchestrates workflows. The Leo part honors Leonardo (@leonardo-jas), an architect with deep roots in Brazil’s tech industry who taught its creator to think in state machines: states, transitions, invariants, the things that must never happen. The core of this project turned out to be exactly that, a scheduler that is, underneath, a state machine.
In v0.5.0 the project took the name of the company that builds it, DexaData,
and became Dexaflow. The dedication stays, and so does everything people
adopted under the old name: the leoflow command, leoflow.yaml, the
LEOFLOW_* variables, ~/.leoflow, the leoflow-* images and the
charts/leoflow chart all keep working. The full list, and the internal names
that keep the old spelling, is in
names from before the rename.