Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of Omni and sass — 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.
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
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.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
This is a stable binding to a C++ library that is itself no longer moving, so the package's work is defined by the compilers and CRAN policies around it rather than by Sass features. Nothing in these entries suggests active development; the maintenance is competent and prompt, but it is maintenance.
The next release will most likely be triggered by a new compiler warning class or an R CMD check requirement rather than by anything in the Sass language. The entries give no signal of planned feature work.
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 sass.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
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 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. Omni 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 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 sass alternatives in Analytics are ranked by recent ship velocity. Browse the "sass alternatives" section above for the current picks, or visit /alternatives/sass for the full list with editorial commentary on each.