OpenSearch Dashboards
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
A side-by-side editorial comparison of Citus and Dagster — release velocity, themes, recent moves, and the top alternatives to consider.
Citus keeps three Postgres branches alive while chasing each new major
Citus publishes synchronized maintenance releases across at least three live branches — 14.1, 13.3 and 12.1.13 all went out on the same day in July 2026 — with contents that are almost entirely backports of the same handful of upstream fixes. The substantive release in the window is Citus 14.0 from February, which added PostgreSQL 18.1 support. Release titles are inconsistent, several carrying release dates that contradict their publication date.
Dagster's declarative automation engine just learned to trigger jobs, not only assets.
Dagster ships a core release weekly on a tight 1.13.x cadence, with most weeks split between component integrations and UI performance work. Two threads dominate the last two months: Declarative Automation as the scheduling model, and Components as the packaging model for integrations — dbt, Snowflake, dlt, Fivetran each arriving as a configurable component rather than bespoke wiring. The 1.13.16 release connects the first thread to jobs, a primitive that had been outside the declarative model.
Citus publishes synchronized maintenance releases across at least three live branches — 14.1, 13.3 and 12.1.13 all went out on the same day in July 2026 — with contents that are almost entirely backports of the same handful of upstream fixes. The substantive release in the window is Citus 14.0 from February, which added PostgreSQL 18.1 support. Release titles are inconsistent, several carrying release dates that contradict their publication date.
The pattern is a distributed-Postgres extension whose roadmap is set by Postgres itself: a major Citus version tracks a major Postgres version, then a long tail of branch releases carries fixes backward to users who cannot upgrade. Recent backport content is concentrated on correctness in edge cases — role propagation with missing grantor dependencies, deadlocks when adding named constraints with long partition names, crashes in CREATE STATISTICS — plus tightening ownership checks on citus-internal UDFs.
Expect the next Citus major to line up with the next PostgreSQL major, with 12.1 continuing to receive backports until it is retired. The entries do not indicate which branch is nearest end-of-life.
Dagster ships a core release weekly on a tight 1.13.x cadence, with most weeks split between component integrations and UI performance work. Two threads dominate the last two months: Declarative Automation as the scheduling model, and Components as the packaging model for integrations — dbt, Snowflake, dlt, Fivetran each arriving as a configurable component rather than bespoke wiring. The 1.13.16 release connects the first thread to jobs, a primitive that had been outside the declarative model.
The direction is a platform where orchestration is declared as conditions over data, and integrations are assembled from YAML-configurable components instead of Python glue. Supporting moves point the same way: dg tooling hardening, an MCP server for agent access, and a Components tab that now enumerates every instance in a code location. Alongside this, a steady stream of virtualization and bounded-fetch work in the UI signals that large deployments — thousands of assets, many backfills — are the deployments Dagster is now optimizing for.
Expect the job-level automation conditions to move from preview toward general availability, and more first-party integrations to be re-released as components. The entries do not show which integration is next in that queue.
Other Analytics 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 Citus or Dagster.
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
Feature releases every two months in 2024; one bugfix release in the last twelve.
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
Every release in this window is columnstore work — compression is where TimescaleDB is spending
See all Citus alternatives → · See all Dagster alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dagster is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. Dagster is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Citus alternatives in Analytics are ranked by recent ship velocity. Browse the "Citus alternatives" section above for the current picks, or visit /alternatives/citus for the full list with editorial commentary on each.
Top Dagster alternatives in Analytics are ranked by recent ship velocity. Browse the "Dagster alternatives" section above for the current picks, or visit /alternatives/dagster for the full list with editorial commentary on each.