Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of Geckoboard and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
Geckoboard is refining the dashboard itself — more filtering control and faster data.
Geckoboard's recent work targets the mechanics of building and reading dashboards: multi-value GA4 contains filters, cross-object HubSpot filtering, chart granularity decoupled from timespan, configurable week-start, and webhook-driven instant updates for Zendesk agent status. It also shipped a stacked column chart — its first entirely new visualization in years.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
Geckoboard's recent work targets the mechanics of building and reading dashboards: multi-value GA4 contains filters, cross-object HubSpot filtering, chart granularity decoupled from timespan, configurable week-start, and webhook-driven instant updates for Zendesk agent status. It also shipped a stacked column chart — its first entirely new visualization in years.
The direction is steady refinement of the core dashboarding surface rather than expansion into new product areas. Most releases give analysts finer control over how existing metrics are filtered, bucketed, and refreshed — closing small gaps power users hit daily.
Expect more of the same: incremental filtering, visualization, and integration-freshness improvements. The single new chart type may signal appetite for more visualizations, but the entries don't confirm a broader push.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
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 Geckoboard or TimescaleDB.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all Geckoboard alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Geckoboard and TimescaleDB 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. Geckoboard and TimescaleDB 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 Analytics products to evaluate alongside.
Top Geckoboard alternatives in Analytics are ranked by recent ship velocity. Browse the "Geckoboard alternatives" section above for the current picks, or visit /alternatives/geckoboard for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.