Editions & operating modes
The two editions (Lite and Pro) and the three runtime modes (Lite · Pro · Demo) — one engine, one UI, one DAG format.
Version v0.4.0 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
Concepts
The model behind Leoflow — editions and modes, core concepts, the architecture, and UI compatibility.
How Leoflow works, and why it is shaped the way it is.
- Editions & operating modes — the Lite/Pro split and the Lite · Pro · Demo runtime modes.
- Core concepts — DAGs, runs, and tasks; pause semantics; why each DAG is its own image.
- Architecture — the Go control plane, the split API/scheduler roles, and the execution data flow.
- UI compatibility — what the Airflow-compatible UI supports, and where it differs.
Looking for term definitions? See the Glossary in Reference.
Core concepts
How a DAG, its runs, and its tasks fit together — pause semantics, and why each DAG is its own container image.
Architecture
The Go control plane, the split API/scheduler roles, and the execution data flow.
UI compatibility
What the Airflow-compatible UI supports, and where it intentionally differs.