tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of Omni and Simple Analytics — 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 seven consecutive weeks 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 support on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The non-AI items are steady BI plumbing — OAuth and GitHub App authentication for dbt connections, mobile dashboard settings, map legend positioning, presentation mode.
Privacy analytics tightening its API and moving IP blocking off the CDN
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
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 seven consecutive weeks 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 support on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The non-AI items are steady BI plumbing — OAuth and GitHub App authentication for dbt connections, mobile dashboard settings, map legend positioning, presentation mode.
Two things are happening in parallel and they are related. Omni is pushing AI into the modelling layer rather than only the query layer, which is what semantic model generation reaching GA signifies — the artifact that normally takes an analytics engineer weeks is being generated. At the same time it is building the commercial and access controls that AI features require: credit limits per user and per embed entity group arrived within weeks of the AI 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.
Credit controls appearing so soon after the AI features suggests consumption limits will keep expanding to cover newer surfaces, and with searchDashboards shipped as an MCP tool, more of Omni's catalog is the obvious next thing to expose that way.
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
The work is about removing borrowed constraints. IP blocking inherited the CDN's limits and blast radius; moving it in-house made it per-site and custom-domain compatible. API v6 does the same for time handling — hourly data separates day and hour, weeks and months carry explicit start dates — while keeping v5 stable so nobody is forced to migrate. Both are the moves of a product whose users integrate it and stay.
With v6 shipped alongside an unchanged v5, expect a deprecation timeline for v5 to be the next API announcement, though the entries do not name one.
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 Simple Analytics.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
See all Omni alternatives → · See all Simple Analytics alternatives →
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 Simple Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Simple Analytics alternatives" section above for the current picks, or visit /alternatives/simple-analytics for the full list with editorial commentary on each.