Discofork
Repository brief

apache/airflow

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T10:33:53.974Z
3mo ago

apache/airflow

Apache Airflow is a mature, actively maintained workflow orchestration project for programmatically authoring, scheduling, and monitoring data pipelines. It has a very large fork and star count, strong community activity, and a recent commit stream, which makes it a high-signal upstream for forks that want an established Python-based platform with broad ecosystem support.

GitHub
Loading tags...
Stars44,828
Forks16,788
Default branchmain
Last pushed2026-03-30T10:30:39Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

19 of 19 fork briefs
Selected

Choose this fork only if you need a near-upstream Airflow mirror and can tolerate a small lag behind upstream. If you want new capabilities or the freshest fixes, upstream Apache Airflow is the better default.

Prefer this fork only if you need its specific customizations and are prepared to maintain a large upstream gap. For most adopters, upstream Airflow is the safer choice because this fork is stale and materially behind recent fixes and maintenance work.

Choose this fork only if its added API/operator/workflow customizations are specifically valuable and you are prepared to maintain a large divergence from Apache Airflow. For most adopters who want long-term compatibility, upstream tracking, and community support, upstream is the safer default.

Choose this fork only if you want a minimally modified Airflow baseline for MWAA-adjacent work. If you need added capabilities or the newest upstream fixes, this offers little evidence of differentiation and is slightly behind upstream.

Choose this fork only if you need its internal customizations and can manage ongoing upstream sync debt. If you want the safest path for new Airflow features and lower maintenance overhead, upstream is the better default.

Prefer upstream unless you specifically need this exact pinned snapshot. This fork does not add capabilities, and its main tradeoff is being slightly behind current Airflow fixes and workflow updates.

Choose this fork only if you need Lyft-specific behavior or are already committed to its operational model. For new adopters, upstream Airflow is the safer default because this fork is stale and heavily diverged, which raises upgrade and maintenance cost.

Choose this fork only if you need its internal operational customizations and are prepared to own a large upstream delta. If you want current Airflow features, fixes, and ecosystem compatibility, upstream is the safer default.

Prefer this fork only if you are already invested in its legacy customizations and can own maintenance. If you want current Airflow features, ecosystem compatibility, and active upstream support, the upstream project is the safer choice.

Prefer this fork only if you specifically need its older custom workflow/runtime extensions and are prepared to maintain a heavily diverged codebase. For most adopters, upstream Airflow is the safer choice because this fork is stale and materially behind current Airflow development.

Choose this fork only if you need an old incubator-era Airflow snapshot and are prepared to own maintenance. For any new or production-minded deployment, upstream is the better choice.

Prefer upstream for any active or new deployment. Choose this fork only if you intentionally need an old Airflow snapshot and accept major maintenance and compatibility gaps.

Prefer this fork only if you need its exact customized snapshot and are prepared to own divergence. For most adopters, upstream Airflow is the better choice because this fork is stale and materially behind the active release line.

Prefer this fork only if you are deliberately staying on a legacy Airflow line for a narrowly defined set of old integrations. For new work, the upstream project is the safer default by a wide margin.

Choose this fork if you need Airflow as a customizable internal platform and can support ongoing upgrade work. Avoid it if you want the lowest-friction path to upstream Airflow releases and documentation.

Prefer upstream unless you specifically need the fork’s custom developer, UI, or plugin workflow changes. This fork looks best for adopters willing to own long-term merge and maintenance cost.

Choose this fork only if you need its custom developer or deployment-oriented changes and are prepared to own a large upstream gap. If you want a stable, low-maintenance Airflow base, upstream is the safer choice.

Prefer this fork only if its specific UI, operator, or Helm customizations are worth the upgrade and rebase cost. For most adopters, upstream Airflow is the safer choice because this fork is materially divergent and appears to lag recent fixes.

Choose this fork only if its customization surface matches your needs and you can absorb ongoing merge debt. For most adopters who want standard Airflow compatibility and the easiest upgrade path, upstream looks safer.