Kestra
Declarative YAML pipelines that are not tied to Python.
84
sovereigntyKestra declares workflows in YAML and runs the actual work in whatever language you like — Python, R, Node, shell, SQL, or a container. That makes it the natural pick when the pipeline is not a Python project: data engineers and analysts can read and edit the flow definitions without being Python developers, and the built-in editor and live-updating topology view make the graph legible to people who would never open a DAG file. It is the youngest and smallest project here, which is the honest caveat, but it is Apache-2.0, self-hostable and moving quickly.
OPEN SOURCEApache-2.0 (core; enterprise edition is commercial)SELF-HOSTLOCAL-FIRST
LicenseApache-2.0 (core; enterprise edition is commercial)
PricingOpen-source core free and self-hostable. Commercial enterprise edition for RBAC, SSO and multi-tenancy.
Open sourceYes
Self-hostableYes
Local-first dataYes
What it does well
- +Language-agnostic — pipelines are not forced into Python
- +Declarative YAML plus a built-in editor and live topology view
- +Event-driven triggers as a first-class concept, not a workaround
- +Single binary plus a database; simple to stand up
Where it falls short
- −Youngest and smallest community of the four
- −YAML gets unwieldy for genuinely complex conditional logic
- −Enterprise features — RBAC, SSO, multi-tenancy — are behind the paid edition
- −Fewer people know it, so you will be training rather than hiring
Kestra as an alternative to
Where Kestra shows up in our comparisons, and how it ranked.
Kestra head-to-head
Straight comparisons against the tools people weigh it against.