dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of Omni and silx — release velocity, themes, recent moves, and the top alternatives to consider.
Omni ships weekly, and almost every week the headline item is an AI feature.
Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across the window the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The most recent week breaks that streak — default filters on composite topics, stopping a running dashboard query, full-screen preview editing — the first digest in two months led by conventional BI work.
silx settles into maintenance a release after its PySide6 migration
silx is in the quiet phase after a generational release. 3.1.1 is a single fix to FitWidget loading a fit function from file. The release before it, 3.1.0, was the first real feature work since the migration - asinh axis scaling, twilight colormaps, and dark-theme icons - and 3.0.1 was similarly small. The 3.0.0 cut that reset the Qt binding and Python floor still defines what the line is doing.
Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across the window the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The most recent week breaks that streak — default filters on composite topics, stopping a running dashboard query, full-screen preview editing — the first digest in two months led by conventional BI work.
Two things have been happening in parallel and they are related. Omni pushed AI into the modelling layer rather than only the query layer, which is what semantic model generation reaching GA signified, then built the commercial and access controls those features require — credit limits per user and per embed entity group arrived within weeks of the capabilities that consume them. The MCP work points at a third direction, exposing Omni's content to external agents rather than only serving its own chat. The latest week's return to filters and query controls suggests the AI surface has reached the point where the surrounding product has to catch up to it.
With searchDashboards already shipped as an MCP tool, more of Omni's catalog is the obvious next thing to expose that way, and credit controls should keep extending to cover newer AI surfaces. Whether the non-AI week is a pause or a genuine rebalancing is not something one digest can settle.
silx is in the quiet phase after a generational release. 3.1.1 is a single fix to FitWidget loading a fit function from file. The release before it, 3.1.0, was the first real feature work since the migration - asinh axis scaling, twilight colormaps, and dark-theme icons - and 3.0.1 was similarly small. The 3.0.0 cut that reset the Qt binding and Python floor still defines what the line is doing.
The cadence has slowed markedly since April, and the content has shifted from structural change to plotting and colormap refinement. That is the expected shape after a binding migration: downstream beamline code needs a stable target, so the project trades feature velocity for a quiet surface. The gap between 3.0.1 in May and 3.1.0 in August is the clearest signal of the deliberate slowdown.
Expect further point releases servicing the plotting and fitting widgets rather than another structural change, with feature work continuing to arrive in the 3.1.x minors rather than patches.
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 Omni or silx.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Omni is currently shipping more aggressively (velocity 6.3 vs 5.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. Omni is currently shipping more aggressively (velocity 6.3 vs 5.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 Omni alternatives in Analytics are ranked by recent ship velocity. Browse the "Omni alternatives" section above for the current picks, or visit /alternatives/omni for the full list with editorial commentary on each.
Top silx alternatives in Analytics are ranked by recent ship velocity. Browse the "silx alternatives" section above for the current picks, or visit /alternatives/silx for the full list with editorial commentary on each.