Apache Airflow
Workflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.
9 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster.
Runs in
Documented customer environment
Scheduler, Dag processor, API server and metadata database, with executor-dependent workers and optional triggerers
- AWS: Customer cloud account
- DigitalOcean: Customer cloud account
- AWS
- DigitalOcean
Servers / containers
Operated by
Your team
Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Airflow Helm deployment on EKS with IAM roles ↗ · Source checked 2026-11-12
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Apache Airflow full application on DigitalOcean ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster. |
|---|---|
| Infrastructure | Servers / containers Airflow components are Python services that run on servers or Kubernetes pods with persistent metadata storage. Worker layout depends on the selected executor; a serverless task executor does not make the Airflow control plane serverless. |
| Licensing model | Open Source / Open Core The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms. |
| License | Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
DigitalOcean provides an Airflow Droplet 1-Click package and separately links a Terraform Blueprint for production. The reviewed image is 3.3.2, not the upstream 3.4 release snapshot; a 4 GB API example is not a production sizing guarantee.
DigitalOcean-listed package; Apache commercial support is not established · Source ↗ · Offer airflow ↗ — Not identified on the reviewed marketplace page; Droplet 1-Click; package 3.3.2 · Reviewed 2026-11-14
Documented · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The FAB Auth Manager provider documents OAuth login with named IdPs and custom provider configuration. Enable the compatible FAB auth manager, configure provider credentials/callbacks and user/role mapping; the default authentication manager and API/execution-token paths differ. This is an optional configured integration, not automatic SSO in every Airflow image.
Airflow web-user authentication through the FAB provider; verify Airflow/provider version compatibility · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Apache publishes an Airflow Helm chart with configurable executors and supporting services. Database migrations, chart/application compatibility, secrets and persistent logs require explicit planning.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The upstream prerequisites recommend at least 4 GB memory but explicitly make capacity deployment-dependent. Scheduler/API, metadata database, triggerer and executor/workers have different resource needs. Task concurrency, DAG parsing, logs, database I/O and replicas must be sized separately; the 4 GB floor is not an HA workload allocation.
Current application installation floor; full service/worker and HA capacity is workload-specific · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses Apache License 2.0 with separately identified bundled-component notices. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Apache Airflow 3.4.0 application; not a provider-hosted service; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was 3.4.0, published 2026-11-06. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream apache/airflow release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (6 not researched)
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The Helm chart is a deployment mechanism, not a managed control plane. Providers and Dag tasks can call external databases, APIs, compute or model services. Review each integration and executor before treating a complete pipeline as contained in the account. Managed Airflow services are separate offerings. Airflow 3.4’s Dag Importer and language-SDK support is experimental; non-Python Dag authoring requires the applicable language runtime and coordinator on Dag processors and workers.
Community & maintenance
The official announcement feed records Airflow 3.4.0 released on November 6, 2026. Stable 1.0.0 TypeScript, Java and Go SDKs followed on November 13, confirming maintained non-Python Dag authoring. The project publishes a named Adyen case study describing production orchestration across more than 20 teams and maintains a broad self-reported organization list; these establish adoption beyond repository popularity.
Category fit
- Workflow orchestration
- Directed workflows with task dependencies, scheduling, execution and monitoring. Python remains the traditional authoring language; Airflow 3.4 adds experimental whole-Dag authoring in TypeScript, Java, Go and YAML. Executor and provider configuration determine where work runs.
Compare within Workflow orchestration
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- Dagster OSSData orchestration platform for developing, scheduling and observing data-asset workflows.
- AWS
- HashiCorp Nomad EnterpriseCommercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.
- AWS
- Azure
- Google Cloud
- Kestra Self-HostedSelf-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Prefect ServerSelf-hosted workflow server and Python framework for resilient task and data pipelines.
- AWS
- Azure
- Google Cloud
- Northflank
- Temporal Self-HostedOrchestrate durable application workflows with a customer-operated Temporal Service.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow orchestration →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- What Apache Airflow does ↗airflow.apache.org
- Component architecture and deployment ↗airflow.apache.org
- Official Apache Airflow Helm chart ↗airflow.apache.org
- Upstream Apache-2.0 and subcomponent licenses ↗github.com
- DigitalOcean Airflow application deployment ↗docs.digitalocean.com
- Airflow 3.4 whole-Dag authoring beyond Python ↗airflow.apache.org
- Airflow TypeScript SDK 1.0.0 ↗github.com
- Airflow Java SDK 1.0.0 ↗github.com
- Airflow Go SDK 1.0.0 ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Airflow Helm deployment on EKS with IAM roles ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The current upstream Amazon provider guide explicitly configures Airflow Helm webserver/worker pods on EKS, including their service account, and links a self-managed Terraform deployment example. S3 logging is optional infrastructure configuration; this is not Amazon Managed Workflows for Apache Airflow. Restrict the example IAM permissions for production.
- Apache Airflow full application on DigitalOcean ↗ · DigitalOcean
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The provider catalog provisions Airflow on a customer Ubuntu 24.04 Droplet, with the application UI, local PostgreSQL and Redis, or customer-managed database services and Celery workers. This is full application hosting, not a database connector. The catalog does not identify the exact Airflow package release; verify the selected image, compatible dependencies, TLS, access controls, backups and upgrades.
- Airflow Helm deployment on EKS with IAM roles ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Current release announcements ↗airflow.apache.org
- Adyen production case study ↗airflow.apache.org
- Project-maintained organization list ↗github.com
- Airflow 3.4 whole-Dag authoring beyond Python ↗airflow.apache.org
- Stable TypeScript SDK 1.0.0 ↗github.com
- Stable Java SDK 1.0.0 ↗github.com
- Stable Go SDK 1.0.0 ↗github.com