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 Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Citus | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | postgresql, distributed-database, backports, multi-branch | field-data-collection, gis, esri-integration, mobile-apps |
| Last editorial update | 2h ago | 2d ago |
| Website | Visit → | — |
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.
Fulcrum is retiring Google Maps and betting its field app entirely on Esri.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
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.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
The Esri consolidation buys capabilities the Google engine could not offer: line and polygon snapping, GPS tracks with background tracking, offline basemaps, a redesigned mobile Location Editor, and direct connectivity to ArcGIS Online and Enterprise feature service layers. That positions Fulcrum as an ArcGIS-adjacent field client rather than a general mobile forms tool. The release cadence is high but the substance is thin between the engine migration and a steady drip of fixes.
Expect migration prompts and default-switch warnings to escalate through August as the deadline approaches, and MMPK layer support to leave early access once Esri is the only engine to support it on.
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 Fulcrum.
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 Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum 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. Fulcrum 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 Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.