Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Comparison · Analytics
GDPuc vs Omni
A side-by-side editorial comparison of GDPuc and Omni — release velocity, themes, recent moves, and the top alternatives to consider.
GDPuc vs Omni: at a glance
What is GDPuc?
A GDP unit converter that keeps widening which currencies and deflators it will accept
GDPuc converts GDP figures between currencies, base years and price bases, using World Bank conversion factors, and is used as a dependency inside the madrat/magclass modelling stack. The 1.6.x line introduced xCU as a unit — local currency of any country x — added arguments for non-default iso3c and year columns, and made the package work with madrat caching and region mappings. The most recent release fixes a bug in iso3c column selection.
What is Omni?
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.
GDPuc vs Omni: editorial side-by-side
GDPuc
0.0ANALYTICS
A GDP unit converter that keeps widening which currencies and deflators it will accept
◆ Current state
GDPuc converts GDP figures between currencies, base years and price bases, using World Bank conversion factors, and is used as a dependency inside the madrat/magclass modelling stack. The 1.6.x line introduced xCU as a unit — local currency of any country x — added arguments for non-default iso3c and year columns, and made the package work with madrat caching and region mappings. The most recent release fixes a bug in iso3c column selection.
◆ Where it's heading
The direction is toward accepting messier inputs from more callers. Successive releases have relaxed assumptions the package originally made — that a year column exists, that column names follow a convention, that PPP data is available for every country — and each relaxation is driven by an integration rather than by an economics question. The one genuinely methodological addition is the CPI as an alternative deflator, which arrived in 1.0.0.
◆ Prediction
Conversion factors are versioned World Bank data and were last refreshed in 1.0.0, so a data update is the most likely content of the next substantive release, alongside continued fixes to the column-detection logic that has now produced bugs twice.
Omni
6.3ANALYTICS
Omni ships weekly, and almost every week the headline item is an AI feature.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to GDPuc and Omni
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 GDPuc or Omni.
Lightdash
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio
RStudio ships through release branches, and the notes are commit messages
Recent activity from GDPuc and Omni
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOmniOmni adds default filters on composite topics and query stopping
- 9d agoOmniOmni adds presentation mode and a searchDashboards MCP tool
- 16d agoOmniOmni adds AI credit controls per user and embed entity group
- 23d agoOmniAI semantic model generation goes generally available in Omni ⚡
- 1mo agoOmniOmni adds AI suggestion endpoints and OAuth for database connections
- 1mo agoOmniOmni brings AI routines to Slack and adds in-app MCP settings
- 8mo agoGDPucFix iso3c column selection
- 9mo agoGDPucxCU unit introduced; madrat caching and region mappings supported
- 1y agoGDPucBetter column detection; magclass objects without years accepted
- 2y agoGDPucCPI added as an alternative deflator; constant euro conversion
- 3y agoGDPucSuggests field cleaned for CRAN compliance
- 3y agoGDPucCorrect conversion factors returned by return_cfs
Frequently asked questions
What is the difference between GDPuc and Omni?
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.
Is GDPuc better than Omni?
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.
What are the best alternatives to GDPuc?
Top GDPuc alternatives in Analytics are ranked by recent ship velocity. Browse the "GDPuc alternatives" section above for the current picks, or visit /alternatives/gdpuc-r for the full list with editorial commentary on each.
What are the best alternatives to Omni?
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.