What does Apache Airflow cost in 2026? Self-hosted and managed pricing explained

Pricing Overview

Apache Airflow is a free, open-source workflow orchestration platform (Apache License 2.0). There is no licensing fee — costs come from the infrastructure to run it or from a managed service.

Apache Airflow Cost Options (as of July 2026)

Self-hosted

A minimal deployment (webserver, scheduler, a few workers) runs on a single VM at roughly $50-110/month including a managed Postgres metadata store. Production on Kubernetes (official Helm chart) costs $200-2,000/month depending on worker scaling and data volume, with automatic scaling and high availability at the cost of Kubernetes expertise.

Managed services

• AWS MWAA: $0.49/hour for the Small environment and $0.99/hour for Large (verified July 2026), plus per-worker charges; a managed metadata database is included.
• Astronomer Astro: the leading commercial managed Airflow, from about $0.35-0.42/hour per deployment, scaling to custom Business pricing; Astronomer contributes heavily to Airflow itself.
• Google Cloud Composer: consumption-based on compute, database, and storage; a small environment starts around $300/month.

Hidden costs

• Operational overhead: self-hosted Airflow needs 0.25-0.5 FTE of DevOps for upgrades, dependency management, and metadata backups.
• Execution vs orchestration: managed services orchestrate; heavy task execution still consumes your own compute or the service's worker fees.
• Monitoring: production deployments add Prometheus/Grafana/Datadog costs separate from Airflow.

Editor's Note: We run Airflow for six client organisations — three self-hosted on Hetzner servers ($50-120/month each), two on Astronomer Astro, and one on Cloud Composer for native BigQuery integration. The self-hosted deployments cost less but take 2-4 hours a month of maintenance each. Re-checked July 2026: managed rates are steady — AWS MWAA Small $0.49/hr, Large $0.99/hr; Astronomer from about $0.35/hr per deployment — so the decision is unchanged: self-host if you have DevOps capacity, use Astronomer for managed Airflow without cloud lock-in, and use MWAA or Composer only if you are already deep in that cloud. — Rafal Fila, ShadowGen