Citus
Citus keeps three Postgres branches alive while chasing each new major
A side-by-side editorial comparison of Fulcrum and Apache Kylin — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | Apache Kylin |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | field-data-collection, gis, esri-integration, mobile-apps | olap, gluten, native-execution, internal-tables |
| Last editorial update | 2d ago | 4h ago |
| Website | — | Visit → |
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.
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Apache Kylin's release stream is close to silent. Four of the six most recent tags carry nothing but the Maven release plugin's own commit message, and 5.0.4 in July 2026 arrived ten months after 5.0.3 with no notes at all. The last release that documented anything was 5.0.2 in April 2025, covering internal-table caching, partition-aware file merging and Gluten jar loading order.
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.
Apache Kylin's release stream is close to silent. Four of the six most recent tags carry nothing but the Maven release plugin's own commit message, and 5.0.4 in July 2026 arrived ten months after 5.0.3 with no notes at all. The last release that documented anything was 5.0.2 in April 2025, covering internal-table caching, partition-aware file merging and Gluten jar loading order.
The substance is in 5.0.0 and its follow-ups: Gluten with a ClickHouse backend as a native execution engine, internal tables, streaming and fusion models. That is a real architectural bet on native vectorised execution, but the project is not communicating it — releases ship as bare tags, and the gap between 5.0.3 and 5.0.4 suggests development has thinned to a trickle. For anyone tracking Kylin from the outside, the release feed is effectively no signal.
The entries do not support a confident call on what ships next; with untitled tags roughly annually, the useful signal about Kylin's direction will come from JIRA and the mailing list rather than from releases.
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 Fulcrum or Apache Kylin.
Citus keeps three Postgres branches alive while chasing each new major
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
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 Fulcrum alternatives → · See all Apache Kylin 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 2.5), 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 2.5), 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 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.
Top Apache Kylin alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Kylin alternatives" section above for the current picks, or visit /alternatives/apache-kylin for the full list with editorial commentary on each.