The data orchestration market has stratified into distinct tiers as of 2026, with several tools at different stages of adoption and maturity.
Tier 1: The Incumbent
Apache Airflow still dominates by sheer scale. It crossed 30 million monthly PyPI downloads, runs in 80,000+ organizations, and has attracted 3,600+ unique contributors — more than Apache Spark or Kafka. That contributor base matters: it means battle-tested operators for practically every system in existence, edge cases handled in production across thousands of deployments, and a hiring market where “Airflow experience” appears on nearly every data engineering job description. 94% of Airflow users say the knowledge positively impacts their careers.
Airflow 3.0, released April 2025, was the biggest release since the 2.x rewrite. The headline features: DAG versioning, a new React UI replacing the aging Flask interface, the Task Execution Interface for better scaling, and — most significantly — an @asset decorator that borrows directly from Dagster’s playbook. By March 2026, Airflow reached v3.1.7.
The @asset decorator is the most telling feature. It signals that even the most established task-based orchestrator recognizes the shift toward asset-centric thinking. But as practitioners have noted: “I don’t believe you can just switch from being task-oriented to assets. This is a much deeper shift that is hard to get for Airflow. Dagster is still miles ahead.” Whether Airflow 3.x can make asset-centric thinking first-class — or whether it remains a feature grafted onto a task-based paradigm — is one of the key questions for the rest of 2026.
Tier 2: The Modern Challengers
Dagster leads the modern challenger tier. With $47M in total funding (Series B, May 2023), roughly $7.2M ARR as of late 2023, and 15M PyPI downloads in 2024, it had the most active codebase by commit volume with 27K commits in 2024. The Components framework reached GA in the 1.12.x cycle, and 50% of Dagster Cloud users integrate dbt.
Half of Dagster’s cloud customer base uses it specifically for dbt orchestration — the highest dbt adoption rate of any orchestrator. The dagster-dbt integration maps each dbt model to a tracked asset with automatic lineage, freshness monitoring, and quality checks from dbt tests. For teams that think in models, refs, and tables, Dagster speaks the same language.
The Components framework and the dg CLI are designed to lower the barrier for SQL-first analytics engineers who find the Python overhead intimidating. If they succeed, the learning curve objection — the most common friction point in adoption — weakens considerably.
Prefect ranks second in raw downloads at 32M PyPI downloads in 2024 and maintains a 25,000-member Slack community. Prefect 3.0 (September 2024) introduced transactional semantics, open-sourced its event-driven engine, and reduced engine overhead by 90%+ over version 2.
Prefect is the tool that feels most like writing normal Python. Flows are decorated functions. Testing is standard pytest. No Docker for local development. Endpoint Closing achieved a 73.78% reduction in invoice costs switching from Astronomer to Prefect. LiveEO reported tripling development speed after adoption. For small to mid-size teams (2–10) who prioritize developer velocity over data-aware orchestration, Prefect is a strong option.
Tier 3: The Rising Newcomer
Kestra is the fastest-growing newcomer. After securing $8M in seed funding in September 2024 — with investors including dbt Labs’ Tristan Handy and Airbyte’s Michel Tricot — it launched Kestra 1.0 on September 9, 2025. Enterprise customers include Apple, Toyota, Bloomberg, and JPMorgan Chase. Its 20,000+ GitHub stars made it the fastest-growing orchestration project in 2024 by star velocity.
But the star count deserves scrutiny. As practitioner Daniel Beach noted, actual production adoption may lag behind the star count. Stars measure awareness and interest, not production deployments. The enterprise customer list is impressive for a tool that only hit 1.0 in September 2025, but production adoption evidence at the small-to-mid scale where most analytics engineers operate is still thin.
Kestra’s YAML-first approach is architecturally distinct from the Python-decorator approach of Dagster, Airflow, and Prefect. Whether YAML definitions or Python decorators win the declarative war remains to be seen, but the direction is clear: the industry is moving away from imperative task graphs.
On the Decline
Not every tool is trending upward. Luigi received only minor bug fixes in 2024. Azkaban had zero code activity. Oozie is legacy Hadoop-era tooling that has no place in a modern stack.
Mage (v0.9.79, ~8,500 stars) still exists but concerns mount about fewer than 5 active contributors, raising sustainability questions. For any team evaluating Mage for a new project, the contributor count is a red flag. A tool with that few maintainers is one key-person departure from becoming unmaintained.
The Strategic Context
Two forces are reshaping this market beyond any single tool’s release cycle.
First, the Fivetran-dbt merger makes external orchestration more strategically important, not less. Teams that want vendor optionality need an orchestration layer they control.
Second, the paradigm shift from tasks to assets is becoming the expected default. Every major orchestrator is moving in this direction — Dagster from the ground up, Airflow through its 3.0 asset decorator, Kestra through declarative YAML definitions. The question is no longer whether to adopt asset-centric thinking, but which implementation matches your team.
What to Watch for the Rest of 2026
Airflow 3.x asset maturation. The @asset decorator shipped, but can Airflow make asset-centric thinking first-class? The 3.x release cycle will answer this.
Kestra’s production adoption reality check. 20K stars need to translate into production case studies at the scale where analytics engineers actually operate.
The Fivetran-dbt integration roadmap. Will the combined entity create a walled garden, or an open platform? The answer shapes whether dbt Cloud’s built-in scheduler is “good enough” or strategically risky.
Dagster Components lowering the barrier. The Components framework and the dg CLI target SQL-first analytics engineers. If they succeed, Dagster’s learning curve objection weakens considerably.