Harbor
Harbor's patch train is now mostly about undoing regressions from its own security hardening.
A side-by-side editorial comparison of Apache Airflow and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Airflow's feed right now is a wall of provider release candidates, not core changes.
Every entry visible is a provider-package release candidate from the same October 6 batch: Telegram, Trino, Teradata, Vespa, Yandex, Tableau, Weaviate, Vertica, YDB and Zendesk, all at patch-level rc1. None carries notes beyond the batch date. The signal here is the size of the integration surface Airflow maintains, not any single change.
werf exposes git provenance to build commands and auto-includes Git LFS content.
werf ships releases almost daily across its v2 alpha/beta channels and the v3 dev line. The October 12 pair, v2.82.0 and v3.9.0, exposes git source provenance to build commands and accepts unsuffixed list environment variables; v2 also gains separate metadata repositories. v3.8.0 now pulls Git LFS content into images automatically and reports registry publication failures.
Every entry visible is a provider-package release candidate from the same October 6 batch: Telegram, Trino, Teradata, Vespa, Yandex, Tableau, Weaviate, Vertica, YDB and Zendesk, all at patch-level rc1. None carries notes beyond the batch date. The signal here is the size of the integration surface Airflow maintains, not any single change.
Airflow ships its connectors on a batched, independently versioned cadence, so provider churn will keep dominating this feed between core releases. The breadth runs from legacy warehouses (Teradata, Vertica) to vector stores (Weaviate, Vespa), which keeps the scheduler relevant as pipelines feed retrieval systems.
Expect these rc1 tags to promote to final provider releases with no content change; the entries shown give no read on the next core Airflow release.
werf ships releases almost daily across its v2 alpha/beta channels and the v3 dev line. The October 12 pair, v2.82.0 and v3.9.0, exposes git source provenance to build commands and accepts unsuffixed list environment variables; v2 also gains separate metadata repositories. v3.8.0 now pulls Git LFS content into images automatically and reports registry publication failures.
After weeks of fix-only patches for Buildah, kubectl handling and host cleanup, both lines are adding features again, and they land on v2 and v3 the same day. The new features are about build inputs and metadata: which commit an image came from, LFS files, and where image metadata is stored. That points to supply-chain traceability as the next focus.
Expect Git LFS support to reach v2 and more provenance or metadata options on both lines. The entries don't show when v3 leaves the dev channel.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Apache Airflow or werf.
Harbor's patch train is now mostly about undoing regressions from its own security hardening.
Tyk is in maintenance mode on four release lines at once, with 5.16 barely stirring.
GitHub is building an identity trail around agent-era code: who pushed, who prompted, who pays.
Infisical puts secret changes on its global approval system and splits out secret scanning.
Drone's source now ships as Harness Open Source, and it last released in August 2025.
Redocly lets docs teams define their own MCP tools, turning a docs site into an agent endpoint.
See all Apache Airflow alternatives → · See all werf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache Airflow and werf are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Apache Airflow and werf are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Apache Airflow alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apache Airflow alternatives" section above for the current picks, or visit /alternatives/apache-airflow for the full list with editorial commentary on each.
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.