Airflow 3 vs Airflow 2: Is the Upgrade Worth It?

Airflow 3 introduces significant architectural changes and improvements, such as a modern React-based UI, a new Task SDK, DAG versioning, a rebuilt FastAPI-based REST API, and data-aware scheduling, which can greatly enhance the user experience for teams deeply invested in the Airflow ecosystem. However, the migration from Airflow 2.x, which will only receive security patches after April 2026, involves substantial refactoring due to breaking changes like the removal of direct database access, deprecated features, and the need for updated deployment configurations. While these changes may benefit Python-native teams without major architectural constraints, others might face increased operational complexity and persistent limitations, such as the Python-only workflow definitions and batch-first architecture. For teams facing these issues or considering alternative orchestration models, options like Kestra offer a language-agnostic, event-driven approach with declarative YAML-based workflows, built-in governance, and the ability to integrate various coding languages without wrapper code. As organizations weigh the upgrade against their future orchestration needs, the decision to adopt Airflow 3 or explore alternatives like Kestra will depend on specific team dynamics, existing investments, and roadmap requirements.