Compare
dbt vs Airflow
dbt and Airflow do not compete. dbt is a SQL transformation framework; Airflow is a general-purpose orchestrator. The realistic architectures are: dbt alone (run via dbt Cloud's scheduler), Airflow alone (running raw SQL or Python), or both (Airflow schedules dbt jobs alongside other work).
Pick dbt when
- › Transformation work is the only orchestration concern.
- › dbt Cloud's scheduler is sufficient for the cadence.
- › Team uses dbt Cloud's IDE for analyst onboarding.
- › Lineage and tests in dbt are enough governance.
Pick Airflow when
- › Pipelines span more than dbt (custom Python, ML, alerts).
- › Cross-tool DAGs need a unified scheduler.
- › Ecosystem operators (S3, BigQuery, Kafka) are heavily used.
- › Operations runbooks and retries need orchestrator-level control.
Price comparison at three workload sizes
| Workload | dbt | Airflow |
|---|---|---|
| dbt-only workload (8 seats) | $800/mo (dbt Cloud Team) | Free (OSS) + 0.5 FTE or $1,500 managed |
| Cross-tool DAGs | Insufficient alone | Best fit |
| Both together (dbt + Airflow) | $800/mo seats | + $1,500/mo orchestrator |
Estimates from each vendor's published pricing page. Tune to your shape with the /tco-calculator.
Decision aid
- Transform-only: dbt Cloud
- Cross-tool orchestration: Airflow
- Mature analytics stack: Both (Airflow schedules dbt)
- Migration question: Wrong question - they are not substitutes
Related
Written by Oliver Wakefield-Smith, Founder of Digital Signet. Independent reference, no vendor sponsorship.
Sources logged at /sources. Pricing-change history at /changelog. Last reviewed 2026-06-21.