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 Lightdash and Citus — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lightdash | Citus |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | bi-as-code, data-apps, ai-agents, governance | postgresql, distributed-database, backports, multi-branch |
| Last editorial update | 1d ago | 3h ago |
| Website | — | Visit → |
Lightdash is making the whole instance — dashboards, roles, agents — checkable into git
Lightdash ships close to daily and the recent run splits cleanly in two. One track is the data-app platform: apps that call third-party HTTP APIs through a server-side proxy that never exposes a secret, a query inspector that links a chart back to the query behind it, and prompt-generated chart types. The other is making the instance declarative — content as code now covers charts, dashboards, spaces, permissions, virtual views, AI agents, automations, and organization-level users, groups and custom roles.
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.
Lightdash ships close to daily and the recent run splits cleanly in two. One track is the data-app platform: apps that call third-party HTTP APIs through a server-side proxy that never exposes a secret, a query inspector that links a chart back to the query behind it, and prompt-generated chart types. The other is making the instance declarative — content as code now covers charts, dashboards, spaces, permissions, virtual views, AI agents, automations, and organization-level users, groups and custom roles.
Both tracks serve the same reader: a data team that wants BI it can build on and review in a pull request. Merging verified content with AI agents was the tell — humans and agents now draw on one trust layer, and the Lightdash MCP exposes it to outside tools like Claude and Cursor. The surface Lightdash is claiming is the semantic and governance layer, with the visualization layer increasingly something you describe rather than configure.
The export side is now complete enough that CI checks on Lightdash content — diffing or validating the exported definitions in a pull request — are the natural next step.
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.
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 Lightdash or Citus.
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 Lightdash alternatives → · See all Citus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Lightdash is currently shipping more aggressively (velocity 7.5 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. Lightdash is currently shipping more aggressively (velocity 7.5 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 Lightdash alternatives in Analytics are ranked by recent ship velocity. Browse the "Lightdash alternatives" section above for the current picks, or visit /alternatives/lightdash for the full list with editorial commentary on each.
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.