Seattle Meetup: The State of Apache Airflow® 2026
Details
Join fellow Airflow enthusiasts and leaders at AWS' Offices for an evening of engaging talks, great food and drinks, and exclusive swag!
We'll start you off with a deep dive into the Airflow 2026 survey results, and finish off with a presentation on Multi-Team Airflow.
PRESENTATIONS
Talk #1: The State of Apache Airflow® 2026
- Speaker: Kenten Danas, Developer Relations Manager, Astronomer
Apache Airflow® continues to thrive as the world’s leading open-source data orchestration platform, with 30M downloads per month and over 3k contributors. 2025 marked a major milestone with the release of Airflow 3, which introduced DAG versioning, enhanced security and task isolation, assets, and more. These changes have reshaped how data teams build, operate, and govern their pipelines.
In this session, our speaker will share insights from the State of Airflow 2026 report, including:
- Latest trends in how teams are using Airflow today
- What’s next for the project and ecosystem
- A discussion of emerging best practices and evolving use cases
Join us to hear directly from a leader in the community and discover how to get the most out of Airflow in the year ahead.
Talk #2: Multi-Team Apache Airflow: A Customer-Driven Journey
- Speaker: Niko Oliveira, Sr. Software Development Engineer at Amazon & Apache Airflow Committer
As Airflow deployments scale and the number of Dag authors increases the question arises: how do we support many teams with different needs and requirements on a shared platform? Over the years we’ve observed many organizations building their own multi-tenant layers on top of Apache Airflow to solve this problem and we’re now adding native support for this type of deployment. This talk explores building multi-team support in Airflow, working backwards from those real deployment challenges and community pain points we’ve observed.
Rather than strict multi-tenancy with complete isolation, we designed a flexible multi-team architecture allowing isolated task execution, UI experience and connections/variables/secrets management to name a few. This allows multiple teams of engineers to operate within a single Airflow environment, sharing the scheduler API server and database.
We’ll cover some of the technical details of the new architecture, how what we’ve built differs from multi-tenancy, and what you can expect for the Airflow 3.2 release.
AGENDA
- 5:30-6 PM: Arrivals, networking, food & drinks
- 6-7:05PM: Presentations
- 7:05-8PM: Networking

